Cannot print labels from Web Applications in Control Center, or cannot access Document Storage from the clients


Problem 1

When you want to print labels from Web applications in Control Center, the procedure fails, and no labels print out. You also cannot get any file (label, solution, image) from Document Storage.

You may see the following message when you use Web Printing:

An error occurred while getting variables from the label: Label file cannot be opened.

The problem is caused by the old version of WebDAV (support for Web folders). During the installation of NiceLabel Control Center, the installer verifies the current version WebDAV files and prompts you to make the upgrade if the version is too old. You didn't make the necessary update, and that makes the Document Storage (and consecutively Web Printing) inaccessible.

Problem 2

When accessing Document Storage from your NiceLabel clients/applications, the application prompts you to enter your credentials, or you are denied access even though the user account that you are using has sufficient permissions to access Control Center.

The problem occurs when Windows authentication is enabled in Control Center and the Control Center server uses FQDN (Full Qualified Domain Name).


Solution 1

You must install WebDAV support on all clients that need to have access to the Document Storage. This includes workstations with NiceLabel Designer PowerForms, Automation, and the Control Center computer itself (if you plan to use Web applications).

For details, please check this KB article.

Solution 2

To resolve this problem, create a new registry entry:

  1. Open registry editor (Click Start, type regedit, and then press <Enter>.)

  2. Locate and then select the following registry subkey:


  3. On the Edit menu, point to New, and then click Multi-String Value.

  4. Type AuthForwardServerList, and then press <Enter>.

  5. On the Edit menu, click Modify.

  6. In the Value data box, type the URL of the server that hosts the web share (e.g. ", and then click OK.

  7. Exit Registry Editor.

  8. Restart the WebClient Service.