PDFDriverInit() failed on RDP server

The Amyuni PDF Converter is our Printer Driver that enables you to convert any documents to PDF format. If you have any questions about installing and using the Amyuni PDF Converter please post them here.
Post Reply
Posts: 27
Joined: Thu May 17 2007

PDFDriverInit() failed on RDP server

Post by danadanny » Tue Jan 08 2013

I am trying to create a pdf printer from my application for each user logged onto the RDP server. The plan is to have each pdf printer is named slightly differently, ie, based on the RDP session ID, eg, user 1 has RDP session id of 123, the pdf printer will be named "MyPdfPrinter#123" and so on.

The pdf driver was initially installed on the RDP server as part of my application's installation package using the "Install.exe -s "MyPdfPrinter" -n "MyLicence" -c "xxxxxxx" command. The distributable files are copied to "C:\myapplication\amyuni" folder before calling "install.exe ...." command. This is working fine until we decided to create a pdf printer for each logged in user.

When I called the PDFDriverInit() method, I get the following error message:

I have given the logged in user administrative rights, ie, the user account is part of the local administrators group of the RDP server. All the distributable files have been copied to both SYSWOW64 and System32 folders. I have manually registered both "System32\cdintf450_64.dll" and "SysWOW64\cdintf450.dll".

OS: Windows Server 2008 R2 64 bit.
Amyuni version

Any help would be greatly appreciated. Thank you.

Amyuni Team
Posts: 550
Joined: Tue Oct 01 2002

Re: PDFDriverInit() failed on RDP server

Post by Jose » Mon Jan 14 2013


The PDFDriverInit() function will install the Amyuni PDF Converter printer on a user’s system and this printer will be removed at the end of your application when calling DriverEnd.

The PDFDriverInit() function needs to be called at the beginning of your application (and not each time you print) and DriverEnd should be called at the end of your application (and not when printing ends).

If users doesn't have administrative or power rights to add and remove a printer from their system PDFDriverInit() will fail.

In this case you can install the printer on your system using Install.exe (Install.exe should be run by an administrator) and inside your application you replace PDFDriverInit by DriverInit (the printer will remain on the system even when the application ends).

The DriverInit() function will take as parameter a string containing the printer name as it appears in your printers' folder.

For easier maintenance, it advisable to give to the printer a name related to your company.

Please note that:
Install "My Printer" : Will install a printer called "My Printer" on the system.
Install -s : Will install the printer in silent mode.

Get PDF Suite, the expert .NET developer toolkit for PDF conversion, creation and editing - www.amyuni.com/pdfsuite

Post Reply