Re: Radius 25 help please.

Dale Reed ( )
Fri, 12 Jun 1998 14:27:09 -0700

Eric Jensen wrote:
> I upgraded to Radius 2.5 and used the Radius_25_124_Update files. I also
> used the rad25_up.sql script to update the database. Users can login
> without a problem and everything seems to be running ok. Except for the
> following errors in the logfile:
> Fri Jun 12 11:07:20 1998: ODBC Error:23000:547:
> [Microsoft][ODBC SQL Server Driver][SQL Server]INSERT statement
> conflicted with COLUMN FOREIGN KEY constraint
> 'FK__RadLogs__RadLogM__0642F512'. The conflict occurred in database
> 'Emerald', table 'RadLogMsgs', column 'RadLogMsgID'

This is most likely because your RadLogMsgs table is empty. You can
populate it with the following statements (execute in isql_w on your
Emerald database).

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(60, "Parse Error", 5)
INSERT RadLogMsgs VALUES(100, "Chap Not Allowed", 5)


> Fri Jun 12 14:55:45 1998: ODBC Error:37000:103:
> [Microsoft][ODBC SQL Server Driver][SQL Server]The identifier that
> starts with '`o' is too long. Maximum length is 30.

I'm not sure which table/field this is. Its possible that this is
caused by a garbage RadLogs entry, though.

-- Dale E. Reed Jr.  (       IEA Software, Inc.      |  RadiusNT, Emerald, and NT FAQs Internet Solutions for Today  |