This is actually a fairly common message and not something you need to be
RadiusNT will only enter an error message for the same user, values and error
once per 60 second period. This is to prevent your RadLogs table (the table
recording authentication failures) from filling up due to redial functions,
particuarly on ISDN devices (which have no handshake time to speak of and thus
can generate 60+ of the same errors per minute). Violations of primary key
simply mean the system already has an entry identical to that one within the 60
seconds allotted. If the user tries multiple different passwords, for example,
each of those errors will appear in your logs.
IEA Software Customer Service
Nicolaj Ottsen wrote:
> Hello everybody,
> I get the following error in -x15 mode when I try to authenticate en unknown
> user several times. The first attemt is OK but the second reprots the
> following error.
> Is something wrong with my RadLogs PrimaryKey ?
> SQL Statement: INSERT INTO RadLogs(RadLogMsgID, LogDate, Username, Data,
> ID) VALUES (10, GetDate(), 'USER01', 'user01', '8479820101')
> ODBC Error:23000:2627:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY
> int 'pk_RadLogs'. Cannot insert duplicate key in object 'RadLogs'.
> Nicolaj Ottsen