Re: Voilation of PRIMARY KEY

Tommy Cheng ( tommycheng@pcmagic.net )
Tue, 05 May 1998 16:25:29 -0700

Dale E. Reed Jr. wrote:
>
> This is NOT a RadiusNT issue, its a configuration issue on your PM.
> RadiusNT IS NAKing the request. Typically a terminal server will only
> allow three requests before it hangs up.

Can you give me a hint on how to do this on a PM3? Lucent guys says
that the default is to kick user after 3 bad passwords. But it is not
working.

> Neither. The constraint is designed to ONLY log on bad attempt per
> minute for a specific user and failure.

This is the trigger in calls
-----
UPDATE Emerald..SubAccounts
Set sa.TimeLeft = sa.TimeLeft - (i.AcctSessionTime/60 +
1)
FROM Emerald..SubAccounts sa, inserted i
WHERE sa.login = i.UserName
and sa.TimeLeft <> NULL
and i.AcctStatusType = 2
-----

But I still get this:

Tue May 05 16:20:41 1998: ODBC Error:23000:2627:
[Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY
constraint 'pk_RadLogs': Attempt to insert duplicate key in object
'RadLogs'.
Tue May 05 16:20:41 1998: User: SonHoang Not found
Tue May 05 16:20:45 1998: ODBC Error:00000:1310760:

Tue May 05 16:20:45 1998: ODBC Error:23000:2627:
[Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY
constraint 'pk_RadLogs': Attempt to insert duplicate key in object
'RadLogs'.
Tue May 05 16:20:45 1998: User: SonHoang Not found
Tue May 05 16:20:48 1998: ODBC Error:00000:1310760:

It's inserting records every 5 seconds. What can I do?

Tommy Cheng