Message-ID: <007501c1df16$ed04e4c0$0b02a8c0@whatsnewdoc> From: "Jeffrey M Donley" <email@example.com> Subject: Re: [RadiusNT] RadiusNT runtime overflow?! Date: Mon, 8 Apr 2002 12:03:23 -0400
Check the CreateDate of your masteraccounts table. I had this same problem and found that a handful of Master Accounts had a createdate with the year 1900. I am almost certain it was the createdate and not a call record. Try something like this in tsql
Select CustomerID, Createdate From MasterAccounts where CreateDate < 1/01/1950
This should give you the CreateDate and customerID, if you login to Emerald search for the customerID and adjust the dates.
----- Original Message -----
From: Kurt Schafer
Sent: Monday, April 08, 2002 4:20 AM
Subject: [RadiusNT] RadiusNT runtime overflow?!
I'm getting this error when I launch RadiusNT 4.0.12 in debug (-x15) mode.
ODBC Error  535:[Microsoft][ODBC SQL Server Driver][SQL Server]Difference of two datetime columns caused overflow at runtime.
1537 ODBC Users Loaded
The program doesn't abort however, it continues on and Radius accounting packets are in fact being recorded to the database.
What is this error ? I haven't tried authenticating from the database because the above error, and the fact that it seems to happen at 1537 users (the database has about 8000 subaccounts) disturbs me.