Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.Join Us
In NPrinting June 2017 release there is a known issue with cache regeneration tasks failing
This is a result of the connection trigger error outlined in the release notes related to Issue ID: OP-5729
In Qlik NPrinting June 2017 (17.4), a manual metadata reload would succeed, but the same reload executed by a trigger would fail with this error message:
"Error running check stuck executions. Row was updated or deleted by another transaction (or unsaved-value mapping was incorrect)"
The issue is resolved in the September release of NPrinting 17
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.Submit a case
Experiencing a serious issue, please contact us by phone. View phone numbers and hours by region.