4

I am writing a console application which uses a workflow service. I tried to attach the visual studio to IIS process to debug my application in two visual studio console but it didn't work and after that when I try to do something with my service ( update the service, build the service, open the service in browser and etc) just in-time debugger pops up: An unhandled Microsoft .net framework exception occurred in w3wp.exe[every time diffident number here]

P.S. I have a running service in IIS and before changing setup I didn't have any problem but now even after restarting I still have this problem.

mani mano
  • 49
  • 1
  • 1
  • 4
  • If its killing the process then it is probably a stack overflow or some bug in unsafe code. What appears in the windows event log? – Ben Robinson Mar 06 '13 at 16:18
  • it doesn't kill the process. I haven't change the code but I've change the setting and then error came up . in windows log, it is about callback exception. and it says something about the faulting application path: c:\windows\system32\inetsrv\w3wp.exe and this is exactly the same service that I've tried to attach visual studio to it. – mani mano Mar 06 '13 at 16:34
  • OK from your description I assumed the process was crashing. – Ben Robinson Mar 06 '13 at 16:35
  • Maybe give it a try with IIS express? – dqm Mar 06 '13 at 16:37
  • it was the IIS problem, I just solved it by restarting the server. – mani mano Mar 06 '13 at 17:56
  • Also, I've removed the service and added it again – mani mano Mar 06 '13 at 17:56

2 Answers2

1

Restart site in IIS and also restart app pool worked for me.

Devesh
  • 11
  • 1
0

Follow below article for more information. I solved this issue by running visual studio as Administrator.

http://anishantha87.blogspot.com/2014/09/an-unhandled-microsoft-net-framework.html

Hope this will help!

Aruna
  • 1,962
  • 4
  • 25
  • 50