Errors while verifying Service Repository in Datamaker

book

Article ID: 5439

calendar_today

Updated On:

Products

CA Test Data Manager (Data Finder / Grid Tools)

Issue/Introduction

When trying to connect to a profile in Datamaker, I am receiving the following error messages: 


Service Layer: Error Testing Connection 
Error verifying Service Repository: 
Mismatched DB versions (This = 3.2D, Service= 3.2B) 
Mismatched Service Names (This = PTESTSQL01, Service= DEV-TEST03\TEST) 
Mismatched Schemas (This = gtrep_testing, Service= gtrep) 


We recently copied over our repository to a new location in another server. We updated the rep.xml file with the new server information. We tried updating the repository (ctrl+alt+m), but there was nothing to update or sync. Datamaker seems to be referencing both database names still. 

Cause

The error is occurring due to the differences between the local repository version (3.2D) and the remote repository version (3.2B) as seen in the service layer. 

The error could also happen when the service name was not updated in GTREP database when it is changed to different servers.

Environment

CA Test Data Manager (TDM)- Datamaker

Resolution

To resolve this, update your 'Primary Service URL' from the Security-> Users and Group-> Service Layer tab to reflect the correct machine name.

<Please see attached file for image>

src="/servlet/servlet.FileDownload?file=0150c000004AK25AAG" alt="primary service url.png" width="956" height="571">

Additional Information

If you experience any further issues, please open a support case by going to https://www.ca.com/us/services-support/ca-support/contact-support.html.  

If the issue is with mismatched servicename, TDOD logs show the below query returned the older server name "OLDServer".

SELECT '', @@VERSION, @@SERVERNAME, '',     '', db_name()

The same query can be run in SQL server and it should show the service name in returned result.

The service name need to be changed in the SQL server to "NewServer".

DBA's can run the below queries to change the service name.

exec sp_dropserver 'OLDServer';
GO

exec sp_addserver 'NewServer', 'local';
GO

Attachments

1558707234868000005439_sktwi1f5rjvs16qm2.png get_app