------=_NextPart_000_0085_01BE1691.8E96A960
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
OK, thanks for that Dale. I have obtained the file, but not yet used it. =
Can I use the Admin portion only, or do I need to upgrade the whole show =
to the beta 2.2 (with all the support limitations of a beta release)?
Given that we are about to throw some $ at iea, how far off is the 2.5 =
release (Enterprise) ? Should we hold off until then?
Thanks again.
Pete.=20
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 4 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Re: [Emerald] In search of a stable Emerald Db
From: "Dale E. Reed Jr." <daler@iea-software.com>
Date: Mon, 16 Nov 1998 23:21:03 -0800
> Peter at Datafast wrote:
>=20
> Hi, hope someone can assist - I am in a 'problematic' evaluation of
> emerald.
>=20
> 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:
>=20
> Radius.exe 2.5.124
> RadAdmin 2.5
> Emerald Admin 2.1.0
> Emerald.exe 2.1.11
>=20
> I have run the script Rad25_up2.sql on the 'fresh' database as advised
> somewhere in this list.
>=20
> I have radius running as a service and am using odbc authentication.
>=20
> 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.
You can ignore the check information. This is a bug in the Emerald 2.1
admin. The Emerald 2.2 Admin (in the /emerald/beta/emerald22 directory)
will correct the problem.
> 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?
This isn't a DB issue. Its a known issue with the 2.1 admin.
--=20
Dale E. Reed Jr. (daler@iea-software.com)
_________________________________________________________________
------=_NextPart_000_0085_01BE1691.8E96A960
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">