Commander 9.0.0 has updated our database SQL driver. This driver has new configuration requirements which may result in issues during upgrades. Before this update, the legacy SQL driver accepted both the instance name and the port. The updated SQL driver uses either the instance name or the port to establish the connection but not both.
To confirm whether or not you are using a named instance or a non-standard port, launch the Snow Commander Control Panel on the Commander application server, and switch to the DB Management tab. You are using a named instance if the Instance Name field contains any content other than MSSQLSERVER (the default instance name). You are using a non-standard port if the Port field contains anything other than 1433.
For customers using the default SQL instance and port, no upgrade issues are expected.
Upgrading when using a SQL named instance
Upgrading when using a non-standard port
Upgrading when using a SQL named instance
The installer will automatically drop the port and use the instance name during the 9.0 upgrade. In order for this to be successful, the SQL Browser service must be running on the Commander database service. The SQL Browser service requires UDP port 1434 be opened between the Commander application server and the database server in order to discover the named instance, but the port can be closed after the upgrade completes successfully.Providing that the instance name (PRDCMDR in the image above) is valid, the installer will establish the connection using the instance name. The upgrade will proceed normally.
If the instance name is invalid, replace it with the correct instance name or leave blank for the default SQL instance and click OK. Restart the Commander Services on the Service Control tab, and then proceed with the upgrade.
Upgrading when using a non-standard port
If you are using a non-standard port, clear the instance name field and click OK. Restart the Commander Services on the Service Control tab, and then proceed with the upgrade.
See Also
Related Articles
Resolving Commander Installation or Upgrade Failures 671Number of Views Best Practices for Upgrading Commander® 383Number of Views Perforce connections cannot connect on non-standard ports 3Number of Views Supplementary Steps for Upgrading to Commander VM Access Proxy 3.8 3Number of Views Opening the Commander Control Panel Yields "Unsupported database connection string found. The Control Panel will now close." 6Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Case id: 00001065
Activity: Status change: 2 hours ago