Views:

Behavior:
The credentials for the database have been changed and Authentication Server will no longer start.

Solution:
Starting in version 6.10, the database connection used by Authentication Server is stored in C:\ProgramData\DocuWare\ServerConfig\dwmachine.config. If you update the password here directly, it will not be encrypted automatically when Authentication Server starts.

DocuWare ships with a command line utility that will encrypt the password before writing it to the dwmachine.config file.

  1. Take a backup of the dwmachine.config file in C:\ProgramData\DocuWare\ServerConfig.
  2. Open a command prompt as administrator.
  3. Paste and run the following command:

Version 6.10 - 7.1:
"C:\Program Files (x86)\Docuware\Setup Components\DocuWare.ServerSetupCMD.exe"
configureDatabaseConnection --databaseType=MSSQL --databaseServer=localhost --databasePort=1433 --databaseUser=admin --databasePassword=admin --databaseName=dwsystem

Version 7.2 - 7.4:
"C:\Program Files (x86)\Docuware\Setup Components\DocuWare.Setup.Server.CMD.exe"
configureDatabaseConnection --databaseType=MSSQL --databaseServer=localhost --databasePort=1433 --databaseUser=admin --databasePassword=admin --databaseName=dwsystem

***Make sure you modify these variables to match your environment before running the command!***

  1. Stop all DocuWare services.
  2. Start Internal Database and Authentication Server.
  3. Change connections for database connections in the DocuWare Administration Tool under DocuWare System->Data Connections->Database Connections.
  4. Start the rest of the DocuWare services.

KBA is applicable for On-premise Organizations ONLY

Comments (2)
  • In version 7.5 and higher - does Identity Services used the database-connection from Administration Tool or from dwmachine.config. We are having issues trying to login to Administration tool. Identity services interface comes up and then it says that it cannot login to the database, therefore, the administration tool never opens. 
  • @Juan The Identity Services uses the database connection information from the dwmachine.config. I have seen that behavior fixed with a reboot of the system on occasion. If that does not work I would recommend opening a support request.