RID manager error in the DC (server 2003 enterprise)

This problem might occur because ASP.NET limits the number of worker threads and completion port threads that a call can use to execute requests.

Typically, a call to a Web service uses one worker thread to execute the code that sends the request and one completion port thread to receive the callback from the Web service. However, if the request is redirected or requires authentication, the call may use as many as two worker and two completion port threads. Therefore, you can exhaust the managed ThreadPool when multiple Web service calls occur at the same time.

For example, suppose that the ThreadPool is limited to 10 worker threads, and all 10 worker threads are currently executing code that is waiting for a callback to execute. The callback can never execute because any work items that are queued to the ThreadPool are blocked until a thread becomes available.

Another potential source of contention is the maxconnection parameter that the System.Net namespace uses to limit the number of connections. Generally, this limit works as expected. However, if many applications try to make many requests to a single IP address at the same time, threads may have to wait for an available connection. To resolve these problems, you can tune the following parameters in your Machine.config file to best fit your situation:

* maxWorkerThreads
* minWorkerThreads
* maxIoThreads
* minFreeThreads
* minLocalRequestFreeThreads
* maxconnection
* executionTimeout

To successfully resolve these problems, do the following...

The quote's continued here... If that doesn't work, you can dig deeper with what's explained here.

There are various things to check when asp.net starts acting all funky. Checking to make sure the extensions are allowed is one, though you usually end up getting 404 not found errors rather than other sorts of failures (this is an intentionally bogus error designed to avoid leaking information to potential hackers).

However, most sorts of troubleshooting eventualy come down to reinstalling the .NET Framework and then running aspnet_regiis.exe to reset everything. There shouldn't be any differences between IIS on 2k3EE vs 2k3SE.

Also, remember that IIS isn't PAE-aware so even if you do have tons of RAM on your box, you might still have problems taking advantage of it in any given app pool.