Last post Jun 16, 2014 09:33 AM by IainF
Jun 10, 2014 06:11 AM|IainF|LINK
I have a similar error to others and have worked through the responses posted here, but no resolution yet.
I have an ASP .Net Web Site which I can deploy and use locally with no issues (Window 7 Enterprise SP1, machine has .Net Framework 4.5.1 installed, IIS 7.5, Application Pool uses Framework v4.0.30319, Site deployed using Visual Studio Express 2013 for Web,
Published via VS using File System method).
When I try to deploy the same to a server I am able to view the default page correctly using the URL http://server/directory/ in the browser, but am unable to access any of the pages when specified directly ie.
http://server/directory/default.aspx. The error i receive is :-
"404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable."
(Virtual Machine, Windows Server Standard 6 - SP2, IIS 7.0, machine has .Net Framework 4.5 Installed, Application Pool uses Framework v4.0.30319, as above)
I have tried various suggestions but no resolution yet.
Any suggestions appreciated.
Jun 10, 2014 06:29 AM|mike4u|LINK
1- backup the site collection
2- delete the old corrupted site collection
3- restore the backup to a new site collection
Jun 10, 2014 09:10 AM|IainF|LINK
Thanks for the response.
I have tried recreating the site on different servers, export & re-import, backup & restore options, different app pools but get the same error.
I was hoping someone had come across this situation before and I was making some mistake with my server deployment or such.
Jun 10, 2014 10:53 PM|Angie xu - MSFT|LINK
Welocme to asp.net forum.
According to your description above, I’d like to suggest you to enable the failed Request Tracing in IIS, this will give me some hint on why a request has failed, we can enable this Failed Request Tracing in the IIS by steps below,
You can check log files in C:\inetpub\logs\FailedReqLogFiles, it will give more details to troubleshoot this issue.
Using Failed Request Tracing to Trace Rewrite Rules
Troubleshooting Failed Requests Using Tracing in IIS 7
Jun 11, 2014 05:13 AM|IainF|LINK
Thank you, I have enabled Request Tracing as you suggested and will check the resulting Log Files.
Jun 16, 2014 09:33 AM|IainF|LINK
This allowed me to identify an issue with the version of the .Net Framework which I have now resolved.