Starting an Autoindex configuration manually causes error

Behavior:
When attempting to start an Autoindex configuration manually, the following error messages are displayed;

"undefinedInternal Server Error"

OR

"There was no endpoint listening at ... that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details." 

Solution:
This behavior is most commonly caused by an incorrect dwmachine.config file. In order to resolve the above error message, these steps are necessary:

1. Open the file C:\ProgramData\DocuWare\ServerConfig\dwmachine.config in a text editor of your choice.
   If your DocuWare system is distributed across multiple machines, you must do this on every machine on which the Frontend Services are installed.
    
2. Check if the file contains an entry that looks similar to the below:
   <Setting Key="LocalWebServices" Value="..." Encrypted="false" />
   1. If the entry already exists, take the URL in the Value attribute, append /Settings/SettingsService.svc to it, and navigate to it in a web browser of your choice.
      For example, if the Value attribute contains the URL http://presentationvm/DocuWare, the site you need to visit is http://presentationvm/DocuWare/Settings/SettingsService.svc.
      If you see a blank or an error page, proceed to step 3.
   2. If the entry does not exist, modify the file to add the entry so that it looks similar to this:
            <Setting Key="ServiceWindowsUserPassword" Value="..." Encrypted="true" />
            <Setting Key="LocalWebServices" Value="..." Encrypted="false" />
          </Settings>
        </ServerSettings>
      </ServerConfigSettings>
3. Modify the LocalWebServices entry to point to the correct URL. This URL must point to the DocuWare directory on a frontend machine.
   For example, the LocalWebServices entry might look like this after the adjustment:
   <Setting Key="LocalWebServices" Value="http://DOCUWARE01/DocuWare" Encrypted="false" />
   Please note that further adjustments are necessary if the frontend server or load balancer is configured only to use HTTPS.
    
   1. For DocuWare systems without load balancers, using the URL http://localhost/DocuWare or http://<hostname>/DocuWare (where <hostname> is the hostname of the frontend machine) works fine in most cases.
   2. For DocuWare systems with a load balancer, most systems will function correctly with http://<loadbalancer>/DocuWare (where <loadbalancer> is the address under which the load balancer can be reached). Under certain circumstances, for example, to help with debugging, using a specific frontend machine instead of the load balancer is recommended.
       
4. In order to apply the changes, restart or recycle the DocuWare Processes App Pool and DocuWare Settings App Pool. This can be done by going to Application Pools within IIS, clicking on the DocuWare Processes App Pool, then selecting Recycle... under the Actions pane.
   

KBA is applicable to On-premise Organizations ONLY.