The browser cannot establish a connection to DocuWare Desktop. In some cases, you get the error 

"Windows User is not a DocuWare Desktop user"

There are several reasons that might cause such an issue. Please refer to the following solutions:

  1. DocuWare Desktop App or Desktop App Service is not started:
    This behavior can occur when either the Desktop Apps or the Desktop Apps Service has failed to start. To address this issue, the Desktop Apps and/or the Desktop Apps Service must be restarted.
    Please refer to 
    Installing and Connecting Desktop Apps for more on Desktop Apps and how to restart these software components. 

  2. Content within the browser cache:
    In some instances, browser cache history can prevent DocuWare Desktop Apps from establishing a connection. Please delete the browser cache and cookies, then reattempt to utilize DocuWare Desktop Apps.

  3. DocuWare Client is hosted using a self-signed SSL certificate:
    The root certificate has to be imported to the Microsoft Certificate Store.

  4. Internet Explorer security zone of the Website:
    (Note: Solution for Internet Explorer ONLY)
    It is necessary to check the Internet Explorer security zones. If establishing the connection does not work, try to add the DocuWare Web Client URL "http://SERVERNAME/DocuWare" to the Internet Explorer security zone "Local Intranet".
    Check whether the Web Client is part of the same IE security zone as the URL for localhost "" and "" and to change this if it is not true.

    Keep in mind that those settings are set by group policies in some environments, thus it is not allowed to add the Web Client URL to a specific Internet Explorer security zone. Therefore it might be necessary to add this URL by amending the group policies.

  5. Internet Explorer in enhanced security configuration is not supported:
    (Note: Solution for Internet Explorer ONLY)
    Internet Explorer Enhanced Security Configuration can prevent DocuWare Desktop Apps from establishing a connection. Switch to a different browser (Firefox, Chrome) for connection creation or disable the enhanced security configuration. Please visit for more information regarding Internet Explorer Enhanced Security Configuration.

  6. DocuWare Client is hosted using a self-signed SSL certificate:
    The root certificate has to be imported to the Microsoft Certificate Store.

  7. DocuWare Client is hosted using SSL:
    (Note: Solution for Firefox ONLY)
    The root certificate “DocuWare GmbH Local Authority” has to be exported from the Microsoft Certificate Store and imported to the Mozilla Firefox Certificate Store: Open and add an exception for the certificate.

    Alternatively, open Firefox Settings, then navigate to Privacy & Security and scroll-down to the Certificates section. Click-on "View Certificates..." , open the Authorities tab and select "Import... ". Select the exported “DocuWare GmbH Local Authority” certificate, then enable “Trust this CA to identify websites.” Once completed restart the browser and try to connect again.

  8. Antivirus or other Security Software 
    DocuWare Desktop Service is trying to recognize which windows user from which session is accessing its functions. Usually the browser processes the user and the session can be found. In some cases the antivirus, which is not working 100% in user context can be the communication partner to DocuWare Desktop Service. During the connection procedure, the antivirus has to be stopped. Sometimes it is not enough to stop it using the icon menu option, but the complete process/service must be stopped.

  9. DocuWare Settings Service is not working properly (On-premise Only):
    If the prior solutions failed to resolve the described behavior, this may indicate that the DocuWare Service Settings are not working as intended. Please refer to the following articles to address this:
    • Known Issues - Web Configuration (Web Client Settings): KBA-34359
    • Error in login with token: 'ClientProtocolManagers are not specified': KBA-34700

KBA is applicable to both Cloud and On-premise Organizations.

Comments (2)
  • New to DocuWare 7 (according to the DW support team):

    The following are the ip addresses used in DocuWare 7 for the Admin tool and Desktop apps.  This is a change from DocuWare 6.x!

    Desktop Apps:
    Admin Tool:

    If you're able to connect with the web client and also able to connect the desktop apps (the connections in Desktop Apps look fine) but you're still unable to use them and you get an error when trying to edit a document then the above IP addresses may still be blocked.


  • Additionally, after a Windows 10 update, localhost may not be resolving correctly at all.  If you can access but not https://localhost:8091/ then you'll need to add (or uncomment) the following line (as administrator) in the following file


    Line: (make sure there is not a # in front)

    Then as administrator from command prompt:  ipconfig /flushdns