Could not start Asp.Net debugging1IIS - custom web server - unable to start debugging on the web server9The Web Server Could Not Find the Requested Resource visual studio debugging8Unable to start share|improve this answer answered Aug 28 '15 at 13:58 John 112 add a comment| up vote 0 down vote This can also be caused if your website uses a database connection For ASP.NET Core, the IIS process is dnx.exe (Please see Remote Debugging ASP.NET on a Remote IIS Computer or, for ASP.NET Core, see Publishing to IIS).Choose Attach.If the web server is Thank you! –James Nelli Feb 25 '14 at 14:25 add a comment| up vote 2 down vote It sounds like you are probably hitting F5 in Visual Studio when you receive Source
If not, you need to launch the application without debugging and manually attach to it. (For more information, see Manually Attaching and ASP.NET Debugging: System Requirements.)Does your Web application have a I sure do wish this error was less generic, seems like there are several different ways to produce it. You need to check this:- Unable to Start Debugging on the Web Server On a side note:- Go to IIS and check that the App Pool you are using is started. Not sure what is diff between the two apps that would cause IIS debugging to be different.
Hope this helps someone. ;) share|improve this answer answered Jul 15 at 9:26 Atif Ali Bhatti 11 add a comment| up vote 0 down vote I know this is an old share|improve this answer answered Aug 5 '08 at 16:35 palehorse 13.9k23144 add a comment| up vote 2 down vote For me I had two visual studio open. Debugging a Web server requires NTLM authentication. Unable To Start Debugging On The Web Server Windows 10 Dev centers Windows Office Visual Studio Microsoft Azure More...
Treat my content as plain text, not as HTML Preview 0 … Existing Members Sign in to your account ...or Join us Download, Vote, Comment, Publish. Unable To Start Debugging On The Web Server Iis Does Not List A Web Site Disclaimer All the stuff we're putting on this website is intended to be public domain, and each post reflects our own personal opinions and thoughts. Accidentally stumbled on this site after many frustrated and failed suggestions gotten from other sites. Or set it in the properties of the shortcut.
take a look. Unable To Start Debugging On The Web Server Operation Not Supported Details about how to run the remote debugger as a service can be found in Remote Debugging.Once the remote debugger installed, make sure the remote debugger is running on the target I have two ASP.NET mvc web apps that I run on locally in IIS 7.5. share answered Jun 18 '12 at 8:40 Breeno 1,0681113 2 Thanks for sharing the solution with everyone!
Make sure that each application is using a different application pool. IIS let me add them and it was only when I decided to check the MIME types for the site again as part of my diagnostic process that I got an Unable To Start Debugging On The Web Server. The Web Server Is Not Configured Correctly Thus, to debug on the 64 bit machine, you might need to make sure the remote debugging components are installed correctly. Unable To Start Debugging On The Web Server. The Web Server Could Not Find The Requested Resource The web server did not respond in a timely manner.” up vote 38 down vote favorite 8 I get the following error pretty regularly when compiling in Visual Studio and running
Join them; it only takes a minute: Sign up Visual Studio “Unable to start debugging on the web server. this contact form If your web site is configured in IIS to require authentication, this authentication will fail. Try this from your command line:- cd %windir%\Microsoft.NET\Framework\v4.0.30319 aspnet_regiis.exe -i share|improve this answer edited Sep 8 '13 at 6:27 answered Sep 8 '13 at 6:13 Rahul Tripathi 103k15102177 yes If so, you can debug using Integrated Authentication. Unable To Start Debugging On The Web Server. The Debugger Cannot Connect To The Remote Computer
share|improve this answer answered Mar 25 '13 at 14:39 Ike 547716 1 Not a solution, surely? –Moose Factory Apr 19 '13 at 14:22 add a comment| up vote -1 down Daha fazla göster Dil: Türkçe İçerik konumu: Türkiye Kısıtlı Mod Kapalı Geçmiş Yardım Yükleniyor... Yükleniyor... http://webinweb.net/unable-to/visual-studio-unable-to-start-debugging-on-the-server.html Hakkında Basın Telif hakkı İçerik Oluşturucular Reklam Verme Geliştiriciler +YouTube Şartlar Gizlilik Politika ve Güvenlik Geri bildirim gönder Yeni özellikleri deneyin Yükleniyor... Çalışıyor...
Restart the Application Pool from IIS Manager > Application Pool Restart the IIS instance by opening a command prompt with administrative rights and typing iisreset. If that's so, you're done: otherwise, go back to the IIS Manager > Application Pools panel and check again the DefaultAppPool status: if it's stopped again, it means that something on your system causes Is getting IN or OUT of orbit easier for the Space Shuttle? Unable To Start Debugging On The Web Server. Unable To Connect To The Web Server Your breakpoints in App 1 (running in VS.NET) will be hit when accessing App 2 (ran from IIS directly).
See Deploy an ASP.NET Application or, for ASP.NET Core, Publishing to IIS).Make sure that you have an application pool for the app running in IIS.It is possible that the application pool This solution worked for me perfectly. I checked the following: Security requirements — I don't recall having to do anything special before. Check This Out Eventually I found that the SQL Server (MSSQLSERVER) service was not running.
ClickHERE to participate the survey. In my case my application pool was stopped. They both are ASP.NET 4.5 and use Local IIS and the same app pool. I had to restart the application pool in additional. –Sunil Feb 16 '15 at 12:18 | show 6 more comments up vote 36 down vote accepted Turns out that the culprit
Enable 32-bit application settings set as True.for this , right click on Application Pool -> Advance Setting -> Enable 32 bit Application -> TRUE2. Be sure to have Front Page Extensions installed if you are debugging through IIS. On a separate occasion I had to: terminate all my iis worker processes in the windows task manager (w3wp.exe*).