Essentials 4.0 Rest Endpoints not working

Marc Rempel

February 06, 2014 00:07

Hi,

I just upgraded to 4.0 and my rest endpoints do not show and throw a 500 internal server error.  Any tips?

 

Marc

0

• 

  Marc Rempel

  February 06, 2014 03:07

  I found the problem with my installation.

  My previous installations of Essentials have been on a drive other than c at the suggestion of our sys admin.  The new Geocortex installer did not allow me to point to a non- c drive installation which then created some odd behaviours in upgrading my existing site.  I ended up manually migrating my sites to a c installation location and then having to remap all of the viewer configs to the new rest endpoints. 

  Marc

  0
• 

  Stefan Schweigert

  February 06, 2014 03:42

  Hello Marc,

  Could you take a look at your REST web.config file and look for a <add /> parameter in your configuration? 

  If that parameter is present, removing it should resolve the issue.

   

  Thanks,

   

  Stefan

  0
• 

  Marc Rempel

  February 06, 2014 03:52

  Thanks for the response Stefan.  I did have a <add /> in my web.config.  Removing it did not clear up my issue however.  It seems to have been related to the previous installation location not being on the C: drive.

  Regards,

  Marc

  0
• 

  Permanently deleted user

  February 07, 2014 00:48

  I had the same thing after upgrading a 3.15.1 instance to 4.0 this morning.  Deleting the empty <add /> worked for me.  Thanks for the tip Stefan.

  Nate

  0
• 

  Permanently deleted user

  February 07, 2014 01:40

  I also upgraded this morning and have run into this same issue. I cannot build any new sites because it is referencing an unknow rest.

  I did upgrade my existing site which was installed on a different drive than the C.  I have checked the rest web.config file and have not found a <add />. I have noticed that the url the entire application is now referencing is not the same as the old Default web page.

  From manager I cannot get to any rest endpoints.

  Example: Old site  http://coagispsom1/COASilverlight1_5/ still works fine and the old viewers still work from the upgrade

  New site http://coagispsom1.(Fully Qualified Domain)/SilverlightViewer_2_0/ any new silverlight viewers or sites from the manager reference the fully qualified name and cannot access the rest or crossdomain.xml file.

  Any thoughts?

  0
• 

  Permanently deleted user

  February 07, 2014 03:05

  This frustrated me for a long time, but it turned out the removing the add and doing an iisreset worked for me.

  The webconfig should be in this location once you remove the <add /> you may need to do an iisreset.

  C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\REST

  0
• 

  Permanently deleted user

  February 07, 2014 22:50

  Just as a note I had 2 references of <add /> in the webconfig, thanks all for this post as it sure saved me some time...

  0
• 

  Marc Rempel

  February 08, 2014 06:27

  Just to close the cirlce on this one.  So after I uninstalled Geocortex 4 from my default location and then re-ran the installer, i saw the option to have a custom install which allowed me to then point to my E: drive for installation.   The installation completed and then after removing the <add /> and two other notOverwrite="True" from REST the web.config, I was able to get things running again in my default location.   I couldn't change the install location just by re-running the installer again without having removed my first upgrade.  Anyway, hope this helps someone else.

  Regards,

  Marc

  0

Please sign in to leave a comment.