Error When trying to print map
Hi, I am getting below error while trying to print a map
"Print error: Exception has been thrown by the target of an invocation. Insufficient memory to continue the execution of the program."
Settings used: 600 DPI; A0 size(46.81"X33.11")
Is there any configuration that need to be changed to fix this?
0
-
Are you using print jobs?
What if you use a smaller paper size?0 -
Thank you for reply, When I am using 300 DPI with same paper size I am not getting the error and I am not using Print jobs. I am getting this error as an Alert message in the viewer itself. 0 -
Try using print jobs. Web servers and browsers place a time limit on web requests. Normally, reports run with a single request and complete within the time limit. However, reports that are particularly large or contain a lot of data can take much longer. To ensure that a large or complex report does not time out, you can configure the report to be created in the background by clicking the Edit Print Job Settings button. When a report is configured for background creation, you can configure email settings to notify the user when report creation starts and ends. Only PDF reports can be created in the background—the other output formats are not supported for background creation.0 -
Through Print Jobs I am able to achieve it. But the requirement is such that it shouldn't redirect to any other page. Looks like there must be some configuration for setting/increasing time out value for making it happen without using print jobs. If you know one, please share. I will search for the same :) 0 -
Hi Srikanth
Have you found any reasonable solution for your problem?
Our costumer has also this problem with A3/300 DPI printing. (he gets the same error sometimes)
He would like to avoid to use "Print Jobs", and he is asking for if it is possible with doing any changes for exemple on IIS/AppPool settings.0 -
Hi Louise,
I've provided Srikanth with a potential workaround in (https://support.geocortex.com/essentialsGSCForum?sub-nav=forum&main-nav=essentials&feedtype=SINGLE_QUESTION_SEARCH_RESULT&id=90660000000CkYvAAK) this thread , but there's a lot going on there, so I'll repost it here:
There is a way to set a longer timeout via the viewer, but it's not something we recommend, because it can potentially create other problems, like requests that should legitimately time out now taking longer to do so. So, with that caveat...
Edit the viewer's Index.html (typically in C:\inetpub\wwwroot\Html5Viewer). Right at the end of the script element is the call to initialize the viewer:new geocortex.essentialsHtmlViewer.ViewerLoader().loadAndInitialize();Replace this line with this instead:new geocortex.essentialsHtmlViewer.ViewerLoader().loadAndInitialize({ onSiteInitialized: function(app, loader) { geocortex.config.io.timeout = 300 * 1000; // 300 seconds } });As you can see, the timeout variable takes time in milliseconds.
Again, this is not something we encourage, but if you really need to increase the timeout without switching to asynchronous reporting, this will do the trick. Note also that if you increase the timeout to be longer than the server timeout, requests will still time out on the server side.0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
6 Kommentare