Problems with ODBC Duplicates in Calls table

Jim Dornbush ( (no email) )
Wed, 19 Mar 97 14:48:05 PST

RadiusNT and Emerald had been working fine on my server for over 1/2 a
year, until I moved everything to a new machine running NT 4.0 sp2 and SQL
Server 6.5. Now I am getting the following error quite frequently:

ODBC: SQLExecDirect Error: [Microsoft][ODBC SQL Server Driver][SQL Server]
Violation of PRIMARY KEY contraint 'pk_Calls':Attempt to insert duplicate
key in object 'Calls'.

I ran radius with the -x15 option and see that there are duplicate
accounting records coming from the Portmaster, each one showing a higher
value in the Acct-Delay-Time field.
It appears that the my Radius server isn't responding fast enough? Is
there a way to make the Portmaster wait a little longer? Some of the
requests are taking 500 ms to respond (but radlogin comes back in less than
100 ms).

I tried to fix this by deleting and recreating the Calls table. It
temporarily fixed the problem, but recurred in about 1/2 hour.

Also, to get the users to authenticate, I need to use the secondary Radius
server for authentication and the primary for accounting. If I don't do
this, the users regularly get disconnected with an error "unable to
negotiate connection".

Any ideas or help?

Portmaster 2e-30 is running ComOS 3.3.3. Radius version is the current
(downloaded today) version from Emerald/beta area.
Running Emerald 2.0.100.

Jim D. Manager of Internet Services, Eagle Design & Technology, Inc.