Re: some headway on CallOnline problem

Gary Austin ( (no email) )
Tue, 1 Apr 1997 20:27:06 -0500

It appears that I am not the only one with this problem. I believe that
this was not a problem when I was using .49. For some reason when I
upgraded to .60 and started using radadmin the tables do not get updated.
Just the calls table. Dale has pointed out many times that the manual
calls update must be turned on but when I do the system gives me a DR.
Watson error stating their was an access violation. I would like to try a
different version other than .60. If anyone has a later version I would
like to try it and see if it works. If not I have dumped my copy of .49 so
maybe I could get someone to e-mail me that version and I will use it since
it did work.

> From: Gregory Cooper <>
> To:
> Subject: Re: some headway on CallOnline problem
> Date: Tuesday, April 01, 1997 7:08 PM
> >To:
> >From: Brad Albrecht <>
> >Subject: Re: some headway on CallOnline problem
> >
> >Is this not the same error that you get if you do not have the nas port
> >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
> >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
> >there was a sample query called callsonline.
> I have both the nas identifier and ports in the table and I am sure that
> with all the other people having the same problem it is not as simple as
> that. If you did get yours working are you using radius 60 with Access
> There are a lot of us that would like to know the exact steps to get it
> update.
> And as far as the query looking like a table, that is only true if the
> query is open. I do not want to keep the query open all the time. I
> like it to update a table and only when I want a display will I run a
> query. Plus I would also like to add information to the view like how
> each conection has been active.
> Greg Cooper
> Owner/General Manager
> ----------------------------------------------------------
> RadiusNT Mailing List