In fact, it's the same problem as the view but for all the entries...
I don't understand it looks like a problem with the lock method on the
database...
We're using MS SQL 7 does anybody has tried to use radius with it ?
thanks for help
David
----- Original Message -----
From: Dale E. Reed Jr. <daler@iea-software.com>
To: <radiusnt@iea-software.com>
Sent: Tuesday, November 09, 1999 7:36 PM
Subject: Re: [RadiusNT] CallsOnLine not correct ?
> Dave wrote:
> >
> > I've checked my accounting timeouts, It is set to 15 seconds which is
> > already important...
> >
> > I've looked to the informations given by radius -x15 and the accounting
time
> > for a stop packet (AcctStatusType=2) is between 100 and 300 ms during
high
> > charges.
> > Another idea ?
>
> Check out the Manual Calls Update for you Stop Records Only Option.
> Older RadiusNT versions use the CallsOnline view for this. If there
> is something wrong with your CallsOnline view (like its not updateable,
> because its a union) then you will have problems like this.
>
> cut/paste the "Update CallsOnline ..." statement from the -x15 debug and
> run it in isql_w to see what it does. Does the port and IP address
> exist?
> Does it update any records?
>
>
> --
>
> Dale E. Reed Jr. Emerald and RadiusNT
> __________________________________________
> IEA Software, Inc. www.iea-software.com
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart