Essentials Manager Problems

Permanently deleted user

February 22, 2012 02:22

Came in from a long holiday weekend to find our main site won't load and Essentials Manager won't run without script timeouts. We can't even see the sample sites at present. We're running version 3.4.1 and no updates have been tried. I finally got my site to refresh and opened it to find it couldn't connect to some services, though I can at the REST end point. Nonetheless, even after removing those services and saving the site, I cannot load the application.

My system log from this morning shows a number of errors, starting with:

<Event Timestamp="2012-02-21T06:52:40.4066202-08:00" Level="ERROR"><Message>Unable to read the REST application settings file at path "\RestAppSettings.xml". The following error occurred: Unable to deserialize the given XML configuration to an object for the following reason: "There is an error in the XML document.".</Message></Event>

 

<Event Timestamp="2012-02-21T06:52:43.9221777-08:00" Level="ERROR" Identity="Super"><Message>Validation failed while loading the site configuration file at path "\Charlotte\Site.xml". The following validation errors were encountered:

 

- [Site (ID: "Charlotte")/DataConnections/DataConnection (ID: "0")]: The Display Name field is required.

 

- [Site (ID: "Charlotte")/Map/MapServices/MapService (ID: "Charlotte")/Layers/Layer (Name: "Zip Codes")/FeatureMaps/FeatureMap (ID: "ZipCodeFeatureMap")]: The Display Name field is required.

 

- [Site (ID: "Charlotte")/Map/MapServices/MapService (ID: "Charlotte")/Layers/Layer (Name: "Parcels")/FeatureMaps/FeatureMap (ID: "ParcelFeatureMap")]: The Display Name field is required.

 

- [Site (ID: "Charlotte")/Map/MapServices/MapService (ID: "Charlotte")/Layers/Layer (Name: "Parcels")/FeatureMaps/FeatureMap (ID: "ParcelOverviewFeatureMap")]: The Display Name field is required.

Errors reading XML files run throughout, yet they haven't been changed recently.The RestAppSettings.xml, for example, dates from 4/20/2010.

Need help troubleshooting, please.

 

 

0

• 

  Permanently deleted user

  February 22, 2012 02:32

  Martha,

  If you're running Windows Server 2003, check to see if both ASP.NET v2 and ASP.NET v4 web service extensions are set to allowed.  

  Also check the application pools in IIS to make sure they are all started.

  Steve

  0
• 

  Permanently deleted user

  February 22, 2012 02:42

  Steve,

  We are running Windows Server 2003. All Application Pools claim to be running and, in the Web Service Extensions folder I see both ASP.NET v2.0.50727 and ASP.NET v4.0.30319 are set to Allowed.

  What shall I check next?

  Martha

  0
• 

  Permanently deleted user

  February 22, 2012 03:06

  Is the REST endpoint you are able to see the ESRI rest endpoint or the Geocortex REST endpoint?  Or both?

  Also check to make sure none of the accounts associated with GE and AGS are locked out.  Do you have any security applied to the site?  If so, you might want to try disabling it until you get this sorted out, though if you don't have access to the REST manager, you will have to work in the site.xml file.

  Something you might want to try to establish a baseline would be to create a new instance on the server to see if that works.  That would at least tell you if the problem is at the server level or within the GE instance.

   

   

   

   

  0
• 

  Permanently deleted user

  February 22, 2012 03:42

  Steve,

  I'm speaking of the ESRI REST endpoint.I don't seem to be able to see the site in the Geocortex REST endpoint. Here's the message:

  Server Error in '/Geocortex/Essentials/REST' Application.

   

  --------------------------------------------------------------------------------

  Request timed out.

   

  Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

  Exception Details: System.Web.HttpException: Request timed out.

  Source Error:

  An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. 

  Stack Trace:

   

  [HttpException (0x80004005): Request timed out.]

   

   

  --------------------------------------------------------------------------------

   

  Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272

  I have opened a ticket now and have sent some XML files to Malcom and Jonathan. Anxious as I am to get this going again, I don't want to overuse the resources there.

  I will look into the remainder of your comments and see where I get with that. Thank you so much for your rapid response.

  Martha

  0
• 

  Permanently deleted user

  February 22, 2012 04:06

  You're welcome, Martha.  Best of luck to you resolving this!

  0

Please sign in to leave a comment.