Message 2: Radius start error
from Ted Olson <tolson@ocsnet.net>
Message 3: Radius start error
from Ted Olson <tolson@ocsnet.net>
Message 4: Re: Radius start error
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 5: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000) produces login failures
from "Dale E. Reed Jr." <daler@iea-software.com>
Message 6: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000) produces login failures
from "Mike Stankavich" <mike@ethergate.com>
Message 7: Re: Radius start error
from Ted Olson <tolson@ocsnet.net>
Message 8: Re: ver2.5
from Ted Olson <tolson@ocsnet.net>
Message 9: Re: ver2.5 (solved)
from Ted Olson <tolson@ocsnet.net>
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 1 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Radius start error
From: Ted Olson <tolson@ocsnet.net>
Date: Sat, 25 Jul 1998 10:49:33 -0700
After *many* months without a glitch, we woke up this morning to discover
that radNT had crashed and now won't start. We made the mistake of
reinstalling Access97 on our auth server yesterday, must be related to the
problem. Here's the debug info ... ODBC indicates v3.50 of the Access
driver. Suggestions anyone, please? If remove/reinstall the driver, where
is the best source for getting the right version?
radius -x15
version 1.16.49b
Initializing Winsock...
ODBC Datasource: 'DMS'...
Allocating ODBC Henv...
Allocating ODBC Connect...
Making ODBC Connection...
ODBC: SQLConnect Error: [Microsoft][ODBC Microsoft Access 97 Driver]General
error
Failed to get the expression serviceRetry 1 (51)
Thanks much,
Ted Olson
OCS Software
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 2 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Radius start error
From: Ted Olson <tolson@ocsnet.net>
Date: Sat, 25 Jul 1998 10:56:18 -0700
Add'l info: Access ODBC driver is 3.50 342800 12/9/96
Thanks again,
Ted Olson
OCS Software
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 3 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Radius start error
From: Ted Olson <tolson@ocsnet.net>
Date: Sat, 25 Jul 1998 12:11:05 -0700
Updated to 3.50 360200 7/16/97
Still no change, same -x15 start error as first reported. Our support
phones are starting to get warm...
Thanks,
Ted Olson
OCS Software
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.
| Message 4 |
'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'
Subject: Re: Radius start error
From: "Dale E. Reed Jr." <daler@iea-software.com>
Date: Sat, 25 Jul 1998 15:17:11 -0700
Ted Olson wrote:
>
> After *many* months without a glitch, we woke up this morning to discover
> that radNT had crashed and now won't start. We made the mistake of
> reinstalling Access97 on our auth server yesterday, must be related to the
> problem. Here's the debug info ... ODBC indicates v3.50 of the Access
> driver. Suggestions anyone, please? If remove/reinstall the driver, where
> is the best source for getting the right version?
>
> radius -x15
> version 1.16.49b
>
> Initializing Winsock...
> ODBC Datasource: 'DMS'...
> Allocating ODBC Henv...
> Allocating ODBC Connect...
> Making ODBC Connection...
> ODBC: SQLConnect Error: [Microsoft][ODBC Microsoft Access 97 Driver]General
> error
> Failed to get the expression serviceRetry 1 (51)
ODBC 2.5 is available from our FTP site (as well as from Microsoft's).
We do not support RadiusNT 1.x anymore. I know that RadiusNT 2.5 corrects
problems with ODBC 3.5 drives for SQL Server. I would recommend trying
RadiusNT 2.5 to see if it resolves the problem.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 5 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000) produces login failuresFrom: "Dale E. Reed Jr." <daler@iea-software.com>Date: Sat, 25 Jul 1998 15:23:16 -0700
Mike Stankavich wrote:> > What about the SQL Server default behavior of converting 2-digit years> between 00 and 49 to 2000-2049 and 50-99 to 1950-1999? That would explain> why 2050 didn't work...
I assumed the date was actually checked in SQL Server on the 2050 thing.Its very possible that putting 1/1/50 would not actually be 1/1/2050.We are using only the new 8 digit date formats which are mmddyyyy forinserting dates into SQL Server that resolves the date interpratationproblems.
-- Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 6 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000) produces login failuresFrom: "Mike Stankavich" <mike@ethergate.com>Date: Sat, 25 Jul 1998 15:48:45 -0700
Yes, 8 digit dates take care of it once and for all. I just wanted to pointout SQL Server's default behavior for 6 digit dates. If you're curious,paste the following SQL into ISQL and execute it and you'll see exactly whatI'm talking about.
select convert(datetime, '12/31/49')select convert(datetime, '1/1/50')
The first select returns Dec 31 2049 12:00AMThe second one returns Jan 1 1950 12:00AM
I'm very comfortable with 2.5's Y2K compliance. I did notice in 2.2 that ifI put in an saExpireDate >= 1/1/2000 authentication would think that theaccount was expired, but no problem in 2.5.
-----Original Message-----From: Dale E. Reed Jr. <daler@iea-software.com>To: radiusnt@iea-software.com <radiusnt@iea-software.com>Date: Saturday, July 25, 1998 3:22 PMSubject: Re: Y2K and Radius: maExpireDate above 12-31-1999 (year 2000)produces login failures
Mike Stankavich wrote:>> What about the SQL Server default behavior of converting 2-digit years> between 00 and 49 to 2000-2049 and 50-99 to 1950-1999? That would explain> why 2050 didn't work...
I assumed the date was actually checked in SQL Server on the 2050 thing.Its very possible that putting 1/1/50 would not actually be 1/1/2050.We are using only the new 8 digit date formats which are mmddyyyy forinserting dates into SQL Server that resolves the date interpratationproblems.
--Dale E. Reed Jr. (daler@iea-software.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQsInternet Solutions for Today | http://www.iea-software.com
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 7 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: Radius start errorFrom: Ted Olson <tolson@ocsnet.net>Date: Sat, 25 Jul 1998 16:05:36 -0700
Thanks Dale,
I've been working on this all day, tried everything I think, really gettinga bit cross-eyed (I think our support phones have all melted). I guesswe'll go ahead with 2.5 - as I wrote you only a short while ago, the onlyreason I was holding off was because everything was running soooo smoothly,and I sure hate to fix what ain't broke. Oh well, another fun day in ISP-land!
-Ted
At 03:17 PM 7/25/98 -0700, you wrote:>ODBC 2.5 is available from our FTP site (as well as from Microsoft's).>We do not support RadiusNT 1.x anymore. I know that RadiusNT 2.5 corrects>problems with ODBC 3.5 drives for SQL Server. I would recommend trying>RadiusNT 2.5 to see if it resolves the problem.>>-- >Dale E. Reed Jr. (daler@iea-software.com)>_________________________________________________________________> IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs> Internet Solutions for Today | http://www.iea-software.com>
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 8 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: ver2.5From: Ted Olson <tolson@ocsnet.net>Date: Sat, 25 Jul 1998 17:45:59 -0700
Dale (or whoever),
Well, we're up with 2.5.124 ... now adding tables and fields to match thenew changes. At the moment we're trying to figure out the relationship (orlack thereof) that is causing a stream of MsgID=19 in RadLogs, accompanyiedby the logfile entries below. Can't really see the relationship so far thatis missing and causing these errors (users trying to dial in keep getting a'wrong password' message). Any help?
Sat Jul 25 17:27:45 1998: ODBC Error:07001:-3010: [Microsoft][ODBC Microsoft Access 97 Driver] Too few parameters. Expected 3.Sat Jul 25 17:27:46 1998: ODBC Error:07001:-3010: [Microsoft][ODBC Microsoft Access 97 Driver] Too few parameters. Expected 3.Sat Jul 25 17:27:46 1998: username: PPP has no RADIUS default attributes.
Well, back to work...
Thanks,-Ted
..------ ------ ------ ------ ------ ------ ------ ------ ------ ------.| Message 9 |'------ ------ ------ ------ ------ ------ ------ ------ ------ ------'Subject: Re: ver2.5 (solved)From: Ted Olson <tolson@ocsnet.net>Date: Sat, 25 Jul 1998 18:06:43 -0700
We kept plugging away and finally got this solved, our community is onceagain alive, well, and (most important) online! I'll write a recap tomorrowthat might be of some help to others, but for now it's been a lonnnnng day,time for a brewski.
Cheers,-TedOCS Software
At 05:45 PM 7/25/98 -0700, you wrote:>Dale (or whoever),>>Well, we're up with 2.5.124 ... now adding tables and fields to match the>new changes. At the moment we're trying to figure out the relationship (or>lack thereof) that is causing a stream of MsgID=19 in RadLogs, accompanyied>by the logfile entries below. Can't really see the relationship so far that>is missing and causing these errors (users trying to dial in keep getting a>'wrong password' message). Any help?>>Sat Jul 25 17:27:45 1998: ODBC Error:07001:-3010:> [Microsoft][ODBC Microsoft Access 97 Driver] Too few parameters. Expected 3.>Sat Jul 25 17:27:46 1998: ODBC Error:07001:-3010:> [Microsoft][ODBC Microsoft Access 97 Driver] Too few parameters. Expected 3.>Sat Jul 25 17:27:46 1998: username: PPP has no RADIUS default attributes.>>Well, back to work...>>Thanks,>-Ted>>