Visual studio remote debugging 20153/31/2024 When you know which app pool which process is running, you can map them to applications that are running on that app pool in IIS Manager and pray that they will be one-to-one application to pool. Connecting to a service while it is starting is useful because determining why a service is not successfully starting is not easy unless attached with a debugger. It's not an issue connecting to a process that is running. To match ID to application pools on server run Command Prompt - As Administrator and run from %windir%\system32\intesrv\ folder command - appcmd list wp to get process ID to application pool mapping, this might help to narrow it down. When using Visual Studio 2015 and its 圆4, 2015 version remote debugger - I can't connect to a service process that is starting. Another way that can give you some insight is to use IDs of processes - IDs in your VS attach to process window can be matched to remote machine IDs (they are also in Task Manager on the server.) On the server go to IIS Manager -> Worker Procesess -> then you can match IDs to the IDs in attach to debugger window in Visual Studio.ģ. I was lucky to get one that was Local Services which I had only one running on that server. If you have RDC (Remote Desktop Connection) to the server machine, then in IIS Manager (Internet Information Services Manager) you can see which ones are Network Services and which ones are Local Services.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |