TDM Portal Masking for SQL Server Error when using named instances

Document ID : KB000111657
Last Modified Date : 30/08/2018
Show Technical Document Details
Issue:
Trying to mask the Travel Database installed in SQL Server results in a connection error. 
"(1) [SERVERNAME].[DBNAME]: Connection error: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host [SERVERNAME], port 1433 has failed. Error: "Connection refused: connect. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall."., Error connecting with connection parameters" 

If the config is saved before the run, it shows the "connect file" and "datasource=[SERVERNAME]" whereas it should be "[SERVERNAME]\[INSTANCENAME]" 

Verified the connection profile. It has instance populated. 

It seems the SQL Server instance name is not getting added to the datasource when running FDM from portal. 

Steps which can result in this problem: : 
1- Install Travel DB in SQL SERVER (With Server Name and Instance Name) 
2- Create a Connection profile with Server and SQL Server Instance Name. 
3- Create a Model based in Travel database. 
4- Run the PII Scan. 
5- Try to mask any table. 
6- Go to the Start masking screen. 
7- Under Additional Options, download the configuration file for review later. 
8- Hit Mask Button. 
9- The Job will be submitted but it will fail with the error saying its unable to connect to the Server.
Environment:
TDM 4.6
TDMWBP
Resolution:
This issue is resolved in TDMWeb-4.6.8.0.  Please contact CA Support for this or a later version.  If you are installing a GA version that is after 20AUG19, please contact CA Support to verify that this resolution is in that version.