CA SDM 17.1 installation against MS SQL Server over a non default SQL port fails

Issue/Introduction:

Some customer installations disable the MS SQL Browser service and configure SQL Server to use non default ports, like 3369, as opposed to the default 1433 port. CA Service Desk Manager (SDM) 17.1 installation against such an installation fails with an error "Unable to create the mdbadmin user"

Install logs show:

Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Named Pipes Provider: Could not open a connection to SQL Server [5]. . 

2018/07/10 13.10.26.156 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired. 

2018/07/10 13.10.26.156 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.. 

2018/07/10 13.10.26.156 INFO [DeployThread: Configuring CA Service Management common tables] [ActiveProcessHolder] Exit Monitor. Process ID (PID): 2424 
2018/07/10 13.10.26.156 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Failed to create mdbadmin user 
2018/07/10 13.10.26.156 DEBUG [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Failed to create mdbadmin user (mdbadmin) for Database Name (mdb) in (RealSDMHostName) Database. 
2018/07/10 13.10.26.156 ERROR [DeployThread: Configuring CA Service Management common tables] [InstallCDB] Creation of mdbadmin user failed.

CA Service Desk Manager (SDM) 17.1 installation against MS SQL Server over a non default SQL port fails with an error "Unable to create the mdbadmin user"

Environment:

SDM 17.1 on MS SQL Server on a non default port

Resolution:

First:
1) on SDM node, invoke SQL Server Configuration Manager
2) SQL Native Client 11.0 configuration (32bit) - Client Protocols - TCPIP -> right click on TCPIP and select properties -> Change the value of the Default port (example: 3369) to the SQL Server port that the remote SQL Server database uses. Click OK
3) Repeat the same to SQL Native Client 11 configuration (this is the 64bit one)

Second:
1) SQL Native Client 11.0 configuration (32bit) - Aliases - Right click on the right pane and select New Alias
2) Alias Name = <SQL Server Host Name>, Port No = <SQL Server port number (3369)>, Server = <SQL Server Host Name>
3) Click OK
4) Repeat 1, 2, 3 but this time for SQL Native Client 11.0 configuration (this is the 64bit one)

Third:
1) Restart SM Installer fully.
2) On Database Configuration window - fill in the correct port # for SQL Server (example: 3369), fill in other details BUT do NOT fill in the Instance Name. The Database Server should have the value of your Database Alias created in SECOND phase above.
3) Complete the details on rest of the screens and now the installer should be successful.

Additional Information:

The above steps to create SQL Alias is not needed on Catalog box, because Catalog uses JDBC.

CA Engineering team is still researching this case via defect DE42550