This will happen when someone tries to login twice within the same
minute both failing. RadiusNT only logs the same type of failure
for the same user once a minute (actually, its a database restriction).
> The other error message I have never heard of...
> "Tue Aug 17 12:08:13 1999: ODBC Error:37000:260:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Disallowed
> implicit conversion from datatype 'varchar' to datatype 'int'
> Table: 'Emerald.dbo.RadLogs', Column: 'CallerID'
> Use the CONVERT function to run this query."
To fix this, use Enterprise Manager to either your RadLogs table.
Rename the CallerID field to CallerIDOld and click save. Then Close
and go back into your RadLogs table and add a new Column named
CallerID type varchar(12) and click save.
> We are also having a problem with RadiusNT, creating an access
> violation and Dr. Watson error late a night. I haven't isolated the
> Radius access violation problem yet, but if anyone knows where I can
> start to look it would be helpful.
What version of RadiusNT are you using? You might want to look
into radcheck, which works well at making sure RadiusNT is running:
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