Terminal server is connecting to the wrong database?

Terminal server is connecting to the wrong database?

Terminal server connects to wrong database in case of server cloning.

Checks:
  1. Check db config
  2. Check the dbo.json files
  3. Check api root: http://zarkvs01/Arkieva/api/v1/config/databases
  4. Check config files on terminal server
At a client, first we had only one PROD application server. That server was then cloned to have a DEV environment for testing. However, when cloning a server, the subscription files are copied, resulting in doubles in the localdb databases for each server.



This only applies for Arkieva database that has not yet worked with the systemdatabase. In later versions of Arkieva, you can find this tables in the system databases.

You can check this by typing sqllocaldb in cmd. This gives a list of databases which should be checked. Open these in ssms with the service account (under which services are installed). Check the "subscription" tables for wrong database references (ZARKVS01 in the example below, as we do not want PROD links in our DEV environment). Delete those entries (for all localdbs for each service).

The timeoutentity table is used if you have to wait for processing and retry (e.g. overrides) of the service and might also contain wrong references. Delete those.

Example of localdb: (localdb)\ArkievaDatabaseDiscovery




    • Related Articles

    • 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.

    • I'm not seeing any databases in the Arkieva Server Selection API?

      If you're not seeing any databases in the Arkieva Server Selection API, first check if the Database Discovery Is running.  If the service is running but you still cannot see the databases, check the zemeter.config file. Inspect the value for the API ...

    • 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. 

    • 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 ...

    • Getting duplicate keys error when adding new user to database?

      Duplicate keys could mean there is a duplicate table in the database. An example is a remnant in the data source view from a table being renamed then added back again into the system model. You can run the below queries together in the database to ...