Software version PDF-Xchange Editor ver 5.5 (build 313.1).
When you run a Terminal Server 2012r2 loaded functional conservation optimized version of PDF, a window appears with the progress, and the cancel button, pressing the cancel button - the program stops responding, you can close it only through the Task Manager - complete the process.
Thanks in advance.
PDFOptimizer.pvp not started on Terminal Server Win 2012r2
Moderators: TrackerSupp-Daniel, Tracker Support, Paul - Tracker Supp, Vasyl-Tracker Dev Team, Chris - Tracker Supp, Sean - Tracker, Ivan - Tracker Software, Tracker Supp-Stefan
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: PDFOptimizer.pvp not started on Terminal Server Win 2012
Hello VMir-St,
Welcome to our forums. Can you please try to explain in a few more words what a "functional conservation optimized version of PDF" is and how exactly are you running this? Are you trying the PDF Optimizer feature through the front end or are you trying to automate some operations?
Regards,
Stefan
Welcome to our forums. Can you please try to explain in a few more words what a "functional conservation optimized version of PDF" is and how exactly are you running this? Are you trying the PDF Optimizer feature through the front end or are you trying to automate some operations?
Regards,
Stefan
Re: PDFOptimizer.pvp not started on Terminal Server Win 2012
I am trying to optimize the pdf
File -> Save Optimized copy ...
out the window, as in the screenshot, and nothing more can be done.
File -> Save Optimized copy ...
out the window, as in the screenshot, and nothing more can be done.
- Attachments
-
- Progress.zip
- Screenshot
- (22.57 KiB) Downloaded 275 times
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: PDFOptimizer.pvp not started on Terminal Server Win 2012
Hello VMir-St,
And if you do not press the Cancel button does the optimization process complete correctly?
Regards,
Stefan
And if you do not press the Cancel button does the optimization process complete correctly?
Regards,
Stefan
Re: PDFOptimizer.pvp not started on Terminal Server Win 2012
If you click Cancel - the button is inactive, close (X) is not active. A modal window does not allow the switch to the main application window, closing is possible only through the Task Manager.
Please simulate the situation, and if you have a program to hang, it means you need to perform work on the bugs, or explain how the system should be set Windows 2012R2 that the program works correctly.
This error appears only when you publish program configured as RDP server Windows.
Thanks.
Please simulate the situation, and if you have a program to hang, it means you need to perform work on the bugs, or explain how the system should be set Windows 2012R2 that the program works correctly.
This error appears only when you publish program configured as RDP server Windows.
Thanks.
Re: PDFOptimizer.pvp not started on Terminal Server Win 2012
Tell me you got to simulate the situation or not? I can provide more data?
We bought 25 licenses in the hope that the program will meet the needs of our close.
We bought 25 licenses in the hope that the program will meet the needs of our close.
- Tracker Supp-Stefan
- Site Admin
- Posts: 17824
- Joined: Mon Jan 12, 2009 8:07 am
- Location: London
- Contact:
Re: PDFOptimizer.pvp not started on Terminal Server Win 2012
Hello Vladimir,
I managed to reproduce this on a WS2008, so we are currently investigating why this is happening.
Regards,
Stefan
I managed to reproduce this on a WS2008, so we are currently investigating why this is happening.
Regards,
Stefan
- Roman - Tracker Supp
- Site Admin
- Posts: 303
- Joined: Sun Nov 21, 2004 3:19 pm
Re: PDFOptimizer.pvp not started on Terminal Server Win 2012
Hello,
The issue has been investigated and will be addressed in the next release of the editor.
Until then, please set Edit->Preferences->Performance->Maximum number of working threads allowed option to be equal or more than 2 (but not more than the double number of the machine CPU cores).
This should workaround the problem.
The issue has been investigated and will be addressed in the next release of the editor.
Until then, please set Edit->Preferences->Performance->Maximum number of working threads allowed option to be equal or more than 2 (but not more than the double number of the machine CPU cores).
This should workaround the problem.