Yes, I've seen this too. You can't run 1.1 and 2.0 apps in the same application pool.
Technically, you only need a single application pool for each .Net version, but really should probably create a separate pool just for MapGuide. This can be shared across all of the MapGuide virtual directories if you want. You can also run MapGuide outside of your default website. Just export the current mapguide virtual directory (or maybe the website) to a config file and then re-import the mapguide virtual directory into the new website. Make sure to set up the alternate application pool before doing this though. Jason -----Original Message----- From: Dave Wilson Subject: RE: [mapguide-users] MG2.0 install with other web applications I believe the issue may be related to the fact that .NET 1.1 and 2.0 apps must each run in their own application pool if I remember something I read a while back. You might have to define separate application pools for each virtual directory. -----Original Message----- From: Xetec Subject: [mapguide-users] MG2.0 install with other web applications I'm looking to find out how to install MapGuide 2.0 server along with other web applications that are installed in the "Default Website" location in the IIS manager? We've run into a challenge with the server not running correctly along side web applications that use .NET1.1. The problem exists after everything is installed. I can log into the admin page and the web studio page, but when I try to connect to the server via MapGuide Studio 2009 beta or AutoCAD Map, I get a connection error. When I change the ASPNET tab to run .NET 2.0 for the mapguide server it makes all the other .NET 1.1 sites lock up and shows an error message in IIS of not being able to run both 1.1 and 2.0 applications in one location. _______________________________________________ mapguide-users mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/mapguide-users
