Database discovery not showing up?

When checking through the environment, we found the Arkieva api was starting and stopping. Checking the event viewer showed the below error, which points to their being a problem with the password of the service account. Changing the password to the service account after the installation is what causes this error.

Change the password of the service account to a password without any special characters to solve this issue.

• Related Articles

• Connect to Azure Web Database?

  Currently it is not possible to connect to Azure because the database discovery service is not configured to work with Azure. 

• Best Method is not showing when run as a job?

  The reason Best Method is not showing when run by a Job is because of the service account. Give the service account full access to all data in security, then try running the job again. 

• Database 'master' error when generating upgrade script?

  Create Database permission denied in database 'master' error when generating upgrade script occurs when the user does not have sufficient rights on the server.

• How can I not give DBO (Database Owner) permissions?

  This query is useful for when the client doesn’t want to give DBO (Database Owner) permissions. Instead it will make the user a DDLadmin, meaning all they have to do is run the query on the database then add the user (or users) to the Arkieva_users ...

• Terminal server is connecting to the wrong database?

  Terminal server connects to wrong database in case of server cloning. Checks: Check db config Check the dbo.json files Check api root: http://zarkvs01/Arkieva/api/v1/config/databases Check config files on terminal server At a client, first we had ...