Vizlib Home

Vizlib Server Troubleshooting - Known Issues / FAQ

When you're working with Vizlib Server it's important to be clear about what you can and can't do. We've collected together any known issues and limitations and listed them in this article for you, along with any answers to any other questions you might need.


Set VZB_Server_Url after Updating Extension File

This issue relates to users updating their extension files for Vizlib Teamwork, Finance and Writeback products.

If you're updating any of these extensions in the Qlik Management Console (QMC), the Extension Server URL custom property VZB_Server_Url (Figure 1) needs to be set after the update completes. 

Figure 1: VZB_Server_Url QMC Empty

If you restart Vizlib Server after the update, the Extension Server Url custom property will be set automatically (Figure 2). 

Figure 2: Extension Server Url VMC

You can also enter the property manually on each extension in the QMC (Figure 3). 

Figure 3: VZB_Server_Url QMC Added

Windows Service not Automatically Starting

Very rarely, Vizlib Server Windows Service gets created during the install but is not automatically started. If you encounter issues with opening the VMC, double-check if Vizlib Server is running using Task Manager. If not, start it manually.

Browser not Loaded

Occasionally, for slower servers, the browser is opened before Vizlib Server is fully initialized and the page is not loaded properly. If that happens, wait another minute and simply refresh the page.

PFX Certificate password error

If you specified the wrong password for the PFX certificate during the install, the page won’t load properly over https. Instead, Vizlib Server will fall back to the HTTP protocol. If this happens, activate the product by following the steps in the installation guide. Open the VMC at http://localhost:1980/vmc open the Logs Browser tab and filter the error logs to check for any possible causes. 

Vizlib Server - Qlik Proxy Service Configuration

If you're installing Vizlib Server on a dedicated server or you have a multinode environment and an error is occuring, check port 4243 has been opened for QPS communication between those servers.


Kenneth is the author of this solution article.

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.