From: "Jeffrey M Donley" <firstname.lastname@example.org> Subject: RE: [RadiusNT] RadiusNT runtime overflow?! Date: Mon, 8 Apr 2002 12:01:38 -0400 Message-ID: <DDEDJOHLDAIGFOJIBADAIEGBCDAA.email@example.com>
It is the StartDate NOT the CreateDate So change it to this:
SELECT CustomerID,StartDate FROM MasterAccounts WHERE StartDate < 'Jan 1
[mailto:firstname.lastname@example.org]On Behalf Of Jeffrey M Donley
Sent: Monday, April 08, 2002 12:03 PM
Subject: Re: [RadiusNT] RadiusNT runtime overflow?!
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 <
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)
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.