<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD><TITLE>Win2003 fcgi Install Issue and Solution</TITLE>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2838" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=791103123-07042006><FONT face=Arial
color=#0000ff size=2>Looks like we're head-banging in unison; I just ran into
the same thing.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=791103123-07042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=791103123-07042006><FONT face=Arial
color=#0000ff size=2>I did the fix that you stated, but I also had to add the
isapi handler to my Web Service Extensions. I must have manually set up
the .exe version last time, or maybe removed too many settings when cleaning up
my old uninstall.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=791103123-07042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=791103123-07042006><FONT face=Arial
color=#0000ff size=2>The Make Package function is very cool. I wonder if
it can be automated...</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=791103123-07042006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=791103123-07042006><FONT face=Arial
color=#0000ff size=2>Jason</FONT></SPAN></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Andy Morsell
[mailto:amorsell@spatialgis.com] <BR><B>Sent:</B> Friday, April 07, 2006
16:27<BR><B>To:</B> users@mapguide.osgeo.org<BR><B>Subject:</B> [mapguide-users]
Win2003 fcgi Install Issue and Solution<BR></FONT><BR></DIV>
<DIV></DIV><!-- Converted from text/rtf format -->
<P><FONT face=Arial size=2>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 face=Arial size=2>I finally traced the problem to the following:</FONT>
</P>
<P><FONT face=Arial size=2>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 face=Tahoma size=1>Andy Morsell, P.E.</FONT> <BR><FONT face=Tahoma
size=1>Spatial Integrators, Inc.</FONT> <BR><A
href="http://www.SpatialGIS.com"><U><FONT face=Tahoma color=#0000ff
size=1>http://www.SpatialGIS.com</FONT></U></A> </P></BODY></HTML>