Skip to main content
Announcements
Defect acknowledgement with Nprinting Engine May 2022 SR2, please READ HERE
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

NPrinting can't find reporting template editor

Hi,

Just installed NPrinting and was about to create my first report when I got the following error:

qlikview nprinting can't find a supported reporting template editor for the file

I am using 16.0.0 NPrinting but I suspect my problem is that I have Office 2010 and 2013. Office 2013 only has Visio installed and not Excel. Is NPrinting looking for Excel 2013 and is that why I'm getting that error?

8 Replies
shawn-qv
Creator
Creator

Check that the paths to the templates are correct both on the server and on the machine you use for development.

S.

Anonymous
Not applicable
Author

Thanks Shawn. They are.

thomasjenn
Partner - Contributor III
Partner - Contributor III

Hi,

NPrinting needs only Office with NPrinting Designer not with NPrinting server.

marcus_malinow
Partner - Specialist III
Partner - Specialist III

Hi Renata,

I regularly have this issue. When I first contacted Vizubi they provided me with some registry settings that resolved the issue.

First copy the settings from below, and save them into a text file with a .reg extension.

You'll need to close down NPrinting and Excel, then double click your reg file to add the settings into your registry. Then restart NPrinting and try again. If that doesn't work immediately then you may need to reboot.

Hope this helps,

Marcus

----- REG settings start here:

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00020820-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00020830-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00020832-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{00020906-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{F4754C9B-64F5-4B40-8AF4-679732AC0607}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{18A06B6B-2F3F-4E2B-A611-52BE631B2D22}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{64818D10-4F9B-11CF-86EA-00AA00B929E8}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{CF4F55F4-8F87-4D47-80BB-5808164BB3F8}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\Wow6432Node\CLSID\{DC020317-E6E2-4A62-B9FA-B3EFE16626F4}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{00020820-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{00020830-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{00020832-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{00020906-0000-0000-C000-000000000046}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{F4754C9B-64F5-4B40-8AF4-679732AC0607}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{18A06B6B-2F3F-4E2B-A611-52BE631B2D22}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{64818D10-4F9B-11CF-86EA-00AA00B929E8}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{CF4F55F4-8F87-4D47-80BB-5808164BB3F8}\DocObject]
@="16"
[HKEY_CLASSES_ROOT\CLSID\{DC020317-E6E2-4A62-B9FA-B3EFE16626F4}\DocObject]
@="16"

Not applicable
Author

I initally had this issue a while ago, and it was due to registry settings as previously stated but there is a fix you can run to avoid the manual process

Workaround for MicroSoft Office 2013 error: "Cannot find a supported template editor" – Customer Fee...

Anonymous
Not applicable
Author

Link is dead but I did find a new one hosted on the qlik community. Hopefully this helps someone else in the future

Workaround for MicroSoft Office 2013 error: "Cannot find a supported template editor"

Not applicable
Author

You need to go to the Excel reports section on NPrinting and browse supporting Excel format of template to be added. It should work if it allow you to add it and edit/preview etc.

andrejfreitas
Partner - Creator
Partner - Creator

Hello,

 

I had the same issue on NPrinting 16.7. I contacted our Qlik reseller and selecting the boxes below on excel.exe fixed this problem.

image (3).png