Skip to main content
Announcements
Qlik Connect 2025: 3 days of full immersion in data, analytics, and AI. May 13-15 | Orlando, FL: Learn More

Identify wrong NPrinting database version restored to NPrinting Server

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Frank_S
Support
Support

Identify wrong NPrinting database version restored to NPrinting Server

Last Update:

Jun 24, 2022 1:35:47 PM

Updated By:

Frank_S

Created date:

Oct 30, 2019 6:37:10 PM

NPrinting is experiencing unusual behavior after an upgrade and you suspect that a restore was performed unnecessarily over the upgraded NPrinting installation using an older NP database version or you have restored the wrong version of the NPrinting database to a Newly installed NPrinting Server.

Some of the symptoms of an unnecessary NP database restore or an invalid version database restore may be as follows:

  • Unable to log into the NPrinting Web Console
  • NPrinting Web Console may appear 'stuck' and does not response after logging in
  • NPrinting Scheduler. Engine and or License services may fail to start.
  • When logging into the web console, you may see an error as follows: "Error trying to open the page"
  • Can no longer access any pages such as connections, apps, reports etc. after logging into the web console
  • Accessing links in the Web Console is very slow
  • The License Page is repeatedly presented to you

Therefore you need to determine if an older database was restored over the existing/upgraded NPrinting server.

Environments:

  • All NPrinting 17 + platform server environments


NOTE

  • It is NOT required to perform a NP database restore after an NPrinting Server Upgrade 
  • The NPrinting upgrade process automatically updates all NPrinting database tables. It also adds or deletes any new or defunct NP database tables. 

Diagnose:

 

  • Retrieve the NPrinting_Manager.log file from the customer found in "C:\ProgramData\nprinting\logs"
  • Search for a similar log entry as shown below:
"The database version {dbVersion} is different from the assembly version {assemblyVersion}"

Assembly version {assemblyVersion}: Installed version of NPrinting
Database Version {dbVersion}: version of restored copy of NPrinting database

Sample log entry of a database version restore mismatch against a currently installed (assembly) version of NPrinting:

2019-11-13 07:41:27,236 [1] WARN Qlik.NPrinting.Manager.Commands.Restore.RestoreDbCommand - Qlik.NPrinting.Manager    19.40.0.0    Qlik.NPrinting.Manager.Commands.Restore.RestoreDbCommand    20191113T074127.236-08:00    WARN    QLIKSERVER3        0    0    0    0    0    0    0    0    
The database version 19.29.3.0 is different from the assembly version 19.40.0.0        

 

  • If a similar message is found, then this confirms that there version mismatch
  • To resolve the mismatch, you will need to roll back to the previous assembly and database version of NPrinting
ie: Restore the pre-upgrade NP database to the pre-upgrade assembly version of NPrinting before attempting another upgrade.
 

What can cause this problem?

  • An NPrinting database is restored {dbVersion} that is older or newer than the current NPrinting {assemblyVersion} Database

References:
Contributors
Version history
Last update:
‎2022-06-24 01:35 PM
Updated by: