Steps to prepare your BizTalk environment for diagnostics

In the past, I publish an article about “An unhandled exception (‘<System.StackOverflowException>’) occurred in BTSNTSvc.exe” with the promise that I would explain in detail how I was able to debug the .NET stack using the Microsoft Symbol Server to obtain debug symbol files and now is the time.

Step 1: Prepare the environment for debugging (set up the Symbol Server)

First one note: if you are using a Lab environment with Visual Studio, like me, skip step 1 and 2.

1. Download the Debug Tools: https://docs.microsoft.com/en-us/windows-hardware/drivers/download-the-wdk
2. Install this Debug Tools in: “c:\tools\debug”
3. Download Sysinternals: https://docs.microsoft.com/en-us/sysinternals/downloads/sysinternals-suite
4. Unzip the tools to: “c:\tools\bin”
5. Go to “Control Panel ➤ System ➤ Advanced ➤ Environment Variables”

   

6. In “System Variables” section, press “New” and add the following variable:
   1. Variable name: “_NT_SYMBOL_PATH”
   2. Variable value: “SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols”

1. In the “User variables for user” section, press “New” and add the following variable:
   1. Variable name: “PATH”
   2. Variable value: “C:\tools\bin”

1. Press the OK button twice.

Step 2: Prepare the “Process Monitor”

1. Run procmon.exe
   

   

2. Go to the menu option “Options ➤ Configure Symbols”
   

   

3. Ensure that the “DBGHELP.DLL” path is equal to “C:\TOOLS\DEBUG\dbghelp.dll” or is one path of the version used in Visual Studio
4. Ensure that the “Symbol Path” is equal to “SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols”
   

   

5. Press OK button

Step 3: Prepare the “Process Explorer“

1. Run “procexp.exe”
   

   

2. Go to the menu option “Options ➤ Configure Symbols”
   

   

1. Ensure that the “DBGHELP.DLL” path is equal to “C:\TOOLS\DEBUG\dbghelp.dll” or is one path of the version used in Visual Studio
2. Ensure that the “Symbol Path” is equal to “SRV*c:\websymbols*http://msdl.microsoft.com/download/symbols”
   

   

3. Press OK button

Now when the exception occurs, the system will automatically instantiate one Visual Studio instance with the trace .NET stack, giving me the exact point of the problem.

References

• Use the Microsoft Symbol Server to obtain debug symbol files: http://support.microsoft.com/kb/311503

Once again I want to thank Jorge Lourenço for help!