Datamaker: Login failed for gtrep

Document ID : KB000005363
Last Modified Date : 14/02/2018
Show Technical Document Details

When trying to connect to the gtrep repository database connection in Datamaker, I am receiving the following error message:

Database Error. 
Error: Unable to connect to Database. 
Profile: gtrep- TDM_Repo 
Title: Test Data Repository 
Database Error Message: SQLSTATE = 37000 
[Microsoft][SQL Server Native Client 10.0][SQL Server] Cannot open database "gtrep" requested by the login. The login failed. 
Transaction Error Code: -1 
Database Error Code: 4060 

The log file shows:
Opening database connection. 
Error occurred while connecting to database. 
Error occurred while accessing database: Cannot open database 'gtrep' requested by the login. The login failed. 
Login failed for user 'GTREP'. 

CA Test Data Manager (TDM)- Datamaker

When narrowing down the root cause of this issue, we recommend enabling debugging for Datamaker and analyzing the log files. Directions on how to do this are listed here: 


You will also want to check the following:

- Are you able to connect successfully in SQL Server Management Studio using the same connection details? The database log files may reveal a more specific error message.
- Are your connection details (username/password) valid?
- Has anything in your environment changed recently? 
- Ask your DBA if any backups or upgrades have occurred to SQL Server recently. 


If any patches or upgrades have been made to your database, you may see that the gtrep database is in a 'recovery pending' status. The database logs will show an error message like this, which is most likely the cause of the error in Datamaker: Database 'gtrep' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server error log for details. 


Typically this error message indicates a database or environment related issue. We highly recommend working with your DBA to resolve the SQL Server error messages so that Datamaker can connect to the gtrep database. Once this is fixed, make sure your repository connection details are correct and follow these instructions to continue connecting:

Additional Information:

If you experience any further issues, please open a support case by going to