asked on

Fatal communication error

I just moved my code from Windows 2000 IIS Platform to Windows 2003 IIS and am suddenly getting the following error.

A process serving application pool 'DefaultAppPool' suffered a fatal communication error with the World Wide Web Publishing Service. The process id was '3260'. The data field contains the error number. (8007006d)

The browser simply shows "The page cannot be displayed" basically telling me nothing.

Any help is appreciated!

Thanks!

ASKER CERTIFIED SOLUTION

a_twixt_in_the_tale

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

pmartinjr1

For anyone else that has this issue, I had a similar problem with an ASP.NET application that is under development.

In my case, the problem was a stack overflow because of a code bug that made some code unintentially recursive :)

Evidently the stack overflow error is an example of a low-level .NET Framework exception that are not trapped by normal .NET exception handling. I would assume that there could be others that behave similarly.

The end result was that the w3svc (or aspnet) process was killed and restarted, the above error message was in the application log, and the application yielded some unusual behaviors.

When I fixed the bug, all symptoms disappeared.

Paul

tedhyu

I have this problem too, but I'm reluctant to change it to IIS 5.0 mode. Does anone know the drawbacks of going backwards to IIS 5.0 mode? It seems counter intuitive and is akin to changing back to Windows 98 to solve a problem.