Critical Viewer Error

Permanently deleted user

22. Februar 2014 02:44

Afternoon,

Trying to reestablish some new data connections, search tables and data connections. But when I import these items from a workable Essentials site, I receive this critical error and the viewer will not load. The error is below:

 

2/21/2014 06:43:49:355: CRITICAL: Unhandled exception occurred: Geocortex.EssentialsSilverlightViewer.Infrastructure.Exceptions.CriticalViewerException: Cannot open configuration file. ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]

 

   at App.OnUnhandledException(Object sender, ApplicationUnhandledExceptionEventArgs e) Geocortex.EssentialsSilverlightViewer.Viewer

 

   at EventHandler`1.Invoke(Object sender, TEventArgs e) System

 

   at Errorstatic .CallApplicationUEHandler(Exception e) MS.Internal

 

   at Errorstatic .GetXresultForUserException(Exception ex) MS.Internal

 

   at DispatcherOperation.Invoke() System.Windows.Threading

 

   at Dispatcher.Dispatch(DispatcherPriority priority) System.Windows.Threading

 

   at Dispatcher.OnInvoke(Object context) System.Windows.Threading

 

   at CallbackCookie.Invoke(Object[] args) System.Windows.Hosting

 

   at ManagedHoststatic .InvokeDelegate(IntPtr pHandle, Int32 nParamCount, ScriptParam[] pParams, ScriptParam& pResult) System.Windows.RuntimeHost

   Details:

 

   Arguments: NotFound

 

   Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.0.61118.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer ---> System.Net.WebException: [HttpWebRequest_WebException_RemoteServer]

 

   Arguments: NotFound

 

   Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.0.61118.0&File=System.Windows.dll&Key=HttpWebRequest_WebException_RemoteServer

 

      at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)

 

      at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa.<EndGetResponse>b__9(Object sendState)

 

      at System.Net.Browser.AsyncHelper.<>c__DisplayClass4.<BeginOnUI>b__1(Object sendState)

 

      --- End of inner exception stack trace ---

 

      at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)

 

      at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)

 

      at System.Net.WebClient.GetWebResponse(WebRequest request, IAsyncResult result)

 

      at System.Net.WebClient.OpenReadAsyncCallback(IAsyncResult result)

 

      --- End of inner exception stack trace ---

 

      at Geocortex.EssentialsSilverlightViewer.Infrastructure.Configuration.ConfigurationTree.WebClientOpenReadCompleted(Object sender, OpenReadCompletedEventArgs e)

 

      at System.Net.WebClient.OnOpenReadCompleted(OpenReadCompletedEventArgs e)

 

      at System.Net.WebClient.OpenReadOperationCompleted(Object arg)

 

Walter

0

• 

  Permanently deleted user

  22. August 2012 20:10

  The problem is because the file is lock for some raison by iis...just reset your iis service in the prompted windows with this command ---:  iisreset

   

  0
• 

  Permanently deleted user

  22. August 2012 20:15

  Will try, many thanks

  0
• 

  Permanently deleted user

  22. August 2012 20:23

  I reset IIS and it fixes the problem.  My question is, why is IIS locking the viewer in the first place? Also this seems to be an ongoing issue, am I going to have to reset IIS all the time? This is happen about every other day.

  Many Thanks,

  0
• 

  James Landwehr

  22. August 2012 20:32

  Craig,

   

  The initialization error is our most common complaint among users, especially after an upgrade. It seems there can be a conflict if a browser is looking for an older .xap file than the site is currently running. It is outlined in the thread at:

  http://support.geocortex.com/Forums/Thread.aspx?pageid=0&mid=2&ItemID=7&thread=46721

  We've followed these instructions and it seems to help a bit. The only problem is every time we upgrade, we have to revisit this workaround. 

  0
• 

  Permanently deleted user

  22. August 2012 20:47

  Thanks Jim,

  That was an interesting read and we have had the same thing happen, vary useful to know the workaround (although not ideal).

  The issue I am having however is different (at least I think), even after I clear my cache I still cannot access the viewer (get an error), or edit the viewer inside of essentials. I have always said that it seems like it is locked by something, which makes Gilles suggestion about IIS make sense.

  Many Thanks,

   

  0

Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.