Map Service not working in Essentials 3.2
I just updated from Essentials 3.1 to 3.2 and when I did the map service for my site would no longer load. This is the error message that Essentials REST Manager was giving me:
The configuration model failed conversion to its business logic layer representation. The following validation errors were encountered:
- An error occurred during initialization of map service "PandRCortexTest2" (ID: "0"). The connection settings may be incorrect of the map service may be temporarily unavailable.
- An error occurred during initialization of map service "PandRCortexTest2" (ID: "0"). The connection settings may be incorrect of the map service may be temporarily unavailable.
This map service was working with Essentials 3.1. I tried to delete the site and recreate and tried to reload the service into the site but it still gave me the same error message. The map service also works fine in my webADF site. Has anyone else encountered the same message or have a solution to my problem?
Thanks,
Thomas
0
-
Hi Thomas, Is your map service available over the Internet? If so, can you send us its address so we can test it from here? Otherwise, can you capture the JSON response for your service and send it to us? Thanks! -Malcolm 0 -
Here is the json from the map service when I look it up through Arc Server:
{ "currentVersion" : 10.01, "serviceDescription" : "", "mapName" : "Layers", "description" : "", "copyrightText" : "", "layers" : [ { "id" : 0, "name" : "Villages", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 250000, "maxScale" : 0 }, { "id" : 1, "name" : "Counties_Eastern_ON", "parentLayerId" : -1, "defaultVisibility" : false, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 2, "name" : "SNC_Township_Boundaries_2009_12_15", "parentLayerId" : -1, "defaultVisibility" : false, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 3, "name" : "SNC Flood Plain", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 4, "name" : "SNC Forest Properties", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 5, "name" : "Eastern_ON_Boundry_Clip", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 6, "name" : "Roads", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 7, "name" : "SNC Boundary", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 8, "name" : "Water Body", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 9, "name" : "Water Course", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 64000, "maxScale" : 0 }, { "id" : 10, "name" : "Concessions", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 128000, "maxScale" : 0 }, { "id" : 11, "name" : "Lots", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 128000, "maxScale" : 0 }, { "id" : 12, "name" : "Railway", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 0, "maxScale" : 0 }, { "id" : 13, "name" : "Building_Symbol", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 4000, "maxScale" : 0 }, { "id" : 14, "name" : "Wetland", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 128000, "maxScale" : 0 }, { "id" : 15, "name" : "Contour_Lines", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 24000, "maxScale" : 0 }, { "id" : 16, "name" : "Building_to_Scale", "parentLayerId" : -1, "defaultVisibility" : true, "subLayerIds" : null, "minScale" : 24000, "maxScale" : 0 } ], "tables" : [ ], "spatialReference" : { "wkid" : 26918 }, "singleFusedMapCache" : false, "initialExtent" : { "xmin" : 390742.329778449, "ymin" : 4967316.46720598, "xmax" : 589656.477606744, "ymax" : 5067329.16723138, "spatialReference" : { "wkid" : 26918 } }, "fullExtent" : { "xmin" : 420524.6243, "ymin" : 4929278.3837, "xmax" : 548290.411264714, "ymax" : 5054608.40284782, "spatialReference" : { "wkid" : 26918 } }, "units" : "esriMeters", "supportedImageFormatTypes" : "PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP", "documentInfo" : { "Title" : "", "Author" : "", "Comments" : "", "Subject" : "", "Category" : "", "Keywords" : "", "AntialiasingMode" : "None", "TextAntialiasingMode" : "Force" }, "capabilities" : "Map,Query,Data" }
Not sure why is stopped working when I did the update but it was definitely working with 3.1.
Thanks,
Thomas0 -
Has anyone else encountered this problem and/or found a solution to it. I still cannot get my map services to work with REST manager but they work with webADF. This problem started when I upgraded from essentials 3.1 to essentials 3.2.
I would really like to find a solution to this problem so I can start working with REST services again.
Thanks
Thomas0 -
Do you get the same error with every map service? What happens if you publish a test service with one layer and create an Essentials REST site to point that service? If it works with the test service then the problem could be a bad layer in the PandRCortexTest2 service. Try restarting the map service and checking the AGS logs for any Invalid Layer messages. ADF sites would handle bad layers by simply removing them from the site. REST sites however, will display the error mentioned above. 0 -
It does work with a Test site so it probably is one of the layers. The thing that I don't understand is that the PandRCortexTest2 works with Essentials REST 3.1. It does not work with 3.2 and 3.3. I don't know what changes were made during the updates that caused the site to stop working. I will probably have to remake the msd that the site is based off of and try to get something working with 3.2 and 3.3 0 -
Hi Thomas,
It would be really useful if I could get access to your site directly. In the absence of that, could you check the logs for any kind of useful looking error messages?
Also, try creating a brand new site in REST Manager, and add that service. See if it tells you anything more useful (or works) when you do that.
Jeff
0 -
Hi
Was there a solution to this - I am having hte same problem but in Essentials 3.4.1 and with newly created map services - older map services work ok.
Thanks
Caroline
0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
7 Kommentare