Re: Its back again (SQL error 2627)

Dale E. Reed Jr. ( (no email) )
Fri, 16 Jan 1998 17:59:41 -0800

I'd call USR and ask them about this. It might be a known issue
with a release of thier OS. If the Session IDs are not incrementing
and repeating, thats a pretty serious problem.

We have lots of USR users and I haven't heard of this one before.
I know computone has this problem if you don't have the time

> David Moore wrote:
> I Turned off the USR TC again and now the errors are back I can't get any
> calls on line and users are not having there on-line information logged so
> they can't be billed. I need to be able to turn off and on the USR from time
> to time and still be able to work normally without having to go through days
> of fiddling to try and get the USR to work, can any body suggest a solution.
> SQL Statement: INSERT INTO Calls
> (CallDate,AcctSessionId,UserName,NASIdentifier
> ,NASPort,AcctStatusType,NASPortType,UserService,FramedProtocol,FramedAddress,Acc
> tDelayTime) VALUES
> (GetDate(),'0001000B','test','',2,1,0,2,1,'',0)
> ODBC: SQLExecDirect Error 2627:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY KEY
> constraint 'pk_Calls': Attempt to insert duplicate key in object
> 'Calls'.Sending Accounting Ack of id 33 to cb230605 (ROMUSR)
> Resp Time: 20 Auth: 1/0 -> 1 Acct: 0/0/2 -> 2

-- Dale E. Reed Jr.  (       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |