Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Question

Monday, July 16, 2007 8:26 AM

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

 

Hi I am getting the above eror when I deploy my asp.net project to my web server. This project runs through VS2005 locally. Also when i deploy the built project on my local machine it also runs. Only when I deploy it to my web server does it bive me the error above. I have ensured that all files are there and that the permissions are set correctly.

I have a number of other projects running from this web server so I would think that if it was an IIS config issue that it would impact the other projects.

Any help appreciated.

Conor.

All replies (14)

Monday, July 16, 2007 9:26 AM

Is the correct version of the .NET framework selected in the ASP.NET tab (in IIS) for this application? 

Monday, July 16, 2007 4:38 PM

Yes The correct version of .NET is selected in IIS (.NET 2.0)

 

Monday, July 16, 2007 4:44 PM

And when you say you have a number of other projects running on this server, are they .NET projects as well (and what version)? 

Tuesday, July 17, 2007 4:50 AM

Yea, All .NET ASP projects running .NET 2.0. All the projects are very similar tot he problem one.

Tuesday, July 17, 2007 5:00 AM

What about application pools? Are there multiple pools and is the problem site using the correct one?

Thursday, July 19, 2007 10:15 AM

There is only one application pool. Also it is only one aspx file in the site that it can't find. The other files are available to view but I can see all the files on a other server and on my local machine

Monday, July 23, 2007 9:19 AM

For anybody who may want the fix for this I finally found out the issues.

I was reading in an external csv file into a class in my application.

Instead of using Server.Mappath, I referenced the file c:\inetpub\www\... directly

As my server virtual directlry was on the D: drive it could never find the file and load the class.

Sneaky!!!!

 

Conor.

Wednesday, July 8, 2009 1:14 PM

 i have various aplication pools, two named the same. my problem occurs when i try to redirect my website to the login page. in the past it was login.aspx, but it gave me an error that made me change it to pglogin.aspx, so i changed everything that had login, to pglogin.

Requested URL: /PayGate/login.aspx

i thought i didnt change it somwwhere in the app but i checked and everything is in order, and locally my app works fine, it fails when I run the app from iis.

for the record, when i launch my application it starts on pglogin.aspx, and works fine, that lead to my masterpage with its content links. the error is happening when i click logout, that is suppossed to direct me to pglogin.aspx again

i hope i made my self clear

thanks,

oswaldo

Thursday, October 8, 2009 10:49 AM

 How exactly did you reference it?  Im new at this so all the help I can get is greatly appreciated!! 

Wednesday, March 31, 2010 4:54 AM

Hi,

I am designing a website through VWD2005 express edition. The database is handled by SQL server 2005 express edn.

I was able to debug the website till yesterday but today when i am trying to debug the website in localhost it is giving me the following error message:-

HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable.  Please review the following URL and make sure that it is spelled correctly.

VWD is installed in C drive and SQL in D drive.

Please help.

Thursday, May 13, 2010 11:57 AM

Hi Jsamir,

Were you able to solve your problem? I am facing the same problem. I would be glad if you can help me out if you have solved yours.

Thank you,

Monday, May 17, 2010 4:52 AM

I was able to solve this problem.

This is when you are running the application in debug mode on your machine, it gives 404 error.

The issue was because I had in the web.config file under the section authentication->Identity, had impersonation to true and provided a userid and pwd. In this situation the userdid did not have permissions to access the page. And since in the web.config file the custom error turned off, which was misleading.

The problem solved when I set <identity impersonate="true" /> then everything is back to normal.

This might help some one.

Thank you,

Saturday, May 22, 2010 10:18 PM

HI,

I have also the same issue. But i am not using the Impersonate.If also i set [<identity impersonate="true" />] i am having same problem.

I am not browsing this through IIS.

Your help is much more appreciated!

Monday, May 24, 2010 8:40 AM

Hi Rakesh,

Make sure you have following set up in your web.config file.

<authentication mode="Windows"/>

<identity impersonate="true"/>

<authorization>

 <allow users="*"/>

</authorization>

If you still see the error then set the custom error mode off in the web.config so that you see the real error message and then you should be able to sort things out.

  • Last updated on