Re: some headway on CallOnline problem

Brad Albrecht ( )
Sun, 30 Mar 1997 16:50:36 -0800

Is this not the same error that you get if you do not have the nas port in
the database for that server? Radius is trying to update a table (OR
query) called Callsonline, looking for a field to correspond to with the
nas port that it wants to update (nas server too). By default, Dale did
not populate the sample database with ports and servers (for obvious
reasons), so it does not work without populating the dB with your data.
All you should have to do is to add the ports for each server, as well as
the server. By the way, a query will work here, as it looks the same to
Radius as a table does. In the last version of the sample database I saw,
there was a sample query called callsonline.

Correct me if I am wrong here Dale, but this is how I got it working, and
it makes sense to me.

Brad Albrecht
Computer Innovations Online

At 02:44 PM 3/30/97 -0700, you wrote:
>This is what I have found so far about the Calls Online problem. I am also
>affected by it and am working on a solution. During debug I have captured
>a screen and the following was reported (x-15 -o -R18)
>Allocating Statement....
>SQL Statement: UPDATE CallsOnline Set UserName='user', AcctStatusType=2,
>CallDate=Now() WHERE NASIdentifier='[nas identifier here]' and NASPort=1
>ODBC: SQLExecDirect Error:
>[Microsft][ODBC Microsoft Access 97 Driver] Too few parameters. Expected 1.
>bla, bla, bla....... ect.
>Based on the SQL statement it is looking for a TABLE (not a query) by the
>name of "CallsOnline" with fieldnames of UserName, AcctStatusType,
>CallDate, NASIdentifier, and NASPort. You must have your "nas identifier"
>in the NASIdentifier field with the corresponding port in the NASPort
>field, (this is for the compare part or WHERE in the statement).
>There was no such table in my download of RADNT_60 so I built the table.
>But it doesn't help due to the SQLExecDirect Error. I still recieve this
>error. I checked the Dr. Watson dump file and did not find any more clues
>to the problem. I could be wrong but my guess is that within radius an SQL
>statement is not conforming to the Microsoft non-standard rules. This
>would also be one possible explanation why some have good results using SQL
>Server as apposed to Access 97.
>just my 2 cents worth.
>Has anyone else found out more about this error?
>I am now working on a VB module triger that will watch for an add record to
>the Calls table and make the appropriate update to the CallsOnline table.
>This will allow for a temp solution and you won't need option 2 checked for
>it to work. I will make this publicly available and it will go in the
>module part of the database untill Dale finds another solution, or if he
>finds out that we are all out of our minds. B-)
>I do want to thank Dale for an extreemly good product.
>I am going to be working on a VB front end that when finished I will place
>on my site for downloading.
>Greg Cooper
>Owner/General Manager
> ----------------------------------------------------------
> RadiusNT Mailing List