Summary

How to configure FlexNet Manager Suite 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.

The following error may be received at the step "Configure the system" during the initial install if using a non-default SQL Server port (that is, not port 1434):

Cause

This problem occurs because the Config.ps1 PowerShell script provided with FlexNet Manager Suite 2019 R1 and earlier is unable to handle a non-default port be specified in the SQL Server instance details.

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 DatabaseHelper.ps1 PowerShell script directly to hardcode the power number.

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 IOJ-1728269 and FNMS-23502.

This problem was fixed in the FlexNet Manager Suite 2019 R2 release.