You should check these solutions in order, from top to bottom.
Solution 1: Check the Trados GroupShare Console on the Trados GroupShare server.
Open the Trados GroupShare Console and go to the Databases section. And check the "MultiTerm Master Database" section. Is the information in there correct and present? In some cases, the fields are empty and in some the information is incorrect and default values are added - "MTMaster" for the database name and the Trados GroupShare server hostname instead of the actual SQL Server name. If that is the case, stop all SDL services, add the correct information, restart the SDL services.
The above informations is stored in the Settings.xml file from here: C:\ProgramData\SDL\SDL MultiTerm\MultiTerm15 (can be MultiTerm16 or newer)
Solution 1A:
In very rare situations all of the above is not enough and something else in the Settings.xml file is broken/incorrect. In that situation do the following:
1. Stop all SDL Services
2. Move the Settings.xml file to a different location (instead of deleting it)
3. In the Trados GroupShare Console after making sure the Database connection details are correct, click Apply Changes.
4. Check that a new Settings.xml file was created and the Database connection information in it is correct.
5. Start all SDL Services
Solution 2: Eliminate database inconsistencies and access problems
MultiTerm Master Database
- Log into SQL Server Management Studio.
- Make sure the database
MTMaster exists and can be accessed by the Trados GroupShare service account.
NOTE: The name of your MultiTerm master database may be different. It can be found in the Trados Groupshare Console at Console Root > Databases. - If this databases does not exist, recreate the database from a backup or try to investigate why it does not exist (moved to another server, etc)
Other MultiTerm Databases
- Log into SQL Server Management Studio.
- View the content of MTMaster database’s table dbo.Termbases.
- For every entry in column PhysicalName, make sure a database with the same name really exists and can be accessed by the Trados GroupShare service account.
- If any of the databases does not exist, delete the corresponding row in dbo.Termbases or try to recreate the database from a backup - in case it was deleted accidentally.
NOTE: The errors can also occur if in theory all databases can be accessed but access is unreliable. In this case, the SQL Server logs may help troubleshoot this issue further.
If all references are correct or above solution cannot be applied, refer to
Solution 2.
Solution 3: Restart SDL MultiTerm Matrix Cache and SDL Application services
- On the GroupShare application server, click Start > Run or press [Windows Key + R] on the Server machine.
- Type in the dialog box: services.msc.
- Click OK to open the Windows Services console.
- Restart SDL MultiTerm Matrix Cache and SDL Application services.
Solution 4: Enable TLS 1.0 on both SQL Server and GroupShare server.
This is required for
Trados GroupShare 2017 all versions.
Solution 5: Ensure compatibility between Trados GroupShare version and MS SQL Server version.
For example,
Trados GroupShare 2017 SR1 CU10 does not support
Microsoft SQL 2019 Server.
MS SQL 2019 Server is only supported from
Trados GroupShare 2017 SR1 CU11 (and above).
Solution 6: Reboot the Trados GroupShare server
Before doing this, make sure the Solutions above have been checked/performed, especially 1 and 2.
