Re: SQL Error .. help

Mike Miller ( michael@abraxis.com )
Mon, 16 Jun 1997 09:29:45 -0400

Dale E. Reed Jr. wrote:
>
> Michael Miller wrote:
> >
> > Is there anyone who can tell me what this error means and how to correct
> > it? It seems to really be a problem and sometimes even causes *extreme*
> > counting delays in excess of 100,000 seconds.
> >
> > SQL Statement: INSERT INTO Calls (CallDate,UserName,NASIdentifier,NAS
> > Port,AcctStatusType,AcctDelayTime,AcctSessionId,AcctSessionTime,AcctIn
> > putOctets,AcctOutputOctets,FramedProtocol,FramedAddress) VALUES (GetDa
> > te(),'dgass','206.155.199.215',20203,2,5,'235018032',171,4660,7251,1,'
> > 206.155.199.54')
> >
> > ODBC: SQLExecDirect Error:
> > [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY K
> > EY constraint 'pk_Calls': Attempt to insert duplicate key in object 'Calls'.
> > Sending Accounting Ack of id 1 to ce9bc7d7 (MAX4002)
> >
> > Response Time: 401
>
> Most likely you need to check the Require Secret in the RadiusNT
> admin. On an Ascend box if you do not have that enabled, it
> will keep resending Accounting packets, and RadiusNT will report the
> above error for all additional copies of accounting packets it already
> has.
>
> --
> Dale E. Reed Jr. (daler@iea.com)
> _________________________________________________________________
> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs
> Internet Solutions for Today | http://www.emerald.iea.com
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com

That is likely the case. I do not have require secret enabled on Radius
NT (which you indicate is required for the Ascend products). The
majority of our server ports are on Ascend boxes, all except a USR
Netserver I which we use for our X2 connections. The reason I don't
have require secret enabled is because the USR Netserver box is not
compatible with it at all. In order to get the USR Netserver to log
accounting and show who is online, Require secret for accounting *must
be off* (I believe there is a mail somewhere about a month ago on the
list about this). If I leave the secret off I get error messages from
Radius on the Ascend boxes, and eventually the Ascend boxes themselves
begin to act up (we have had to reset one allready). If I require
secret, then the USR don't log, which is very important as well. Is
there any solution to the problem? Or is there just something simple I
am missing here (likely the case.. it's early, and it's Monday).

-- =================================================  /\                          Mike A. Miller /--\         \/              Abraxis Networks /    \ B R A  /\ I S                       /                      N E T W O R K S         michael@abraxis.com=================================================