[mapguide-internals] Access violation registering signal
handler on server startup
mars.wu at autodesk.com
Sun Jan 29 20:21:48 EST 2012
Thanks for the information. I will take a look at this problem.
From: mapguide-internals-bounces at lists.osgeo.org [mailto:mapguide-internals-bounces at lists.osgeo.org] On Behalf Of Trevor Wekel
Sent: Friday, January 27, 2012 1:24 AM
To: MapGuide Internals Mail List
Subject: RE: [mapguide-internals] Access violation registering signal handler on server startup
Ok. I figured it out.
The IPV6 network stack must be installed/enabled on the machine. I am developing on a Windows XP box with only IPV4 enabled. I found a mapguide-internals thread from September where Jackie ran into the same problem. Looks like IPV6 is now a prerequisite even if IPV6 addressing is not being used. Can someone at Autodesk please verify? The thread from September is in limbo.
The workaround is simple - just add IPV6 support to your network adapter.
This issue may affect a large portion of our user base since not everyone will add IPV6 support to their network adapter. Three out of eight PSC members have now tripped over this. I would not be surprised if the same ratio applies to our user base. The support load on Autodesk Support could be fairly large if customers don't get around to reading the release notes.
Zac's post also brings up an interest point with regards to platform support. If IPV6 cannot be enabled on Windows Server 2003, then is may no longer be a valid platform for MapGuide. As near as I can tell, mainstream support for Windows Server 2003 ended in July 2010. Extended support ends in July 2015 so it is still possible that some customers are on Windows Server 2003.
More information about the mapguide-internals