Each thread is RadiusNT uses its own connection to the SQL Server. The
error is when the thread doesn't clean up one query before making another.
Hence the "connection is busy". I thought I cleared all of them up, but
you probably found an instance (most likely the result of an odd error)
where it still happens. I'll check the DB code and see if I can find it.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com