Monday, 22 January 2018
Unable to start debugging on the web server. The remote server returned an error(404) Not Found.
in: vs
In this article, We will discuss about How to resolve Unable to start debugging on the web server. The remote server returned an error:(404) Not Found Error.
This issue is basically related to IIS and reason behind is Sometimes IIS Stopped and due to Which this Issue Came into Picture.
There are 2 Ways exists to Resolve this Error,
1/ To Resolve this Error Open IIS Manager and in the top right Side You can find there are Restart,Start and Stop Link Button.
With in that, Click on Start button if Stop Otherwise you can also Click on Restart button also Which is Shown in below figure,
2/ Open Command Prompt in Administrator Mode and type iisreset and after Sometime the IIS will reset and Which is Shown in below figure,
RELATED POSTS
There was a problem getting an AppDomain to run the transformation from the host.The process cannot continue. while adding a View or Controller in asp.net mvc.
This is generally a Common Problem or the error could be like this, ...

Chrome script debugging in Visual Studio is enabled.
In this article, We will discuss about Chrome script debugging in Visual ...

Run Visual Studio Always in Administrator Mode.
In this article i will explain about How to run Visual Studio always ...

Copying file Content\Images\tab-close.gif to obj\Release\Package\PackageTmp\Content\Images\tab-close.gif failed. Could not find file 'Content\Images\tab-close.gif' While Publishing through File System in Visual Studio.
In this article, We will discuss How to resolve issue Could not find fil ...
-
This issue is Completely related to EntityFramework and this issue arises whenever you have installed EntityFramework in one project at th...
-
This is generally a Common Problem or the error could be like this, To Resolve this error, One Small Solution is Exists which is as b...
-
In this article, We will discuss What is the above Error and How to resolve this Error. Whenever, We are Restoring our database into A...
issue not fixed. Still showing the same error.
ReplyDelete