RESOLVED: NPrinting Designer Issue

Katie_Davis · ‎2021-10-13

Updated 1/05/2022 to include upgrading to NPrinting May 2021 Service Release 3 (SR3) will resolve issue.

vinicius_rosa · ‎2021-11-03

Microsoft recently updated the Windows office and registry and bugged the way Nprinting Designer works.

We apply the steps bellow em 3 environments and all works well.

1. Open Registry Windows
2. Go to HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\ (logged with the user run nprinting Designer and in this example using office version 16, check if is other version)
3. Delete Common key or Rename for Common.old
4. Create Common key
5. Right Click on Common key and go to Permission
6. Add everyone and Deny Full Control and Read and apply
7. For work test, try to create key inside the Common, we should see the error (permission is expected)
8. Now, try to edit report (does not require restart of server or anything, just open)

if anyone can validate I hope it helps

vinicius_rosa · ‎2021-11-09

I've tried being more specific and figured out which key is causing the problem.

The following steps are required:

delete key: HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentConfigs

Recreate the HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentConfigs key

Edit permissions and block write and full control

More details below

https://github.com/MicrosoftDocs/OfficeDocs-DeployOffice/issues/419

Andrea_Bertazzo · ‎2021-11-11

Anyone having this problem, please, test the workaround provided in the "Preliminary Step" in this article:

https://community.qlik.com/t5/Knowledge/NPrinting-Designer-cannot-find-a-supported-template-editor-W...

Kindly, confirm that this resolves the issue.

andregas · ‎2021-11-11

Hi @Andrea_Bertazzo,

I confirm, this resolves all the issues. The step 3 of the link is necessary starting from Office version 2109.

marcginqo · ‎2021-12-02

I would suggest not to use the solution from @vinicius_rosa

I applied this solution and it worked for getting NPrinting fully up and running again (in this case with Excel Office 365).

Unfortunately it messes up your complete Office registry. If you look at the different keys that are in the Common registry entry the suggestion was to rename it and create and empty Common one. Although it works, it happened to me that I was logged out of office and not able to login again. Then Office told me to activate my license but it did not work anymore.

We spend over 10 hours with Microsoft support to solve it and finally realize that this change in the registry was the root cause of Office not working correctly anymore.

I would suggest not using this at customers to avoid any major issues and wait for Qlik to come with a solution.

After reverting back the registry edit Office worked again for me.

Marc

Ruggero_Piccoli · ‎2021-12-03

@marcginqo the solution tested by R&D is in https://community.qlik.com/t5/Qlik-NPrinting-Documents/Qlik-NPrinting-Designer-cannot-find-a-support... and it doesn't require to modify the registry.

Best Regards,

Ruggero

vinicius_rosa · ‎2021-12-03

if the registry change is not the best way maybe you try to rollback Office365.

Using this link bellow to check all versions release by Microsoft

https://docs.microsoft.com/en-us/officeupdates/update-history-microsoft365-apps-by-date?redirectSour...

I used and works well version 14026.20308

Then running this commands in CMD (with administrative privileges)

cd C:\Program Files\Common Files\microsoft shared\ClickToRun

OfficeC2RClient.exe /update user updatetoversion=16.0.14026.20308

The download site can be found here.