> Next time somebody logs into the port on the NAS that Emerald thinks
> somebody is logged in on (but isn't) the new call will replace the
> existing
> call. So, assuming your dial-in pool is too extensive to warrant
> simply
> going through and clearing the calls that are inaccurate if you just
> left
> concurrency control off for a little while eventually your caller
> report
> would clean itself up.
>
> I'm just getting into this stuff myself but that seems to be the
> logical
> course to me.
>
> - Kurt
>
Thanks for your reply this is exactly what was happening. I did indeed
turn off the concurency control.. Also as a note I , I was able to
clear the whole list by reporting the portmaster, in the server ports
section. Do not know how safe this was but it worked. Bye the way
the clear calls button in teh online tab just returns a SQL server fail
message.
Now on to reports.......
> ----------
> > From: Ian Pizey <ifpizey@kenora.com>
> > To: emerald@emerald.iea.com
> > Subject: Online calls are locked
> > Date: Wednesday, July 16, 1997 9:50 PM
> >
> > OK, I have expanded the database device and emerald database , and
> the
> > logsegment maxiumum size is gone away.
> >
> > However there are still a few calls locked up in the Online tab.
> > This is preventing the users from gaining access again. For now I
> have
> > turned off concurency mode, But this is not the long term solution.
>
> >
> > Is there any SQL statements or such to clear this table?
> > If so what are the appropriate commands (SQL illiterate)
> >
> >
> >
> > Thanks for any help you can give...
> >
> > ----------------------------------------------------------
> > Emerald Mailing List listserver@emerald.iea.com
> >
>
> ----------------------------------------------------------
> Emerald Mailing List listserver@emerald.iea.com