We have a Windows Service that watches a folder for PDF files to be deposited. Once awakened, it executes the Adobe Reader in command line mode to print the PDF files to secure check printers. The Windows Service was working fine with 11.0.06.70 but no longer works with 11.0.07.79.
There are no event viewer errors or errors returned to our Process.Start() call. The Windows Service is running under the identify of an administrator account and has explicit full access to the printer. We have also tried the local computer's Administrator account as well as the default Local Service, but none work.
Using ProcMon to examine the failure, it showed Adobe Reader making many successful registry and file accesses. Adobe Reader then creates a new process, another instance of itself to read in the PDF file and print to the printer. However, ProcMon only shows Adobe Reader accessing AcroRd32.exe, syswow.dll (sp) and ntdll.dll and then the thread and process immediately exits with an exit code of 0 (no file or registry accesses). So, something is causing the instantiated process to fail immediately.
After more research and trying many things, we disabled "Enable Protected Mode at Startup". This enabled things to work again.
We are concerned that disabling this feature might expose security concerns for our customers.
We are suspecting that some security concerns were tightened with 11.0.07.79 that has inadvertently caused printing from Windows Services to falsely be identified as security violations. Can you please investigate and provide a resolution?
Thank you.
Craig Keating
Alliance Enterprises, Inc.
Hi,
Can you please give the following details:
1) Command (given in command line)used to print PDF files?
2) Is the issue reproducible with other printers as well?
3) Is directly printing the PDF from that folder using command line i.e without using windows service works fine or not?
Thanks,
Shakti K