Views:

Behavior:
Internet Explorer cannot establish a connection to DocuWare Desktop.

Solution:

There are several causes that might cause such issue:

  1. DocuWare Desktop is not started
    Solution:
    (Re-)Start DocuWare Desktop
    More information on this is available here: http://help.docuware.com/en/#t62652

     
  2. DocuWare Desktop Service is not started
    Solution:
    (Re-)Start DocuWare Desktop Service
    More information on this is available herehttp://help.docuware.com/en/#t62652
     
  3. Internet Explorer security zone of the Website
    Solution:
    It is necessary to check the Internet Explorer security zones. First of all if establishing the connection does not work try to add the DocuWare Web Client URL "http://SERVERNAME/DocuWareto the Internet Explorer security zone "Local Intranet".
    The next step would be to check whether the Web Client is part of the same IE security zone as the URL for localhost "http://127.0.0.1" and "https://127.0.0.1" 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 IE security zone. Therefore it might be necessary to add this URL by amending the group policies.
     
  4. Internet Explorer in enhanced security configuration (http://support.microsoft.com/kb/815141) is not supported.
    Solution:
    Switch to a different browser (Firefox, Chrome) for connection creation or disable the enhanced security configuration.

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

     
  6. Content within the browser cache is causing trouble while trying to establish the connection
    Solution:
    Delete the browser cache and cookies and try it again.

     
  7. DocuWare Settings Service is not working properly
    Solution:
    Check these KB articles:
    Known Issues - Web Configuration (Web Client Settings)
    Error in login with token: 'ClientProtocolManagers are not specified'