Support for Named SQL Instance and custom SQL Port

[ChrisMoreland]

Hi All,

I just wanted to check if anyone knows whether UIM Installation is supported on a named SQL Server instance with a custom SQL Port (Not 1433)?

I am trying a new, clean install to such an environment and receive an error:

Failed to connect to database server with provided field values. Recheck fields for accuracy.
Login failed for user 'db user name'. ClientConnectionId: f11a...........

------------------------------
KR,
Chris
------------------------------

[Danny Moran]

Not sure about a clean install, but I can't see why it wouldn't work using a different port than 1433.

Our MSSQL database was migrated to a new cluster and in the process, the access port changed from 1433 to 52580. We just updated the port in the data_engine and it worked fine without any additional modifications. We have since done multiple upgrades and they have all worked fine using the new port.

Are the credentials/permissions for the account used to connect to the database correct? if it was having difficulty connecting, would it not give a connection error rather than a login failed error?

Might be one for Broadcom support.

[Andrew Cooper]

Kris

Non-standard ports are definitly supported, we use MS-SQL Listener so named instances are not an issue (as they are not visible so I cannot comment on this part.  Upgrades use the data_engine connection parameters as @Danny Moran points out, however a "new install" uses some very old ms-sql utilities (the install scripts have not been updated in xx years) which do not support specifying the ports seperately so you may find you need to include it in the host string (its been awhile (read years) since I have had to do a "new" install) but certainly we got 20.x to install with a non-standard port.

If I remeber correctly we had to "test" with the commandline tools (sqlcmd  or osql or such) directly to find the correct parameters to use so that we got a good install.  On a final note we first use a SQL account to install UIM then we updated primary hub (robot + data_engine) to use Windows authentication and then installed UMP (on another robot) and then finally CABI on a 3rd robot  (note: CABI has non-trival definitions for the database connection and we never found a way to change authentication schemes without re-installation (maybe someone else has a better experience), but my recommendation is get UIM and UMP database authentication worked out (SQL, Windows, MSA) and then do the CABI install.

Good Luck, Andrew

------------------------------
Knows a little about UIM/DXim, AE, Automic
------------------------------

[ChrisMoreland]

Thanks Andrew,

So I did get it to install, using both non standard SQL port and a named instance now. What I had to do was use Windows Authentication (AD) to perform this, as a SQL user would not work and kept throwing that error.

Very interesting, as the SQL user had sysadmin rights, and whether I tried to create the DB before hand, or let the installer create a new DB, I would get an error. But when I used AD, then I could do it without any issues at all.

I will try to pass onto support too, so that they may be able to look into it at some point.

Thanks again for the advice.

------------------------------
KR,
Chris
------------------------------

[Stephen Danseglio]

Hi Chris,

I posted a message about configuring named instances some time ago - not sure if you came across it.

https://community.broadcom.com/enterprisesoftware/viewdocument/tech-tip-uim-how-to-use-the-sqls?CommunityKey=170eb4e5-a593-4af2-ad1d-f7655e31513b&tab=librarydocuments

Steve

------------------------------
Support Engineer
Broadcom
US
------------------------------