Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi!
The server had NPrinting 18.39.6.0 installed. It has not been updated for a long time due to the organization's security policies.
Then we decided to upgrade immediately to 22.15.2.0. The update went fine BUT after the update and the start of all services, it is impossible to authenticate as an administrator.
In web log - Qlik.NPrinting.WebEngine 22.15.2.0 Qlik.NPrinting.WebEngine.Controllers.HttpHelper 20220610T215022.137+03:00 ERROR SERVERNAME-00-01 0 0 0 0 0 0 0 0 Security exception serving the request http://FQDN-SERVER:4996/npe/license/ System.Security.SecurityException: Invalid user↵
Are there any methods for checking and correcting authentication problems?
It is not clear what the issue might be.
So I suggest that you start by attempting to use NPrinting Security to log in with.
This is the email address and password that was used with you first installed NPrinting. Check your company's internal NPrinting installation documentation for this unique to your organization information.
The above email and password must be entered into the NPrinting login screen email and password field and NOT into secondary logon field that you might be prompted with after clicking the blue Windows Authentication button.
Kind regards...
It is not clear what the issue might be.
So I suggest that you start by attempting to use NPrinting Security to log in with.
This is the email address and password that was used with you first installed NPrinting. Check your company's internal NPrinting installation documentation for this unique to your organization information.
The above email and password must be entered into the NPrinting login screen email and password field and NOT into secondary logon field that you might be prompted with after clicking the blue Windows Authentication button.
Kind regards...
Hi,
The error message says "Invalid user" so be sure you are trying to login with the correct username and password. You can check the users by querying the repository DB. If you need help in doing that please open a support ticket.
The upgrade process keeps the information in the repository so also the users and their login parameter. Upgrading directly from 18.39.6.0 to 22.15.2.0 is supported (refer to the Release notes for the complete list).
Best Regards,
Ruggero