Having Print Error frequently (unknown reason but fixed by restart EssentialsAppPool4)
Hello, 
We are running Geocortex 4.6.1 and HTML5 2.7. Almost once every week at least we have trouble to use the out of box print tool and receive the following alert message in the viewer:
Print error: Exception has been thrown by the target of an invocation. The operation completed success.
Restart the EssentialsAppPool4 in IIS then everything went back to normal. I checked Windows Event logs and could find 3 most relevant error about the Application / ASP /.Net (as attached below).Also the server host Geocortex is a 4-core machine with 30Gb memory, where the w3wsp.exe process takes about 1.5gb. Wondering if anyone else had the similar behaviour or could show me any clue that would be appreciated!
regards,
Jack
0
-
Hi Jack,
Interesting! I found a bug that I think might be the culprit (GE-6470), but to help narrow it down, can you please let me know, when this happens, can you still run workflows, or do you get the same error? What about using the export map tool, does that work?
One possible workaround I found that may or may not help (depending on whether the cause is the bug I mentioned above) is to set your App pool to recycle on a schedule (once a day should be plenty).
Thank you!
Danny0 -
Hi Daniel, sorry I've been away for a while. To answer your question yes when the error happens I got same or similar for running any workflows. I’ve set the recycle on EssentialsAppPool4l every night as you suggested, hope it helps. BTW, I also suspect this could be some memory-related. So what would be the recommend virtual memory or memory usage for a 32Gb RAM server to trigger the recycle start? 0 -
Hi Jack,
When the memory on the server is very high, and you don't hit the ceiling often, you may be running into issues with garbage collection not running. I'm afraid we don't have specific recommendations for virtual memory settings, but the memory usage may offer us some clues.
How has the server been running since your last post?
Thanks!
Danny0 -
Hi Jack,
I just saw your post and I'm the original error reporter as far as I know. I set the app pool to recycle every 24 hours and it's much better but not perfect. Our biggest issue is when we get hit with multiple async print requests.
Latitude, has any progress been made on this issue?
Dave0 -
Has there been any updates on this? I too am experiencing this. 0 -
any updates? 0 -
Hi Adam,
This will be an issue until your workflows are converted over to use the new WF5 technology (from the old WF4) or you switch to use the new viewer when it is released. The best thing to do at this point is to try and limit the symptoms by using frequent App Pool recycles and the clean up setting as detailed in another post (search for GE-7972). The issue is inherent to the technology used in WF5 and it cannot be fixed, only managed.
Regards,
Wayne Richard
Latitude Geographics Group Ltd.
Head Office: 300 – 1117 Wharf Street Victoria, BC Canada V8W 1T7
Tel: (250) 381-8130 | Fax: (250) 381-8132 | wrichard@latitudegeo.com
Developers of Geocortex web-based mapping software | www.geocortex.com
An Esri Platinum Business Partner0 -
Thanks Adam, I thought about that too (migrate WF4 to WF5) though it's gonna be a lot of work and some of the functions in WF4 are still not in WF5 (e.g. Export map). We have upgrade our viewer to 2.11 so it's great to know it helps with this issue. 0 -
Hi,
We just started having this issue 2 days ago. When users tries to print they would get an error saying: "Print error: Exception has been thrown by the target of an invocation. The operation completed success".
Doing the IIS Reset on the server where the Essentials is installed would fix a problem, temporarely. But the next day the issue reappeared. We are at Essentials 4.10.0.069 and Viewer 2.11.0. We have been at this version for a while now (about 6 weeks). But the print issue just started happening 2 days ago. It is happening on the sites that have custom print workflow and on the sites that use out of the box print tool.
We have not adjusted our AppPool setting yet, but it will be our next step if it keeps happening. We are just try to understand why it started happening now?
Thank you,
Nataliya0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
9 kommentarer