------=_NextPart_000_0004_01BE11C2.911DF5E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Hi, hope someone can assist - I am in a 'problematic' evaluation of =
emerald.
My current concern is that I might not have alignment between the =
software components and the installed database structure. I have =
installed the following components on an nt4 sp3 with sql6.5:
Radius.exe 2.5.124
RadAdmin 2.5
Emerald Admin 2.1.0
Emerald.exe 2.1.11
I have run the script Rad25_up2.sql on the 'fresh' database as advised =
somewhere in this list.
I have radius running as a service and am using odbc authentication.
With the above I can achieve a working system, however I am not able to =
perform certain operations, for example I get an SQL error if I attempt =
to alter the default attributes for a service (and the default =
attributes get wiped!). This was not the case prior to running the =
update script, however without the update script other errors prevented =
any authentication because the stored procedure getradattributes =
disagreed with the radattributes table structure. In either case (ie, =
both before and after running the update script) the 'check database' =
routine reports the tables RadAttributes & RadValues (among others) have =
an incorrect number of fields.
I will be happy to provide more exact SQL trace info or logfile output =
with -x15 debugging from radius, however I feel sure the problem lies in =
the process I am using to create the database, or is it this flakey for =
everyone?
Best regards
Peter Cassar
------=_NextPart_000_0004_01BE11C2.911DF5E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">