(10.5.0.393): Sign-Document: Invalid provider

[Burdarper]

Hello everybody,

we just stopped rollout of the new version of PDF-XChange Editor 10.5.0.393 in UAT phase due to an error after signing and saving a PDF document : (Deployment via PatchMyPC / intune / 7500 clients)

Error Message looks like this

Sign Document:
The signature placement failed.
"Error [System]: Invalid provider type specified."

pdf_x_-change_sign_error.jpg

If the previous version 10.4.4.392 is re-installed the signing works again.

The certificate used is distributed by a self IssuingCA.

This error has been already mentioned in this forum, but no solution was provided.

I would be happy for any hint.

Greetings

[Daniel - PDF-XChange]

Hello, Burdarper

Build 393 made a few changes to our Crypto handling methods to account for some issues on the windows side, which could cause errors for users of more rigorious certificate providers. In your case, please open the preferences, and enable this new option:

image.png

This should restore the old functionality for your use case, without needing to roll back the software.

Kind regards,

[Burdarper]

Hello Daniel,
thank you for this quick reply.
It worked.
However I would have to add this configuration to the main intune package.
So is it possible to make this change via install command prompt parameter or with a script running after installation?

[Daniel - PDF-XChange]

Hello, Burdarper

Conveniently, this is a temporary feature, it was added to give manual control incase the previous change lead to other complications (Which it thankfully did not).

In the next release, this checkbox will actually become obsolete, as the editor will automatically switch modes as needed when an error like this comes up. The option itself will be removed later in the future, but you can look forward to build 394 simply fixing this error for everyone regardless of this options setting.

For this reason there is no way to enforce the change through Intune or other methods, however if you will be using build 393 for a long time, you can enable this option with the following registry key:

Code: Select all

[HKEY_CURRENT_USER\SOFTWARE\Tracker Software\PDFXEditor\3.0\Settings\Security\Signatures]
"b.UseCAPIforCMS"=dword:00000001

(remove the key, or set its value to 0, to "uncheck" the option).

Kind regards,

[ingriddeweerdt]

Hi,

Some users in our organization experience the same issue. However it looks that this option is not always available:

image(1).png

Version:

image(2).png

Also it looks like the error seem to appear only on devices that are build with AutoPilot (Azure only). We also still have Hybrid AD joined devices which seem not to suffer from this issue.

The mentioned regedit key cannot be found; the path stops at HKEY_CURRENT_USER\Software\Tracker Software\PDFXEditor\3.0\Settings\

Any advice is appreciated.

Kind regards, Ingrid

[Stefan - PDF-XChange]

Hello ingriddeweerdt,

Welcome to our forums, and sorry to hear you are also experiencing this!
Is the registry path and value do not exist - it is OK for you to create that, and it would then have effect on the Editor after the next re/start.

Kind regards,
Stefan

[ingriddeweerdt]

Hi Stefan,

Thanks. For now we are first trying the set that new option. If that works for the current reported cases we have (and continue to work also after a reboot), I will create a KA in our support database.

Regarding the registry: that is plan B if the setting is gone after a reboot.

When is the next build expected?

With kind regards, Ingrid

[Stefan - PDF-XChange]

Hello ingriddeweerdt,

Next build is on the way, and if testing for it goes without any significant slowdowns - it should be out by the end of the week.

Kind regards,
Stefan

[Burdarper]

ok, if the new version is just around the corner, I'll just ride out this update.
Then I save myself the effort of creating and assigning a script to all computers.

Many thanks for the open and fast communication

[Willy Van Nuffel]

The new build 394 is available.

[Stefan - PDF-XChange]