Unfortunately the information which you provided is simply not enough to understand the actual nature of the issue of that you are experiencing exactly.
Please provide the following:
Details steps to reproduce the issue and exactly what did you change? what was working before you made the change?
What are your expected results? Provide a sample/mockup of expected results
What are your actual results? Provide samples of the output or errors encountered
What version of NPrinting are you using?
What version of QlikView or Qlik Sense is NPrinting connecting to?
What operating system in NP and QS or QV running?
Log files that correlate directly with the time that the issue was experienced.
In the meantime, try refreshing your NPRinting connection, then open the template editor and right click each table object and select 'update' from the right click context menu. This will update your template editor with the right object information if the source objects - columns etc in the qvw or qvf - have changed.
We are just 'like' you and like to be liked when providing a helpful answer. You may also press the 'Solution Accepted' button if an answer provided resolves your question or issue... Cheers!
Please remember to specify the version of Qlik NPrinting you are using.
I suggest you to check if there are some special, or not printable characters in your template. You told the issue appeared after changing some objects, verify if those objects introduced strange tags.
Maybe you could post a screenshot of the template.
Best Regards, Ruggero --------------------------------------------- When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads with a LIKE if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads with LIKEs if you feel additional info is useful to others.
Thanks Frank and Ruggero, the version is April 2019 (I think it's in the question tags).
In the end we understood the issue by rebuilding from scratch, one formula had been changed and there was no indication from the logs of what or where the error was...
It looks like if a table has a calculated dimension with hyphens, apostrophes or dollar signs it might throw this error. I wasn't able to reproduce it constantly since it's also built using dollar-sign expansions.