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

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

Related

Asp.net Debugging Not Working

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

Unable to start debugging on the web server.

Ok so I've set up IIS on my laptop, I then went to visual studio and created a new test project called IISTest, right clicked the solution > properties > Web > and choose > Local IIS and created the virtual directory, message popped up saying directory was created successfully, I then open IIS to make sure its there and below is what I see - seems normal:
I then run the project and got the follow message:
Unable to start debugging on the web server. Unable to connect to the web server. Verify that the web server is running and that incoming HTTP requests are not blocked by a firewall.
I off to google I went, found this which explains the problem I'm experiencing http://saiabhilash.blogspot.com.au/2012/03/unable-to-start-debugging-on-web-server.html
When I open IIS and try to see if its running on the right hand side this is what I see, I don't get the option to select start/stop or reset:
Would anyone be able to suggest what's wrong please.
You start or stop/recycle the application pool. On the left pane, Application Pools are above the Websites, the options will now appear on the right pane.
You can also run Appcmd.exe, for Application Pool operations
or
Run iisreset from the command-line, for IIS Server Wide operations

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"

Calling a web service gives "Unable to connect to remote server error"

I am calling a web service from .net development environment located on my company's server. Everything was working fine until yesterday and it was returning correct data. However, today it suddenly gives me an error "Unable to connect to remote server". I entered the service URL in the browser, and that works fine. Does anybody have any idea what this problem could be about?
First thing that comes to my mind is that the proxy configuration is now different between your application and your browser. Alternatively, it could be an antivirus program running on your machine that had its configuration updated.
Just delete the webservice from app reference and re add.. it will work again.the error happens just because port number of webservice changed.

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