I’m currently attempting to setup our compliance server and have run into a snag. I have a ticket open with IBM support, but right now we’re still researching/looking into the issue.
I followed the setup instructions that are in the Compliance Setup fixlet and installed the compliance piece on the destination server. I also installed SQL Server 2016. I’m on a terminal server and using IE, I’m attempting to finish up the compliance setup and creation of the application database, but I’m running into this error:
For host, I’ve tried everything from the full name of the compliance server, the IP, and even just “localhost” and keep getting this “could not connect to localhost” error. I’ve tried Windows Auth as well as SQL Server Auth using an SA account that I know is on the SQL server. I have verified that the ports are open for 1433, 433, and 52311 from the terminal server to the compliance server, and in our hardware firewall rule I don’t see any explicit denies so I’m at a loss.
I’m able to ping the compliance server, port 1433 is open and listening on it, so I’m not sure what the issue could be. Has anyone experienced this before?
Edit: I had not preemptively setup the database on the compliance server yet because I assume that this step does that. Maybe I’m wrong?