It seems to be a response time problem. If you look at the response
times, they are from 10 seconds upwards to 30 seconds. Thats not
going to cut it. :(
> Any idea what might be causing this? It wasn't happening on the old
> machine, and it's the exact same database as before, no changes to table
> structures or indexes. Is there a way to determine which table/index is
> being referred to? (It just happened again...) Here's a longshot, but is
> the dual CPU config an issue at all?
Its referring to the accounting (calls tale, primary key). The issue
is that the records DOES get saved the first time, but takes so long
the NAS re-sends it laster (getting this error). This starts an
avalanche affect that you are seeing.
One thing you might try is running in single thread mode. I'm
still not sure about how well MS Access will handle auth and
accounting simulataneously, which you are seeing a lot of (the
intertwined debug from the auth and acct is a sign of that).
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com