Silverlight Viewer Not Working 4.2 Upgrade

Permanently deleted user

October 10, 2014 03:21

I recently upgraded Geocortex Essentials 3.14 (Silverlight 1.91) to Geocortex Essentials 4.2 (Silverlight 2.3) on our test server (Windows Server 2012 R2). After the installation I ran the test URL to test the Silverlight viewer and it worked (http://localhost/Geocortex/SilverlightViewer/viewer.html). However, when I attempt to view a site within Manager I get an error ("Critical Viewer Error – An error occurred during initialization and the Viewer could not be started. This may be due to network connectivity problems, viewer configuration problems, or site configuration problems". When viewing the log from the error it shows “Silverlight version 1.9.1.2” still for some reason. Also says “….cannot load Xaml resource…”. Any ideas??

I tried a whole bunch of troubleshooting, without luck. It appears that Manager is still referencing SilverlightViewer 1.9, even though in the site viewer details it shows 2.3 and it appears SilverlightViewer 2.3 is working because the test URL worked. I want to note that when the doesn't work, the loading screen looks different, the old version "Your organization name here". The test site (which worked) the loading screen looks updated.

Any help is greatly appreciated!!

0

• 

  Permanently deleted user

  October 10, 2014 03:38

  We had issues with the Silverlight viewers as well upgrading from 4.0 to 4.2 (Silverlight 2.0 to 2.3).

  There was something wrong with some of the configurations files referencing the wrong viewers.Some files to check:

  C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Manager\App_Data\RestManagersettings.xml

  C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\Default\REST Elements\Sites\Templates/Templates.xml

  A suppor tperson got us sorted. Seemd to be an issue going from an older verison to 4.2 rather than teh last I think?

  0
• 

  Permanently deleted user

  October 10, 2014 22:46

  Thanks for the suggestion. I checked and it looks OK. I'll most likely have to open a ticket with Support.

  Any other ideas?

  If I find out something in the mean time, I'll post.

   

  0

Please sign in to leave a comment.