Hostname: W2016
Instance name: CLARITY
Port: 1433
You wouldn't put "\" in the hostname, and the MSSQL instance name is the value after the "\".
This makes the assumption though that your SQL Server instance is actually running on (the default) port of 1433 though. it might not be, since when connecting via SQL Server Management tools / ODBC, you're using the hostname\instance syntax which relies upon the SQL Browser service running (on port 1434), which will then query SQL Server by that name in order to figure out what the port is for connecting.
If not specifically configured to 1433 (or some other specific port if that one is already in use either by another MSSQL instance/install), then it may be using another port altogether, and that may even be dynamically set instead of static.
You'll need to adjust that under the network config of the SQL Server services in the MSSQL management software, and restart them, to get it to use a specific port if not already set that way.
I would then encourage using another jdbc-based db query tool (e.g. dbeaver, squirrel, or better) to confirm that your MSSQL server is specifically reachable using its hostname and port before getting the CSA to accept it. Reason being that the CSA will "swallow" many misconfiguration reasons without reporting the detailed cause back to you, leaving you with a guessing game to fix things. The other tools will be more specific in their error messages to guide you.
Original Message:
Sent: 07-05-2020 02:48 PM
From: Martti Kinnunen
Subject: Setting up existing Clarity disk on a new server
This relates slightly to
Clarity
but is somewhat different.
I've got Clarity on a system with two disks. The first disk contains mainly the OS and the MS SQL program files. The second disk contain Clarity and db data and log files
What I am trying to do is to install OS MS SQL program files.on a new disk and use the Clarity install and db on the second disk.
What I did is created empty niku and ppm_dwh databases with the same names as before and copied the old data and log files over them.
Run the scripts setting the database and user. Now I can log in to the niku db with Management Studio and see the data.
Installed java and tomcat. I set the environmental variables as the should be. That is as far as I get.
Preinstall check for upgrade says it cannot connect to the database