Class not registered Exception

[rn101506]

We are receiving below exception while generating PDF document using PDF-Xchange Library. I checked in registry. the class exists. this error will disappear after reinstalling PDF-Xchange. Please help.

Retrieving the COM class factory for component with CLSID {217974DB-6777-4A9F-90A7-AA5EBA834BA2} failed due to the following error: 80040154 Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

what we did is
(1) Install our application ( PDF-Xchange is embeded into it).
(2) generate PDFs
(3) Uninstall our application
(4) Resintall our application .
(5) reboot the computer
(5) Try to generate PDFs. Throws class not registered exception.

[Paul - Tracker Supp]

Hi rn101506,

thanks for the post. One of the developers will look at this tomorrow. Sorry for the delay - there are some heavy deadlines right now demanding attention.

I hope that will be OK at your end.

regards

[rn101506]

Any updates on this please. this is little urgent.

note: this is happening only on 64 bit machines.

[Nico - Tracker Supp]

Hi rn101506,

Thank you for your post.
Please could you tell us the following:

• Version and build number of PDF-XChange Drivers API you are using
• Operating System version and architecture, service pack#
• How you are installing the drivers API? what installation package are you using? (.exe, redistributable, .msm, etc)
• Please try to register pdfSaver4.exe by typing: pdfSaver4.exe /regserver and verify it is registered in the system
  Thanks.
  
  Sincerely,

[rn101506]

Here are the details

PDF File Description : pdfSaver for PDF-XChange 4.0
PDF Prodcut Version: 4.0
PDF File Version : 4.0.195.0
Operating system : Windows 7 enterprise, Service park 1, 64 bit OS

regarding the installation, we have got PDFX4SA_sm.exe file from you. we run this file to install PDF Saver.

We are not able to register the pdf saver.
When this problem occured, the pdfsaver4.exe does not exist. for some reason, we are missing this file.

[Nico - Tracker Supp]

Hi rn101506,

Thank you for the information provided.
The build number 4.0.195.0 is quite old. Please try installing the newest build for PDF-XChange Drivers API version 4 from here (build 4.0.210):
https://www.pdf-xchange.com/version ... ivers-api/
and please let me know if this solves the issue.
Thanks.
Sincerely,

[rn101506]

At this moment, we may not be able to install the 4.0.210 version. could you please provide us the solution and root cause of this problem.
as i metioned earlier we have seen this problem in 64 bit machines so far.

[Nico - Tracker Supp]

Hi rn101506,

Thank you for your reply.
Regarding your questions, the root of problem seems to be that the COM Service Control Manager is not finding our print driver, to provide a solution we need to know why this is happening. I tested the 4.0.195.0 installer in Windows 7 Ultimate Service Pack 1 - 64 bit and it works correctly.

Please take a look at the registry after installing the API in a 64-bit machine and make sure you have the following keys:

HKEY_CLASSES_ROOT\CLSID\{217974DB-6777-4A9F-90A7-AA5EBA834BA2}
HKEY_CLASSES_ROOT\PXCComLib.CPXCControlEx\CLSID
HKEY_CLASSES_ROOT\PXCComLib.CPXCControlEx.1\CLSID

HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{217974DB-6777-4A9F-90A7-AA5EBA834BA2}
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PXCComLib.CPXCControlEx\CLSID
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PXCComLib.CPXCControlEx.1\CLSID

The key {217974DB-6777-4A9F-90A7-AA5EBA834BA2} should have a subkey called LocalServer32 which contains the location of pdfSaver4.exe which should be:
"C:\Program Files\Tracker Software\PDF-XChange 4\pdfSaver4.exe".
Please make sure you have this key and also that pdfSaver4.exe is in that location.
All these values are registered by the installer, please uninstall the Drivers API, reboot, reinstall and reboot before checking this values.
Thanks.

Sincerely,

[rn101506]

it works for me too but not always. so i just wanted to know what could cause this issue and throws class not registered exception.

should we reboot computer everytime we uninstall and install the pdf driver? is that the best pratice to follow to prevent these kind of issues?

[Tracker Supp-Stefan]

Hello rn101506,

Yes we would recommend that you do reboot after uninstalling and reinstalling our drivers.

Best,
Stefan

[rn101506]

Thank you. As I mentioned earlier this issue is intermittent. We will let you know when this happens again. If possible we will share the desktop. Would you like to have look at it? That would help us in finding the root cause of the problem

[Tracker Supp-Stefan]

Hi rn101506,

Thanks for your willingness. So please do make sure that you are rebooting the machine(s) after each update, and if despite that the issue still appears - we would like to take a look. So do let us know if this happens again, and we will see to set up a remote session with you.

Best,
Stefan

[Nico - Tracker Supp]

Hi rn101506,

Thank you for your post. Please verify that the issue never happens when you reboot the system after the installation of our drivers and that this behavior is consistent. If the system is not rebooted after installation we cannot guarantee the installation changes in the registry have been completed, therefore at that moment installation has not finished yet.
Thanks.

Sincerely,