[RadiusNT] Concurrency problems

Sam Lowe ( (no email) )
Tue, 7 Sep 1999 14:10:26 -0500

All of a sudden our concurrency checking quit (almost) last Friday. We
noticed it was getting sporadic over the previous few days, but put it off
as a problem not getting stop records from a particular NAS. Thinking it
was possibly and indexing problem, I created a new empty calls table,
stopped the database and renamed the tables and cranked it back up. Even
with just a few records we were not getting the the stop records posted
promptly (I think). I get only ODBC timeout errors when I write an access
query, so I'm going to go back in with ISqlw to see if I can determine if
were missing stop records.

Any other ideas would be appreciated.

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