Re: [Emerald] error in log
Mon, 07 Feb 2000 10:46:39 -0600

Any other ideas on the connectivity issue? The server is on the same
local net as the NASs, in fact, everyone authenticates fine. It is
only with accounting packets. The ODBC connection checks out fine as
well when Testing on setup (in the control panel).

On Sat, 05 Feb 2000 21:41:23 -0800, you wrote:

> wrote:
>> Any idea what would cause these errors to start showing up in the log?
>> [Microsoft][ODBC SQL Server Driver][SQL Server]Violation of PRIMARY
>> KEY constraint 'pk_RadLogs': Attempt to insert duplicate key in object
>> 'RadLogs'.
>RadiusNT only logs an error once per minute per user. They tries to
>login twice with the same incorrect password. No big deal, it just
>tries to prevent your radlogs from filling up fast with duplicate
>> Sat Feb 05 09:46:23 2000: ODBC Error:S1\T00:0:
>> [Microsoft][ODBC SQL Server Driver]Timeout expired
>> Sat Feb 05 09:46:38 2000: ODBC Error:S1T00:0:
>> [Microsoft][ODBC SQL Server Driver]Timeout expired
>> Sat Feb 05 09:46:54 2000: ODBC Error:S1T00:0:
>> [Microsoft][ODBC SQL Server Driver]Timeout expired
>These sound like connectivity/SQL problems. Unless your over a WAN=20
>link, this shouldn't happen.
>> Obviously the NAS can't insert the accounting records and it's
>> accounting records get backed up. There are tons of the ODBC errors
>> and every now in then the KEY constraint error. The only thing I can
>> think of is the NASPort field has a size of 4 and I think it passes 5,
>> however, it has always been that way and the problem just started.
>NASPort is an int, not a string.=20

For more information about this list (including removal) go to: