Hi,

When trying to start the Command Center, we get the message: "We're sorry, but we could not find what you were looking for."

This is a new installation.

WebServer.log:

12056 3     08/27 11:13:56 ### ### dmConf::GetMongoConnectionString - Exception Message [A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)]

What could have gone wrong here?

Thanks.

I often see SQL Server connection problems when doing a CommServe hardware refresh, but not usually on a new installation.  Are all the Services running?  Usualy a quick indication that there is an SQL Connection String related problem is if the Workflow Engine cannot start.

Services are running. No problems with the Workflow Engine.

An uninstall / reinstall didn't help.

What URL are you hitting in the browser? 

The URL should be: https://<HOST>/adminconsole 

Also, can you check if this loads: https://<HOST >/webconsole?

URL is correct, although with IP address (tried also with short name, server is not in domain).

Webconsole gives the same error message.

The SQL Server Agent (COMMVAULT) btw is stopped and the option to start it manually is greyed out.

I believe I have seen something similar which came about when the SQL Management Tools (e.g. Management Studio) were not installed during the installation.

The reason in my instance is that I believe someone unpacked the Media Kit and the user chose to ignore that the extracted path exceeded 255 characters, which resulted in being about six files short of what was needed for the install.  The core SQL Server services were installed, but the SQL Tools like SQL Management Studio were skipped.  In my instance I could not easily uninstall SQL Server because there were some core windows registry values missing.  The simplest solution was to reinstall the Operating System, but after a bit of persistence with the registry I was able to make sufficient changes in the windows registry to uninstall the SQL Server, then reinstall the extracted Media Kit from a shorter path.