Clever Geek Handbook

Attaching Visual Studio Debugger to Sharepoint 2007 Workflow Crashes Process

When trying to connect to a sharepoint-related iis workflow, the workflow exits with the following error:

The debugging process of the web server that was debugged was interrupted by IIS. http://blog.chrisballance.com/content/binary/workerProcessError.png

I have the correct assemblies installed because adding the following line to my code has the same effect when the debugger is not connected, similar to the IIS workflow for Sharepoint crashing:

System.Diagnostics.Debugger.Break();

Environment

  • Visual Studio 2008
  • IIS7
  • Single VM processor with 4GB memory

Any ideas here?

+2


source to share


2 answers


Chris

I don't know where you go to debug in your code, but I'm guessing it's in the section that somehow breaks communication with the workflow. If standard checks are performed in place (the default behavior) for the health of the workflow, IIS detects that your workflow is unresponsive and recycles it.

I have no suggestions from the code side, but have you tried to disable the app pool health check while debugging? This will require the following for the workflow serving your site:



  • Uncheck the boxes marked on the Recycling tab of the relevant application pool configuration settings.
  • Uncheck the Health tab options for pinging and fast crash protection.

This should prevent IIS from assuming that your worker process is "hanging" when, in fact, it is paused and waiting for your intervention.

Hope this helps!

+1


source


Did you notice that the Maximum Ping Response Time value shown in the error message is not set very low for the SharePoint application pool?

IIS Manager => Application Pools => (Select Application) => Advanced Settings



The default is 90 seconds, but for real debugging, you probably want to increase this

+1


source






More articles:


All Articles