500 error: The system cannot find the path specified.

Jan 6, 2010 at 7:23 PM

Hello, I am working with a customer who is trying to configure ManagedFusion as a reverse proxy on IIS 6.0.  I have successfully configured ManagedFusion as a reverse proxy on both my Windows 2003 Server and Windows XP dev servers.  But for some reason I can't seem to get it working at the customer site.  I can understand how the issue I'm facing might not be related to ManagedFusion itself but perhaps someone else has encountered a similar error.

The web app configuration at the customer appears to be correct as it is nearly identifcal to my dev servers which work perfectly.  Rewrite logging is enabled (with level = 9 if that matters).  And most importantly, the checkbox "Verify that file exists" is NOT selected under the wildcard mapping.

Our ManagedFusion.Rewriter.txt file contains a single rewrite rule:  RewriteRule /myapp/(.*)  http://server2/myapp/$1   [P,L]

The idea of course being that when a client requests a page from the IIS server (e.g.  http://server1/myapp/abc.html ) that the IIS will proxy the request to server2 (e.g http://server2/myapp/abc.html )

The behavior/issue we have is the following.  From a browser, we enter the URL http://server1/myapp and we can see in the rewrite log file that the URL is being processed.  However when we try to access a specific page (e.g. http://server1/myapp/login.jsp) the rewrite log file does not contain any additional traces, suggesting that ManagedFusion has not been given a change to examine the request.  The IIS log shows a response code of 500 was returned.  And the browser shows the message "The system cannot find the path specified."

Please let me know if you have any suggestions on how I might resolve this issue.

Thanks in advance,



Jan 8, 2010 at 5:15 PM

Make sure the *.jsp file isn't being handled by the Java VM on server1.  

Jan 11, 2010 at 6:15 PM

Yeah, we checked.  There is not anything registered for the jsp extension.

But you got me thinking, what about other extensions.  Our initial tests only focused on two requests, one without a page reference, the other request with a .jsp page.  To my surprise other file extensions (.asp, .js, .jpg) are working as expected.  So my guess is that something has been previously configured on the customers' IIS for jsp files (for another site perhaps).  I'm in the process of making that determination now.  Thanks for help!


Jan 11, 2010 at 6:41 PM

No problem, glad I could help.