As readers of Ashley Buzzeo’s latest blog post already know, Towson University’s Center for GIS (CGIS) has migrated its hosted ArcGIS Servers from ArcGIS Server 9.3 to ArcGIS Server 10. As the migration took place all GIS services were reviewed to make sure they were functioning properly. While most services were converted without issue a handful would not start post-migration. After several hours of troubleshooting, the problem was identified as being related to a unique subset of WFS-enabled map services.
What was interesting about this problem was that several WFS-enabled map services worked properly after the migration while a few did not. Knowing this, I knew that the problem’s solution existed in understanding how the functioning and malfunctioning WFS-enabled map services differed. By comparing the information contained in the REST endpoints for a functioning and malfunctioning WFS-enabled map service I noticed one difference: the functioning WFS-enabled map service had unique field aliases while the malfunctioning WFS-enabled map service had two fields that had the same alias. Making the malfunctioning map service’s field aliases unique solved the problem as I was able to start the service and confirm it worked properly. All the other malfunctioning WFS-enabled map services were also explained by duplicate field aliases.
While this blog touched on only one issue related to ArcGIS Server 10 migration, there are many other issues that one may experience. Visit ESRI’s Migration to ArcGIS Server 10 page as a starting point for answers to other migration-related questions you may have.

Posted by Jeremy Monn 
















