RE: [RadiusNT] .209 broke something

Graeme Slogrove ( )
Tue, 4 Jan 2000 13:56:57 +0200

Checked the database on this side and it was already set up exactly as you
recommended, but still no joy with calls online.


---Graeme Slogrove, BSc (Eng) Elec (Wits)Director, Systems Development & Value Added ServicesNetActive InternetTel: 011-719-0333    Fax: 011-719-0444Support: 011-719-0300

-----Original Message-----From: Dale E. Reed Jr. []Sent: 30 December 1999 01:21To: radiusnt@iea-software.comSubject: Re: [RadiusNT] .209 broke something

Graeme Slogrove wrote:> > We had the same problem with .209 - no calls online appear anymore.> > Haven't looked at the debug, but I'm switching back to .206 right away.

Its not a problem with 209, but rather a DB issue. 209 addressesa VSA problem with RadValues. You MUST modify your RadValues tableas follows:

1) Remove the Primary Key on your RadValues table, and insert two New Columns after the RadAttributeID:

RadVendorID Number Default: 0 RadVendorType Number Default: 0

2) Save the table (without a Primary Key).

3) Run this query:

Update RadValues Set RadVendorID=0, RadVendorType=0

4) Add a primary key with the following fields (you click the first, and hold down the control key while clicking the rest).

RadAttributeID RadVendorID RadVendorType Value

> On bootup, we get:> > SQL Statement: Select Server, IPAddress, Secret From RadRoamServers Where> RadRoamServerID > 0> > ODBC Error:07001:-3010:> [Microsoft][ODBC Microsoft Access 97 Driver] Too few parameters. Expected1.

This is how MS Access says "I didn't know one of those columns". DoubleCheckyour RadRoamServers table and make sure it has atleast those threecolumns. > And our calls table stopped updating. We get the following error:> > SQL Statement: UPDATE Servers AS s, ServerPorts AS sp Set> sp.Username='propp',sp.AcctStatusType=1, sp.CallDate=Now,> sp.FramedAddress='', CallerID='5176879328',> AcctSessionID='30000CAD' WHERE sp.ServerID = s.ServerID AND> s.IPAddress='' and sp.Port=5 AND (DateAdd('s', 0-1, Now) >=> sp.CallDate OR sp.CallDate IS NULL)> > ODBC Error:07001:-3010:> [Microsoft][ODBC Microsoft Access 97 Driver] Too few parameters. Expected> 2.

Again, this is probably missing columns in your ServerPorts table.209 adds support for AcctSessionID and CallerID in the ServerPortstable. If you don't have those columns, you will need to add them.You can get the size/types from the calls table.


Dale E. Reed Jr. Emerald and RadiusNT__________________________________________IEA Software, Inc.

For more information about this list (including removal) go to:

For more information about this list (including removal) go to: