Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello,
me and my colleagues use NPrinting Designer locally with Office 365.
Yesterday, suddenly, we were not able anymore to open the NPrinting Designer when editing Excel reports.
We work for different customers with different versions of NPrinting and none of us is able to open the designer anymore.
Everything works fine with Pixel Perfect, Word and Power Point.
Do you know if there has been some kind of update to Excel 365? We started to experience this issue only yesterday and worked correctly for the last months.
I attach the error's screenshot
We already tried to solve the problem editing the screen resolution and the Designer.exe compatibility tab as explained here.
Thank you very much,
Davide
Thanks to both of you for the support!
Davide
Having it set to "Optimize for compatibility" was causing the same error for me as @Greg1291 had.
I had similar errors in previous instalations too though and I guess update of Excel just resets that setting to default (maybe)?
So to replicate steps which cause error you just need to set it up to the setting as on gif below:
cheers
Lech
I also faced one different problem in powerpoint template, that was introduced in office 365 version 2102.
Qlik support accepted at as a bug, last week we got response that it is planned to be fixed in May 2021 SP 3 but release date is not yet known.
In brief, its quite possible that something works in old office version and fails in new version.
Thanks,
This issue is currently under NPrinting Developers review (QB-7433). Please, contact Qlik Support in case the solution suggested by Lech_Miszkiewicz does not work. Please, specify what version of Office is in use and what is the latest Windows update in your OS.
Hi @Greg1291 ,
Please let us know the exact version of Excel that caused the issue. You can access it selecting File, then Account and opening the About Excel dialog.
Thanks.
Best Regards,
Ruggero
Thank you @Greg1291
Your post information has been forwarded to R&D.
Keep in mind R&D is in Europe so unfortunately we may not get a response until tomorrow.
Hi @Greg1291
Please see this article about the issue and for a possible solution