There are more than one W3P.exe instances running in a CRM system (CRM app pool, reporting service etc). While debugging the MSCRM Application sometimes we get more than one W3P.exe instances. And usually we attach all those instances which slowdowns the processing of the system.
It’s unnecessary overload on system processing. We can avoid this by attaching the appropriate W3P.exe instance.
To find out which instance to attach in debugger just run the IISAPP.VBS in command prompt, it will list out all the W3P.exe instances with their port no. Now just match the port no of the CRM App Pool/ Default App Pool with the available processes list, attach the appropriate W3P.exe and start debugging.
It’s unnecessary overload on system processing. We can avoid this by attaching the appropriate W3P.exe instance.
To find out which instance to attach in debugger just run the IISAPP.VBS in command prompt, it will list out all the W3P.exe instances with their port no. Now just match the port no of the CRM App Pool/ Default App Pool with the available processes list, attach the appropriate W3P.exe and start debugging.
No comments:
Post a Comment