Could the column name be mis-spelled or something.
If not, then add that column.
Try it on a test table first, but I think you can add it
to an existing table with something like;
++++++++++++++++
alter table masteraccounts
overdue tinyint
go
++++++++++++++++
Verify that in the transact manual please.
-----Original Message-----
From: Mike Noel <noel@integrityonline.com>
To: RadiusNT@emerald.iea.com <RadiusNT@emerald.iea.com>
Date: Thursday, May 07, 1998 10:48 PM
Subject: Can't find overdue column name?
I'm trying to use a SQL Server database with RadiusNT (without emerald).
I'm using RadiusNT v2.2 so I took the radius7.mdb file and converted it to
an SQL Server database using the SQL Server upsizing plugin. I added my
portmaster to the server file and left the 1 test user in the database.
I am running radius -x15 from a prompt and each time I try to connect I get
the following error message on the screen. What's the deal?
***************************************************************************
radrecv: Request from host cdee121d code=1, id=12, length=75
User-Name = "test"
Challenge-Response =
"\001\023\270\013\032T\337\360\371=\350AfC{\331\201"
NAS-IP-Address = 205.238.18.29
NAS-Port = 1
NAS-Port-Type = Async
User-Service = Framed-User
Framed-Protocol = PPP
rad_authenticate_ODBC()
Challenge-Response =
"\001\023\270\013\032T\337\360\371=\350AfC{\331\201"
SQL Statement: Select DateAdd(Day, (ma.extension + ma.overdue),
maExpireDate), DateAdd(Day, sa.extension, saExpireDate), sa.AccountID,
sa.AccountType, sa.Passw ord, sa.Login, sa.Shell From MasterAccounts
ma, SubAccounts sa Where (sa.Login= 'test' or sa.Shell='test') AND
ma.CustomerID=sa.CustomerID and sa.Active<>0 and ma.Active<>0
Sending Reject of id 12 to cdee121d (pm1.intl.integrityonline.com)
LOG: ODBC: SQLExecDirect Error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'overdue'.
ODBC: SQLExecDirect Error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'overdue'.
Resp Time: 130 Auth: 0/1 -> 1 Acct: 0/0/0 -> 0
****************************************************************************
*
I'm kinda stumped for now. Any ideas? Do I have a trigger wrong or
something? Where's the "overdue" column coming from? BTW, if I try the
long select statement (above) in the SQL Query tool I get similar errors
about an invalid column name.
Thanks for any info.
_M_
----------------------------------------------------------
RadiusNT Mailing List lists@iea-software.com