Asp.net Debugging Not Working - asp.net

Asp.net Debugging not working
Hi,
I am trying to run and debug my asp.net application. But i am getting the below error :
Unable to start debugging on the web server.Could not start ASP.NET debugging. More information may be available by starting the project without debugging.
You can refer the screen shot as well from the above link.

These steps might help.
Restart the app and then try restarting IIS
If the web server is local, try attaching to the server process
If the web server is local, try attaching to the server process
If the web server is remote, make sure the remote debugger is running
for more info goto original MSDN Article

Related

why I can run my asp.net site on local iis?

I have local iis7 on my machine. there are two application running on it: web service and asp.net site.
until yesterday it had worked perfectly, but today suddenly when I run it I get this error:
unable to start debugging on the web server.
the underlying connection was closed: an unexpected error occurred on a send.
click help for more information.
when I build it I don't see any problem.
what can be the problem?
See the "Tray Icons".....and
Right click on the webserver Icon->exit/close....
then run your application or
Or
restart your computer.....causes your IIS will restart...
More Information :
http://support.microsoft.com/kb/915599
Tray area in desktap

Debugging a production asp.net application locally

I made an asp.net application on my development box which was deployed on production.
I can see my application on production URL with public domain such as https://www.myapp.com ( sample).
Is it possible to debug the application by attaching the process using from my Visual studio development environment by following - Go to debug and then attach the process by selecting the browser displaying https://www.myapp.com ?
I tried it and its attaching the process but it does not hit the debug points in VS2010 . Can anyone please let me know if its possible to do this way ?
Thanks in Advance! Junni
It sounds like you are just debugging your browser. If you want to debug a remote machine you need a debug version of your code running on that machine and MSVSMON.EXE running on the remote machine. You would be best servered by reading http://msdn.microsoft.com/en-us/library/bt727f1t.aspx
then researching MSVSMON questions here.

Running ASP.net application on IIS - timeout error

I was running my asp.net application on localhost in the internal IIS for Visual Studio and for Testing purposes I was trying to host my website on my LAN at home. I obviously had to switch to use the custom IIS web server. I followed all the steps to do this i.e. I turned on IIS from the windows features in control panel and added my web application to IIS and configured VS settings to use that server and gave it a start URL.
However when I run my project I am getting an error message:
Unable to start debugging on the web server. The web server did not
respond in a timely manner. This may be because another debugger is
already attached to the web server.
What is the cause of this error and how can I solve it?
Thanks
One workaround is to make an empty page and you call the debugger from it as
System.Diagnostics.Debugger.Launch();
To solve it and make possible to start the debugger from the VS you must configure the start up page to see the local IIS on the properties of your project. Also I have notice that if you do not have default browser the IE it may also fail. So for me, to move on, call the debugger from the page.
I have the same problem and I solved it by reseting iis from cmd => "iisreset"

Debug ASP.NET application hosted on shared server from my VS2010 IDE

i have web site and it is hosted on shared server ORCSWEB. now when i testing one page locally then i found it is running fine but when i test the same page putting our live site url then i found it is not working. so i want to test that from live site but from my own VS2010 IDE and want to set break point. i just do not know is it possible or not but i can not install any remote debugger there due to lack of access.
i visit this url for gudance http://www.codeproject.com/Articles/38132/Remote-IIS-Debugging-Debug-your-ASP-NET-Applicatio
but i could not help me. thanks
I'm not an Orcsweb customer, but you cannot do Remote Debugging unless the VS Remote Debugger service is running on the target machine. If I were a shared webhost then I wouldn't provide this service to my customers because it's a massive security liability.
Out of curiosity, why can't you fix it based on any exception reports generated right now?

An unexpected DCOM error occurred while trying to automatically attach to the remote web server

I've two web sites running on my IIS 7.5. Both on port 80. Since they are both on the same port, I have to stop one to start the other. I am not using the inbuilt cassini server. Debugging works fine when using cassini.
The problem I am facing is that when I try to debug my mvc application (which was created under the second website) I get the error:
Unable to start debugging on the web server. An unexpected DCOM error
occurred while trying to automatically attach to the remote web
server. Try manually attaching to the remote web server using the
'Attach To Process' dialog.
The web application has windows authentication enabled. Any ideas?
Additional details : I'm able to do a "attach to process" and debug it. But cannot debug using F5
Although I was trying to remotely debug a simple *.exe application running on a different machine but I was getting very similar error mentioned by the OP.
Unable to attach to the process. A DCOM error occurred trying to
contact the remote computer. Access is denied.
It may be possible to avoid this error by changing your settings to
debug only native code or only managed code.
I followed this Microsoft documentation and following below step helped resolve my error:
Turn off Native Compatibility Mode and Managed Compatibility Mode.
You can follow below screen shot to achieve the same:
I didn't require to reboot the machine. You can also try that way and if it doesn't work then go ahead the reboot the machine.
Set the Connect as property of the website to Application user.

Resources