When only some databases are appearing in the API, copy and paste one of the following links into Google Chrome and make adjustments to the server name for it to work in the client environment.
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 ...
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 ...
Most likely a misconfiguration. f you get this error, test http://cit-arkievaprd/Arkieva/API. This is the path you should have entered when installing the Fat Client. It is stored in “C:\Program Files\Arkieva\Zemeter.NET.exe.config”. Look for: <add ...