We're using SQL 6.5 SP5a with MDAC 2.1 SP2 (2.1.2.4202.3)
The SQL driver that comes with that is version 3.70.06.23
Josh
----- Original Message -----
From: Josh Hillman <admin-maillist@talstar.com>
To: <radiusnt@iea-software.com>
Sent: Friday, October 01, 1999 1:08 PM
Subject: Re: [RadiusNT] SNMP concurrency-checking inconsistencies
> > Josh Hillman wrote:
> > > Max 5 has the same community names as the other Maxes we have (HP
> TopTools
> > > can read data from all of the Maxes) and the problem that we're having
> here
> > > isn't specific to just Max 5--it's with all of them and it appears to
> only
> > > be a problem when RadiusNT is running as a service--the SNMP
concurrency
> > > checking appears to work fine when Radius is run from the command
prompt
> as
> > > "radius -x18". I don't know why it'd work when running from the
command
> > > prompt, but not as a service (unless it's some kind of permissions
> issue?)
> >
> From: Dale E. Reed Jr. <daler@iea-software.com>
> > Who is the RadiusNT Service configured to run as?
>
> The RadiusNT services runs using the "radius" account. The DSN is
"Radius",
> using "sa" for the login. Should these be set differently?
>
> > One thing
> > that might affect is is double-check your data directory is pointing to
> > wherever your RadiusNT installion is, and make sure the mib.txt is in
> > there. If RadiusNT can't find the mib.txt, the SNMP thread will fail,
> > and so will the SNMP checking. Remember, the RadiusNT service starts
> > in the sytem32 directory, not the c:\radius directory (or whatever).
>
> I tried this out several times today after typing in "c:\radius" into the
> RadiusNT Admin and restarting RadiusNT.
> I tested the SNMP concurrency checking--sometimes it worked; sometimes it
> caused RadiusNT to hang with the following error being displayed on the
> screen:
> Initialization of the dynamic link library c:\winnt\system32\user32.dll
> failed. The process is terminating abnormally.
>
> All subsequent authentications (by regular customers as well as me) failed
> because of Radius timeout. I had to stop RadiusNT and remove the
> "c:\radius" that I entered into the Admin before restarting
> RadiusNT--otherwise, the same problem would have occurred again at some
> point.
>
> Here's what the debug info reported (for the connections that caused
> RadiusNT to hang):
>
> radrecv: Request from host c72cc20e code=1, id=58, length=105
>
> User-Name = "test"
> Password = "-\270\337\011D\301\\015Mi="
> NAS-Identifier = 199.44.194.14
> NAS-Port = 20116
> NAS-Port-Type = Async
> User-Service = Framed-User
> Framed-Protocol = PPP
> State = ""
> Caller-Id = "8509420655"
> NAS-Port-DNIS = "8772090"
> Acct-Session-Id = "303453165"
> rad_authenticate_ODBC()
>
>
> SQL Statement: Select DateDiff(Minute, GetDate(), DateAdd(Day,
> (ma.Extension+ma.OverDue+1), maExpireDate)), DateDiff(Minute, GetDate(),
> DateAdd(Day, sa.Extension+1, saExpireDate)), sa.AccountID, sa.AccountType,
> sa.Password, sa.Login, sa.Shell, sa.LoginLimit, ma.Balance, ma.OverLimit
> From MasterAccounts ma, SubAccounts sa Where sa.Login='test' AND
> ma.CustomerID=sa.CustomerID and sa.Active<>0 and ma.Active<>0
>
> Checking for duplicate logins.
>
> SQL Statement: RadCheckOnline 'test'
>
> test found on-line 7 time(s).
>
> SQL Statement: RadCheckOnlineSNMP 'test'
>
> Error in packet.
> Reason: There is no such variable name in this MIB.
> This name doesn't exist:
> Server:199.44.194.14 SNMPUser:.1.3.6.1.4.1.529.12.3.1.4.303453158 User:
> ODBC Error:S1000:0:
> [Microsoft][ODBC SQL Server Driver]Connection is busy with results for
> another hstmt
>
> ODBC Datasource: 'Radius'...
> Making ODBC Connection...
>
> SQL Statement: INSERT INTO RadLogs(RadLogMsgID, LogDate, Username, Data,
> CallerID) VALUES (40, GetDate(), 'test', '199.44.194.14', NULL)
>
>
> For more information about this list (including removal) go to:
> http://www.iea-software.com/support/maillists/liststart
For more information about this list (including removal) go to:
http://www.iea-software.com/support/maillists/liststart