wkhtmltopdf Performance and Execution Issues in WebSpeed vs prowin32

Chad

New Member
OEv11.7 / Windows 11

Hi all,

I'm using wkhtmltopdf.exe from webSpeed to convert HTML files to PDFs. While everything works perfectly when run via prowin32.exe or _progres.exe. However, I’m hitting two key problems when executed inside a WebSpeed agent:

Problem 1: Extremely Slow Execution in WebSpeed

When I call wkhtmltopdf using OS-COMMAND from a WebSpeed agent, it takes 60–90 seconds to complete, despite the same command running in under a second when called directly running from a batch file or executing from app builder.

Example code:

DEFINE VARIABLE cCommand AS CHARACTER NO-UNDO.
ASSIGN
cCommand = "C:\path\to\wkhtmltopdf.exe " +
"--enable-local-file-access " +
"C:\temp\input.html C:\temp\output.pdf".

OS-COMMAND SILENT VALUE(cCommand).


Problem 2: No Execution When Broker Runs Under My Admin User

If I configure the WebSpeed broker to run under my personal (admin-level) user account, the wkhtmltopdf command doesn’t run at all — no error, no output, no logs.

However, if I run the broker as LocalSystem, the command executes, but still with the 60–90 second delay.


Questions:

Has anyone encountered this execution delay in WebSpeed?

Are there known restrictions in WebSpeed’s OS-COMMAND context?

Is there a better architectural pattern for offloading command-line tools from WebSpeed?
 
Last edited:
I'm going to ask an obvious question. Whatever procedure/method/function that is outputting to C:\temp\input.html, has it closed the output stream before calling the OS-COMMNAD?

Do you still have the performance issue when creating a PDF from a URL i.e. ?
 
Back
Top