Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a long file path that works on my server, but a simliar path returns a 404 error when it is on my clients (IIS6) server (

Here's the functioning file path on my server: Files/McCurdys_1_0_0_0/Content/FBX/CCAE1B33/Roof-sectionB-02.fbm/hello.htm

My guesses:

  1. Maybe the file path is too long?
  2. Maybe the ".fbm" in the directory path is invalid?

Sorry for the vauge problem description. Please let me know what additional info I can provide that'd be helpful.

Update: The problem happens even in short paths, with no spaces: http://www.myserver/test.folder/hell.htm

Thanks, Adam

share|improve this question

I'm interested in finding out the cause of this also. So I did some research online. I found this article. I think it might help answering this issue.

share|improve this answer

The problem is the space in "Application Files". You should URL-encode the link (substitute the space with %20 in this case):


Two things:

  1. Perhaps your client forgot to install/enable static content on IIS. It's a feature that must be explicitly enabled on the server. See this blog post: Don't forget to check "Static content service" in IIS7 installation (it's Vista related: here the Windows Server 2008 procedure: )

IIS check static content feature IIS 7

  1. It would be very strange, because it's not the default for .htm, but maybe your client's IIS/website configuration doesn't allow the htm mimetype. See this support article: IIS 6.0 does not serve unknown MIME types
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.