"Database population failed” when configuring the Symantec Critical System Protection (SCSP) Server to use a custom port to communicate with the SQL DB
|Article:TECH194274|||||Created: 2012-08-01|||||Updated: 2012-10-29|||||Article URL http://www.symantec.com/docs/TECH194274|
During a new SCSP 5.2 RU8 MP4 installation, a database population failure occurs when configuring the SCSP server to use a custom TCP port to communicate with the SQL DB Server.
"Database population failed” error is encountered during the SCSP Server install.
Microsoft does not allow an SA login with hostname/default instance name. For e.g. MyMachineName/MSSQLSERVER.
One needs to specify only hostname and the password. However, if just the hostname is entered the install dialog with go through but will gernerate an error during the install ahead.
Fixed in: 5.2.9 MP1 (estimated availability in December)
1. Before starting the install, log into the SQL Server Managament Studio and delete:
a. the SCSPDB
b. the accounts [i.e. SCSP_OPS…etc.]
2. Ensure that the SQL Browser Service is running
3. Start the installation and as soon as the JRE starts getting extracted, pause the installation and go to the tempdir/ search for dbtableloader.txt and msde_params.bat and replace the instance name with MSSQLSERVER
4. Resume the installation
5. Go to tomcat /conf/server.xml files and update the instance name with MSSQLSERVER
NOTE: Do not use a % in the password. This is not currently supported.
There are 2 ports involved in MS SQL, (1) the discovery port  and (2) the actual instance service port [1433 by default].
Article URL http://www.symantec.com/docs/TECH194274