This seem to be created when Radius writes to the Calls table. Should
AcctSessionId be a Primary Key? Our calls table has two AcctSessionId for
each client connection (one login, one logout).
ODBC: SQLExecDirect Error -1605
[Microsoft][ODBC Microsoft Access 97 Driver] The changes you requested to the
table were not successful because they would create duplicate values in the
index, primary key,
Thanks Loads :)
At 03:37 PM 12/19/97 -0800, you wrote:
We recently upgraded to RadiusNT 2.2 and are trying to run it with our
>> Access 95 file. Radius will stop verifying after an hour or so, it seem to
>> have trouble seeing the Access database. It seem that maybe the ODBC is
>> locking up (I have the newest version I can find). There doesn't seem to be
>> any pattern to the problem but resetting RadiusNT snaps it out of its funk
>> and then it's good as new (for awhile). I've tried both the temporary
>> licence and our permanent one so it don't seem to be stuck in demo mode.
>> I've had it on three different computers (NT3.51 SP5, and NT4 SP3), and it
>> acts the same on all. The strange thing is I can run radlogin all night and
>> it won't have any problems.
>What does RadiusNT show in -x15 debug when this happens?
>Dale E. Reed Jr. (email@example.com)