Re: [Emerald] Violation of PRIMARY KEY constraint 'pk_RadLogs'. Cannot

Dale E. Reed Jr. ( (no email) )
Wed, 22 Sep 1999 08:10:11 -0700

Mourad Dahoumane wrote:
>
> I remember this problem rose a few months ago
> but I can't find the answer.
>
> Movin to a new database, all of sudden users couldn't connect, after looking
> around in radius
> I removed the concurrency control and then they could connect again. I
> checked the time limit is set to 1 and
> secret is correctly set

Could it be that the calls online was not reset after the transfer to
the
new database? Is you calls online working at all on the next database?

> Any thoughts what can be causing this?
>
> M.Dahoumane
>
> [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY
> constraint 'pk_RadLogs'. Cannot insert duplicate key in object 'RadLogs'.
> Sun Sep 19 19:15:53 1999: User: tevans Bad PasswordSun Sep 19 19:15:56 1999
> [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY
> constraint 'pk_RadLogs'. Cannot insert duplicate key in object 'RadLogs'.

Most likely the clinet tried to auth twice in a row with the wrong
password. The second one doesn't get logged (its a duplicate).

-- 

Dale E. Reed Jr.      Emerald and RadiusNT__________________________________________IEA Software, Inc.    www.iea-software.com

For more information about this list (including removal) go to:http://www.iea-software.com/support/maillists/liststart