RE: [RadiusNT] just upgraded to USR HiperARC - ODBC Error:23000:-

Sean Herr ( Sean@YNC.NET )
Sun, 7 Mar 1999 15:49:56 -0600

I am running 4.1.59-6 for code in my HiperARC. Was this supposed to be
corrected in that version?

I also have an issue of port numbers coming in at 2048 or 7065 or the
majority of port 1. So basically my calls online table does not work at all
any more. Any have any ideas about that?

Sean Herr
@YourNET Connection, Inc.
847-524-3910
http://www.ync.net

-----Original Message-----
From: Clancy Knaup [mailto:cbknaup@internetwis.com]
Sent: Sunday, March 07, 1999 1:10 PM
To: radiusnt@iea-software.com
Subject: RE: [RadiusNT] just upgraded to USR HiperARC - ODBC
Error:23000:-1605

What code are you running on your HiperARC

Clancy

> -----Original Message-----
> From: radiusnt-request@iea-software.com
> [mailto:radiusnt-request@iea-software.com]On Behalf Of Dale E. Reed Jr.
> Sent: Sunday, March 07, 1999 12:49 PM
> To: radiusnt@iea-software.com
> Subject: Re: [RadiusNT] just upgraded to USR HiperARC - ODBC
> Error:23000:-1605
>
>
> Sean Herr wrote:
> >
> > I also included the records in the calls table with the same Session ID,
> > pretty strange. Is this possible a USR issue?
>
> This seems tbe be getting a progressively worse problem with USR. They
> send duplicate accounting records after a reboot. The best way to work
> around the prolem, is to add the username and nasport in the key.
>
> > SQL Statement: INSERT INTO Calls
> >
> (CallDate,UserName,NASIdentifier,AcctStatusType,AcctSessionId,Acct
> DelayTime,
> >
> NASPortType,NASPort,CallerId,FramedAddress,AcctSessionTime,AcctInp
> utOctets,A
> > cctOutputOctets) VALUES
> >
> (Now(),'jusgrr8','206.185.xx.xx',2,'18468182',0,0,2819,'','206.185
> .xx.xx',69
> > ,411,304)
> >
> > ODBC Error:23000:-1605:
> > [Microsoft][ODBC Microsoft Access 97 Driver] The changes you
> requested to
> > the table were not successful because they would create
> duplicate values in
> > the index, primary key, or relationship. Change the data in
> the field or
> > fields that contain duplicate data, remove the index, or
> redefine the index
> > to permit duplicate entries and try again.
>
> This just basically means the Acounting Record is already in the
> database.
>
> --
>
> Dale E. Reed Jr. Emerald and RadiusNT
> __________________________________________
> IEA Software, Inc. www.iea-software.com
>
> For more information about this list, including removal, please
> see this URL: http://www.iea-software.com/maillist.html
>

For more information about this list, including removal, please
see this URL: http://www.iea-software.com/maillist.html

For more information about this list, including removal, please
see this URL: http://www.iea-software.com/maillist.html