Re: NASidentifier Problem
Dale E. Reed Jr. ( (no email) )
Fri, 15 May 1998 02:44:22 -0700
Lamar Townsend wrote:
> >> Resp Time: 361 Auth: 1/0 -> 1 Acct: 2/1/0 -> 3
> >> radrecv: Request from host cfcb0a22 code=4, id=41, length=66
> >> Acct-Status-Type = 7
> >> Acct-Delay-Time = 2460
> >> Acct-Session-Id = "This is an Accounting ON message"
> >> ODBC: SQLExecDirect Error 233:
> >> [Microsoft][ODBC SQL Server Driver][SQL Server]The column NASIdentifier
> >> table Calls may not be null.
> > RadiusNT 2.5 supports the accounting on/off records (it just acks them
> > right now). RadiusNT 2.2 doesn't handle them, and to succesfully
> > work you would have to have a default on all of the Key fields, except
> > Acct-Session-ID (which is likely to fail anyways, seeing how long it
> > is).
> > --
> > Dale E. Reed Jr. (firstname.lastname@example.org)
> So the ODBC: SQLExecDirect Error 233: argument is no big deal and I do
> not have to
> worry about it? It looks like everything else is working correctly for the
> time being.
Its not a big deal. Unless the NAS is continually trying to re-send it
(and it very well might be) you can ignore it.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com