Radius 2.5 still not working

Dusan Janjic ( (no email) )
Wed, 16 Sep 1998 13:13:13 -0400

Hi Dale,

I am still having problems with RadiusNT 2.5 Let me give you the sumary
of your help so far. Also a note that it works in text mode.

I originaly asked the question after installing it on our backup server,
after witch it did stop working. Let me also say that calls online and
accounting was working correctly prior to the upgrade. Here is waht you
had us do in order to solve the problem:

> > > I am not sure how to solve this??
> >
> > Run the rad25_up2.sql script against your Emerald database. It
includes
> > the missings fields noted.
>
> This seemed to fix the problem but only partially. I have noticed more
then
> usual number of users that Radius reports as logged in. Here is the
portion of
> the messages from the log file:
>
> Fri Aug 28 13:45:42 1998: ODBC Error:23000:547:
> [Microsoft][ODBC SQL Server Driver][SQL Server]INSERT statement
conflicted
> with COLUMN FOREIGN KEY constraint 'FK__RadLogs__RadLogM__1E1A7EA3'.
The
> conflict occurred in database 'Emerald', table 'RadLogMsgs', column
> 'RadLogMsgID'

The other common issue is that you don't have any entries in the
RadLogMsgs table. Because of constraints, you can't put an entry into
the RadLogs table w/out a defining entry in the RadLogMsgs table.
Run these lines in isql_w to populate the table:

INSERT RadLogMsgs VALUES(0, "Generic Message", 0)
INSERT RadLogMsgs VALUES(1, "Generic Error", 5)
INSERT RadLogMsgs VALUES(10, "User Not Found", 3)
INSERT RadLogMsgs VALUES(11, "Bad Password", 3)
INSERT RadLogMsgs VALUES(12, "User Expired", 2)
INSERT RadLogMsgs VALUES(13, "User OverDue", 2)
INSERT RadLogMsgs VALUES(14, "Over Login Limit", 1)
INSERT RadLogMsgs VALUES(15, "No Time Left", 1)
INSERT RadLogMsgs VALUES(16, "Port Not Allowed", 2)
INSERT RadLogMsgs VALUES(19, "No Attributes", 3)
INSERT RadLogMsgs VALUES(50, "Bad Request", 4)
INSERT RadLogMsgs VALUES(51, "No Username", 4)
INSERT RadLogMsgs VALUES(52, "No Password", 4)
INSERT RadLogMsgs VALUES(53, "Bad Digest", 6)
INSERT RadLogMsgs VALUES(54, "Bad username", 3)
INSERT RadLogMsgs VALUES(60, "Parse Error", 5)
INSERT RadLogMsgs VALUES(100, "Chap Not Allowed", 5)

I ran the suggested script and after that I have sent you another
question to which I never got a response. I also included the folowing
error log with the same question, but didn't receive anything from you.

Mon Aug 31 10:18:33 1998: ODBC Error:S0022:207:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'Data'.
Mon Aug 31 10:18:36 1998: ODBC Error:S0022:207:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'RadVendorID'.
Mon Aug 31 10:18:36 1998: ODBC Error:S0022:207:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'RadVendorID'.
Mon Aug 31 10:18:36 1998: rwallace: PPP-Ed has no RADIUS default
attributes.
Mon Aug 31 10:18:36 1998: ODBC Error:S0022:207:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'Data'.
Mon Aug 31 10:18:37 1998: ODBC Error:S0022:207:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'RadVendorID'.
Mon Aug 31 10:18:37 1998: ODBC Error:S0022:207:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'RadVendorID'.
Mon Aug 31 10:18:37 1998: canoe_va: PPP has no RADIUS default
attributes.

Mon Aug 31 10:18:37 1998: ODBC Error:S0022:207:
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid column name
'Data'.

After all this users were able to login only in the text mode. I would
like to fix this and make it work in ODBC mode as well. Can you help???