[Solved] Unable to CoCreateInstance on CDIntfEx on Win64

[Inferno]

Hi,

We're running Windows 2003 SP2 x64 Edition.

I have installed PdfDrv300DemoEn.exe, and have tried the registered version of 3.00 that we have as well. Both installs are failing on the CoCreateInstance for CDIntfEx, we get a null interface back, and the error is 0x80040154 (E_CLASSNOTREGISTERED).

I traced it down, and on the 64-bit machine, CDIntfEx is registered with the CLSID of {68B34269*. This does not seem right, on Win32, it is {68B34268*.
I am using a 32-bit C++ client.

Is there an error with the installer I am using? Is this a known issue?

Thanks,
Sameer

[Joan]

Hello,

On which port are you installing the Printer?

If you are installing it on LPT1: port, please create a new port, call it 'NUL:' and attache the printer to it.

Then relaunch your application.

[Inferno]

Just to let you know, I tried using the NUL: port, and I also tested with your C# Test Application. I get the same error (I have attached an image of the error).

It seems that the version I am installing is not installing correctly on Windows 2003 64-bit edition (the GUID for the class CDIntfEx is incorrect in the registry).

[Inferno]

Ok, it seems that the CDIntfEx version 3.00 is not compatible with the one from CDIntfEx version 2.5, and therein lies my guid problem. I can get it to start printing and create the pdf file now, but in the print spooler, the document says "error" and the file is 0 bytes in length.

[Joan]

Hello,

I will post here the answer you got from our Technicals Support team in case other users are facing this same issue.

To resolve the issue that you posted on the forum, we suggest that under 64bit installation you slightly modify how your applications install the PDF Converter:

These steps are only run once by the Admin user:

- Install PDF Converter as before.
- Programmatically create a new local port (giving the port any custom name such as AmyuniPDF)
- Attach the PDF printer to the custom local port

Hope this helps

[Inferno]

I'm still fighting this issue, I have tried creating new local ports, both by the names "NUL:" and "AmyuniPDF" as suggested, both give me the same "error - printing" on the queued document. I have (not been able to, see below) include a screenshot detailing the problems we are seeing, and showing the custom port association. Please let me know if you have any other suggestions, or debugging techniques.

Hmm, I can't seem to upload the screenshot, the forum says "could not upload attachment to ./files/12358_c4f0f6cee6fb7aba5a63219191db0fa5".

[Inferno]

FYI, the solution to this problem was to check "Spool print documents so program finishes printing faster" instead of "Print directly to the printer" in printer properties for the Amyuni printer driver.

[Joan]

Hello,

Thank you for posting the solution here.

I will check why you are not able to upload an attachment. Maybe i have disabled uploading attachments when setting this forum.

I will let you know.