* This is the VOP Radius mailing list *
It was definately a SQL problem.  Just not sure yet what the problem was.
All "looked" ok, mem, cpu, services, etc...

> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Gary Carr
> Sent: Tuesday, December 03, 2002 8:46 AM
> To: [EMAIL PROTECTED]
> Subject: [VOP RADIUS] Never seen this error.
>
>
> * This is the VOP Radius mailing list *
> That means that your radius server was not able to contact your sql server
> so it started the local queue then it became full and will no longer
> authenticate any new users. Check your ODBC connection and your sql server
> for processor overload or a out of memory issue.
>
>
>
> Gary
>
> ----- Original Message -----
> From: "Lanham Rattan" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Tuesday, December 03, 2002 10:34 AM
> Subject: [VOP RADIUS] Never seen this error.
>
>
> > * This is the VOP Radius mailing list *
> > I have never seen this error.  I am running SQL 7.0 for database.
> >
> > (Warning :00235) 12/3/2002 5:05:55 *X*X*X*X* Accounting ODBC Queue FULL!
> > *X*X*X*X*
> > (Warning :00235) 12/3/2002 5:05:55 The LOCAL Server thread is full of
> queued
> > requests!
> >
> >
> > **
> > To leave this list, send an email to [EMAIL PROTECTED]
> > and put the word "LEAVE" in the BODY of the email.
> >
>
>
>
> **
> To leave this list, send an email to [EMAIL PROTECTED]
> and put the word "LEAVE" in the BODY of the email.


**
To leave this list, send an email to [EMAIL PROTECTED]
and put the word "LEAVE" in the BODY of the email.

Reply via email to