[RESOLVED] HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed

Hi,

The relevant project has been deployed fine in the server but when it is being called by one other project, I got this. Why?



Server Error in '/App11' Application.

--------------------------------------------------------------------------------





The resource cannot be found.

  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.




 Requested URL: /App11/Detail.aspx





--------------------------------------------------------------------------------

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.18044  

I would suspect that you are calling a relative URL, but the web address is different on your deployment server.  In other words, you were using the same web address in development, but they have different addresses in production.

No, it is being called like this

Response.Redirect("http://192.168.168.1:81/App11/Detail.aspx");



and I see in IIS, App11 has been deployed properly.

Verify your ports then.  Make sure that they are not blocked by any firewall (server and client).

But other projects deployed in the same way, are working fine there.

Look at the "path" from the requesting page to this page that is apparently invisible to the requesting page.  What is different between this "path" in comparison to your other projects/pages.  This would involve any kind of network interaction, especially
firewalls, between the requesting page and the requested page.

Sorry, I don't see any difference within security of the path of the current project in comparison with other projects.

Hi,

Try setting up a Reverse Proxy using IIS, URL Rewrite and ARR

http://blogs.msdn.com/b/carlosag/archive/2010/04/02/setting-up-a-reverse-proxy-using-iis-url-rewrite-and-arr.aspx

Hope it can help you

wmec

No, it is being called like this

Response.Redirect("http://192.168.168.1:81/App11/Detail.aspx");

There are a lot of specific points where this could go wrong. For starters the bindings; if you're using different hostname bindings then that could obviously cause a problem. Have you tried using this same URL from your location to see what happens?

Also important to know; is there anything specific mentioned in the IIS logfiles? Because that could give you a good clue as to a possible cause.