Print not working in 3.13

March 05, 2013 02:58

Updated to 3.13 on Friday and was notified that the printing is not working anymore. It gives this error, "The print operation could not be completed succesfully. Please contact your system administrator for assistance." Can I roll back to 3.12 by just running the 3.12 installer?

Comments

22 comments

Marc Rempel

March 05, 2013 04:16
I found the problem was related to a service that we have that is not displayed in the layerlist, but is set to be visible (it is a cartographic mask layer to focus on area of interest). It was not selected to be displayed in the legend, which was the source of the problem. Once I enabled it to be displayed in the legend, the print worked again. It must be a new check that was added in 3.13 since it was working before we upgraded.

Regards,

Marc
0
Ryan Cooney

March 05, 2013 06:37
Hi Marc,

Did you see a stacktrace or anything interesting in the REST logs that could help us diagnose this issue?

--Ryan
0
Marc Rempel

March 05, 2013 07:08
Ryan,

This is what showed up in the logs:

03/04/2013 11:06:36:571: ERROR: System.Runtime.Serialization.SerializationException: Exception has been thrown by the target of an invocation.

   at PrintTemplatesView.OnError(Exception ex) Geocortex.EssentialsSilverlightViewer.CoreModules.PrintTemplates

   at PrintTemplatesView+<>c__DisplayClassa.<SendRequest>b__4(Object sender, PrintCompletedEventArgs e) Geocortex.EssentialsSilverlightViewer.CoreModules.PrintTemplates

   at WebMap.OnPrintCompleted(PrintCompletedEventArgs e) Geocortex.Essentials.Client.Integration

   at WebMap.FinishPrint(Object sender, ExecuteRestCallResult result, Boolean cancelling, Object userState) Geocortex.Essentials.Client.Integration

   at WebMap+<>c__DisplayClass1.<PrintAsync>b__0(ExecuteRestCallResult x) Geocortex.Essentials.Client.Integration

   at RestHelperstatic .ExecuteRestCall_ProcessResults(AsyncCompletedEventArgs e, String resultString) Geocortex.Essentials.Client

   at RestHelperstatic .ExecuteRestCall_DownloadStringCompleted(Object sender, DownloadStringCompletedEventArgs e) Geocortex.Essentials.Client

   at WebClient.OnDownloadStringCompleted(DownloadStringCompletedEventArgs e) System.Net

   at WebClient.DownloadStringOperationCompleted(Object arg) System.Net

   at RuntimeMethodHandlestatic .InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor) System

   at RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) System.Reflection

   at Delegate.DynamicInvokeImpl(Object[] args) System

   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:

   Object reference not set to an instance of an object.
Marc
0
Permanently deleted user

March 05, 2013 21:31
Ryan, we are also experiencing a similar issue with print layout not working with 3.13. It seems to be isolated to print templates with legends.

We're trying to find a work around right now, other then removing the legends from all our print templates...

-Alex
0
Ryan Cooney

March 06, 2013 04:23
Hi Marc,

Thanks. The stacktrace you provided is the one from the viewer. It appears to just report an error that originated on the server. Do you see anything in your Essentials logs found here "C:\Program Files (x86)\Latitude Geographics\Geocortex Essentials\<instance>\REST Elements\REST\App_Data\Logs"?

--Ryan
0
Marc Rempel

March 06, 2013 04:31
Ryan, this is what was in the logs.

<Event Timestamp="2013-03-04T15:06:36.0796842-08:00" Level="ERROR" Identity="Guest"><Message>Exception has been thrown by the target of an invocation.

Object reference not set to an instance of an object.</Message></Event>
Marc
0
Ryan Cooney

March 06, 2013 07:32
Thanks to everyone for their contributions. We have been able to replicate the issue here. This appears to be isolated to cases where a print request includes at least one visible layer for a particular service but excludes all layers from the legend for that service. We will have this fixed for the next release.

The reference number for this issue is: GE-2964.

--Ryan
0
Permanently deleted user

March 06, 2013 07:35
thank you Ryan

-Alex
0
James Landwehr

March 11, 2013 20:36
We are experiencing this issue too and need a quick fix as it has disabled the ability to print. Does anyone have a quick workaround as we don't have time to wait for a release or patch.

Thanks.
0
Marc Rempel

March 11, 2013 21:59
I had to determine which layer that we have that is displayed on the map but set to not display in the legend and enable it to be seen in the legend and that cleared it up for us. Hope that helps.

Marc
0
James Landwehr

March 11, 2013 22:04
Thanks Marc. My short-term solution was to take legends out of my templates. I'll look at trying to implement your suggestion until we get a patch.
0
Chris Dunlop

March 11, 2013 22:25
It also happens if you have a map service turned to visible, but none of the layers in that map service are visible.

Chris
0
Marc Rempel

March 14, 2013 00:17
I found another wrinkle that may or may not be related. I found that if I have a map theme selected that the error also happens. Could be a symptom of the same issue Ryan has identified, but wanted to make sure that it gets tested in the map theme context as well.

Marc
0
Permanently deleted user

March 20, 2013 01:54
Wow, big problem! We're having the same issue with Printing. Is it possible to roll back to 3.12? Removing all the legends or showing all layers on the map aren't really great options for us.

Thanks.

Niki
0
Permanently deleted user

March 21, 2013 11:26
I totally agree - big problem.

Removing all the legends or showing all layers on the map are also not really great options for us.

Any chance on getting a fix for this asap? Or instructions on how to roll back asap?
0
Permanently deleted user

March 21, 2013 22:38
Latitude provided instructions for me to roll back to 3.12. It was very easy and worked for me.

Here are Malcolm Walker's instructions:

You should be able to do this quite easily with just the Essentials installer.

Make a backup of the Sites folder before you begin. Then, uninstall Essentials 3.13 and install Essentials 3.12 into the same folder location. Run the post install for Essentials 3.12 and everything should work fine.

Any new tags introduced by the 3.13 upgrade will be ignored by 3.12.

Good luck!

Niki
0
James Landwehr

March 27, 2013 22:08
Unless a fix is imminent, it looks like I will need to rollback as well. Users are beginning to complain.
0
Ryan Cooney

March 31, 2013 12:24
A fix is coming. It should just be a matter of days.

--Ryan
0
Permanently deleted user

April 30, 2013 07:34
Hi Ryan,

Just wondering if the hotfix is available to download? THanks

regards,

Jack
0
Ryan Cooney

April 30, 2013 23:15
Hi Jack,

The fix for this issue was included in the 3.14 release.

--Ryan
0
Permanently deleted user

May 02, 2013 20:20
Thanks Ryan, unfortunately we can't use 3.14 as it has some issue with display map service with Cad data(we downgrade from 3.14 to 3.13).
0
Ryan Cooney

May 02, 2013 23:41
Hi Jack,

Cad Annotation Layers and Cad Feature Layers are supported with Hotfix 2 for 3.14.

--Ryan
0

Please sign in to leave a comment.

Print not working in 3.13

Comments

Didn't find what you were looking for?