VeryPDF Knowledge Base

You should run pdfprint.exe from an interactive user account instead of default Local System User Account, because Local System User account can't access to network printer, we suggest you may use CreateProcessAsUser() function or RunAs.exe application to run pdfprint.exe from an interactive user account, then pdfprint.exe will able to print your PDF file to network printer properly.

Please refer to following solution, we hoping the following solution will helpful to you,

1. Please download CmdAsUser.exe from following page first,

http://verydoc.com/exeshell.html
http://verydoc.com/download/cmdasuser.zip

2. You can use CmdAsUser.exe to run pdfprint.exe from a special user account, e.g., Administrator user account,

CmdAsUser.exe Administrator . /p password /c "C:\pdfprint.exe" –printer \\verypdf-printerserver\myprinter C:\test.pdf

Please notice, you need modify user name and password in above command line.

3. You can call CmdAsUser.exe from your code to launch pdfprint.exe inside an interactive user account, then you can print your PDF files properly.

You may encounter Error #1314 when you switch the user account, please refer to following solution to solve Error #1314,

~~~~~~~~~~~~~~~
To resolve this issue:
1. Click Start, click Run, type "secpol.msc", and then press ENTER.
2. Double-click "Local Policies".
3. Double-click "User Rights Assignment".
4. Double-click "Replace a process level token".
5. Click "Add", and then double-click the "Everyone" group
6. Click "OK".
7. You may have to logout or even reboot to have this change take effect.

Please refer to two screenshots at below,

http://www.verydoc.com/images/err1314-1.png
http://www.verydoc.com/images/err1314-2.png

"To resolve Error #1314 error, you'll need to elevate the rights of the account calling CreateProcessAsUser() with the "Replace a process level token" right. To do so, open the Control Panel / Administrative Tools / Local Security Policy and add the user account to the "Replace a process level token" right. (You may have to logout or even reboot to have this change take effect.)"
~~~~~~~~~~~~~~~

Sometimes, Windows system can’t map computer name to IP address properly, for example, the following command line may not work in computers,

pdfprint -debug -chgbin 257 -printer "\\verypdf-server\Xerox Global Print Driver PCL"  "c:\temp\verypdf.pdf"

however, after we change the “\\verypdf-server” to IP address, it does work,

pdfprint -debug -chgbin 257 -printer "\\192.168.1.10\Xerox Global Print Driver PCL"  "c:\temp\verypdf.pdf"

so, you should better use IP address to instead of computer name if your system can’t map from computer name to IP address properly.

VeryPDF

Hello,

When using VeryPDF printpdf, it works fine from the windows command line.  However when we shell out to the operating system from within an application, and redirect the io to a file, we see that printpdf cannot find the printer that we are passing to it.  This seems to have begun happening when we moved to a new server.  Please note, if we shell out of the same application and run the –listprinter option and redirect the io to a file we can see that it is listing out the printer we are passing to it.

Please advise,

Thanks,

=========================================

Are you trying to call pdfprint.exe from Windows Service application or non-interactive user account (Local System Account or System account or others)? If yes, please notice an important matter, Service account and system accounts haven't privilege to access to network at default, please refer to following information,

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

In default, Windows does not enable the SYSTEM user account to access to network resources. The easiest method to bypass this is to run your app under a real account (interactive user account) that has network access rights.

If you're utilizing the Win2000 scheduler to start your app, it is possible to alter the account easily, right click your "task", select "Properties" menu item, and change the Run As: account.

If you are being launched by a custom service, change the account the service runs under. In Services, right click the service, select "Properties" menu item, switch to Logon tab, select "This account" and enter the account information.

If you can't do that, you are be able to grant the SYSTEM account privileges to things, see this article,

http://support.microsoft.com/default.aspx?scid=kb;EN-US;132679

and this one,

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q124/1/84.asp&NoWebContent=1

but these are old and you may no longer be able to do this.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

We have another solution to you, you can use VeryPDF CmdAsUser.exe application to run pdfprint.exe from an interactive user account, CmdAsUser.exe can be downloaded from following web page,

http://www.verydoc.com/exeshell.html

http://www.verydoc.com/download/cmdasuser.zip

after you download and unzip cmdasuser.zip to a folder, you can run following command line to print your PDF file to network printer,

CmdAsUser.exe Administrator . /p password /c "C:\pdfprint.exe" -printer "\\192.168.1.10\VeryPDFPrinter" C:\verypdftest.pdf

If you encounter Error #1314 problem with above command line, please refer to the solution of Error #1314 at following web page,

http://www.verydoc.com/exeshell.html

after everything is fine in CMD window, you can call above command line from your Service or ASP or PHP or C# source code, then you can print the PDF file to network printer properly.

VeryPDF