“Windows cannot access …@8080\DavWWWRoot” – NiceLabel Error Message

Target Audience: IT Manager
Article #: 13282


When using NiceLabel, Network Error dialog box appears stating, “Windows cannot access …@8080\DavWWWRoot. Check the spelling of the name. Otherwise there might be a problem with your network. To try to identify and resolve network problems, click Diagnose.” If you see this error message your company’s network name will appear between the \\ and @.

This article will guide you through the steps needed to resolve the issue.


Usually, it is a previous install of Control Center that causes the “cannot access …@8080\DavWWWRoot”. When Control Center is first installed, it will write to web.config files within Internet Information Services (IIS) as well as create a NiceLAbel database. By default, Control Center names this database NiceAN. Unfortunately, there is no way to modify the installation of the program. Therefore, uninstalling and then reinstalling Control Center appears to be the only way to reconfigure certain features of NiceLabel Label Management System (LMS). These features include HTTPS/HTTP bindings, WebDAV name, or the NiceLabel database sign-on options.

Please note that this is a different problem than the NiceLabel Cloud “cannot access \\localhost@6050\\davWWWRoot” error message although root cause is very similar.


It is uncertain precisely which files need to be configured, as of the time of this writing. While you can web.config files in the related IIS subdirectories, there are various other files which will need to be changed as well. Therefore, the best way to resolve the issue prompting the network error is to completely uninstall Control Center, the default database and IIS. Both IIS and the database contain configurations for the correct ports and HTTPS protocols. These configurations influence the WebDAV – and are likely causing the errors. First, reinstall IIS. Then, reinstall Control Center. Make sure that you select the correct options during reinstallation. Once you have completed this, the error should not reoccur.

Additional Comments

If you need further assistance, please contact us.


Was this article helpful?

Related Articles