Thanks for sharing your detailed solution. Everyone of them posted up here may help someone in the future.<br><br><div class="gmail_quote">On Tue, Dec 20, 2011 at 11:22 AM, John Grego <span dir="ltr"><<a href="mailto:johng@vtnnv.com">johng@vtnnv.com</a>></span> wrote:<br>
<blockquote style="margin:0px 0px 0px 0.8ex;padding-left:1ex;border-left-color:rgb(204,204,204);border-left-width:1px;border-left-style:solid" class="gmail_quote">My problem is now solved.<br>
<br>
Although I’ve tried everything contained in the following solution before, I<br>
believe the thoroughness and sequencing of the steps was the key to my<br>
current success in configuring IMS 2012 to run on IIS 7.5, Windows 2008<br>
Server R2 (64-bit).<br>
<br>
1. Move the contents of the Default Web Site (c:\inetpub\wwwroot) to a<br>
temporary location.<br>
<br>
2. Remove IIS 7.5 and the c:\inetpub directory contents.<br>
<br>
3. Uninstall the IMS web server extensions and remove the directory; in my<br>
case: C:\Program Files\Autodesk\Autodesk Infrastructure Web Server<br>
Extension 2012<br>
<br>
4. Reboot the server.<br>
<br>
5. Add the Web Server (IIS) role with the default services, and include all<br>
of the Application Development services, i.e., <a href="http://ASP.NET" target="_blank">ASP.NET</a>, CGI, etc.<br>
<br>
6. Install Microsoft.NET Framework V4.0.30319. At one time I had<br>
successfully configured IMS to run with Framework V2.0.50727, but I decided<br>
to try V4.0 because it was referenced by someone in another thread.<br>
<br>
7. Restore the contents of the Default Web Site that were moved in step 1.<br>
<br>
8. I reinstalled the web server extensions as I’ve done on numerous<br>
occasions, using the instructions contained here:<br>
<a href="http://wikihelp.autodesk.com/Infr._Map_Server/enu/2012/Help/New/0000-Installa0/0008-Installa8/0011-Configur11/0014-Configur14" target="_blank">http://wikihelp.autodesk.com/Infr._Map_Server/enu/2012/Help/New/0000-Installa0/0008-Installa8/0011-Configur11/0014-Configur14</a><br>
<br>
9. I created an application pool for my IMS applications, based on the V4.0<br>
.NET Framework Version in Integrated Managed Pipeline Mode. I also set<br>
the Enable 32-Bit Applications setting to False, as Hans suggested earlier.<br>
<br>
It may have been possible to achieve the same results without completely<br>
removing everything, but after various combinations of settings that did not<br>
work, this method finally helped me get IMS up and running again. I hope<br>
others may find this information useful.<br>
<br>
Regards,<br>
<br>
-John<br>
<div class="im"><br>
<br>
-----<br>
John Grego<br>
VTN<br>
<a href="http://www.vtnnv.com" target="_blank">http://www.vtnnv.com</a><br>
--<br>
</div>View this message in context: <a href="http://osgeo-org.1803224.n2.nabble.com/Mapagent-FCGI-Not-Found-tp1804128p7112984.html" target="_blank">http://osgeo-org.1803224.n2.nabble.com/Mapagent-FCGI-Not-Found-tp1804128p7112984.html</a><br>
<div class="HOEnZb"><div class="h5">Sent from the MapGuide Users mailing list archive at Nabble.com.<br>
_______________________________________________<br>
mapguide-users mailing list<br>
<a href="mailto:mapguide-users@lists.osgeo.org">mapguide-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/mapguide-users" target="_blank">http://lists.osgeo.org/mailman/listinfo/mapguide-users</a><br>
</div></div></blockquote></div><br>