<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">
<TITLE>Win2003 fcgi Install Issue and Solution</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><FONT SIZE=2 FACE="Arial">I just experienced one of those maddening installation issues where a 1/2 hour upgrade turns into a couple of hours of banging my head on my keyboard. This was a Windows 2003, IIS6 and .NET web extension installation. I uninstalled the prior version and confirmed that the virtual and physical directories had been removed. I then installed the new version opting to have it configure IIS with .NET. Upon testing, any calls to the .fcgi mapagent resulted in a 404 page not found error. </FONT></P>
<P><FONT SIZE=2 FACE="Arial">I finally traced the problem to the following:</FONT>
</P>
<P><FONT SIZE=2 FACE="Arial">In the mapagent virtual directory in IIS, under Configuration, Application extensions, the .fcgi extension was configured as: c:\PROGRA~1\MAPGUI~1\WEBSER~1\www\mapagent\ISAPI_~1.dll. When I changed it to the long path of "C:\Program Files\MapGuideOpenSource\WebServerExtensions\www\mapagent\isapi_fcgi.dll", it mysteriously started working. I checked at the command prompt using the dir /x command to make sure that the short name was valid, and it all looked OK. So, I have no idea why using the long path and filename solved the problem, but it did. On this server, I can readily replicate the problem by substituting back in the short path and filename.</FONT></P>
<P><FONT SIZE=1 FACE="Tahoma">Andy Morsell, P.E.</FONT>
<BR><FONT SIZE=1 FACE="Tahoma">Spatial Integrators, Inc.</FONT>
<BR><A HREF="http://www.SpatialGIS.com"><U><FONT COLOR="#0000FF" SIZE=1 FACE="Tahoma">http://www.SpatialGIS.com</FONT></U></A>
</P>
</BODY>
</HTML>