PowerShell script process fails when non default SQL port is used

[#1]

Summary

How to configure FNMS with a custom SQL Server port, instead of the default 1434

Symptoms

When installing FlexNet Manager Suite, you are asked to enter the Database information at the beginning of the install when running the Config.ps1 PowerShell script.
Customers may get the following error at the step "Configure the system" during the initial install if using a non-default SQL Server port 1434:

Exception calling "Open" with "0" argument(s): "A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name
is correct and that SQL Server is configured to allow remote connections. (provider: TCP Provider, error: 0 - No
connection could be made because the target machine actively refused it.)"
At C:\Temp\SP4Install\FlexNet Manager Suite Installer for 2015 R2 SP4\Support\DatabaseHelper.ps1:19 char:2
+ $sqlConn.Open()
+ ~~~~~~~~~~~~~~~
+ CategoryInfo : NotSpecified: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : SqlException

Cause

This error occurs when the powershell scripts attempt to connect to SQL Server that is running on a port other than 1433, and using a comma to enter the port number will break the Powershell Script.

Resolution

The Host, Instance and Port values in the Database configuration screen can be entered in multiple formats based on your environment while using a single quote to escape the comma.
If the database configuration pop-up no longer appears, the wrong settings could have been already saved in the registry and you can use the ForceUpdateConfig argument at the end of the Powershell script command.

Here is an example of the most common scenarios:

1. Using the default SQL Server port 1434 with no custom Instances: ServerName
2. Using the default SQL Server port 1434 with a custom Instance: ServerName\InstanceName
3. Using a custom SQL Server port and default Instance: 'ServerName,PortNumber' (pay attention to the single quotation in this setup)
4. Using a custom SQL Server port and a custom Instance: 'ServerName\InstanceName,PortNumber' (pay attention to the single quotation in this setup)

Here is a screenshot of scenario #4:

Workaround

As a workaround if the above was not successful, you can also modify the Powershell script directly to hardcode the power number.
Please modify "$Server" variable in "DatabaseHelper.ps1" so that the variable contains a correct server name and a port number.

E.g: $connectionString = "Server=ServerHostnameGoesHere,PortNumberGoesHere;Database=$Database;Trusted_Connection=yes;"

In addition when executing the updated scripts due to changing the "DatabaseHelper.ps1" the PowerShell execution policy needs to be modified to bypass the sign checking.
This can be done as follows by changing the execution policy before running the scripts:
Set-ExecutionPolicy -Scope Process -ExecutionPolicy Bypass

Scope limits the execution policy to the single powershell process and Bypass does not perform the signature checks.

Additional Information

This defect is being tracked under reference FNMS-23502.