Problem
During the installation of the SCSP Managenent Server, it fails while creating the database with the error "Database population FAILED".
Or possibly with the below MDAC error:
Causes & Solutions
1. The SCSPDBA password that was entered during setup was not complex enough.
Specific length must be respected
8 characters minimum including uppercase, lowercase, a number and a non-alphanumeric character (only _ or # are allowed by SCSP).
2. The TCP/IP setting is disable in SQL Server Configuration.
To enable TCP/IP setting in SQL Server Configuration
- In the Microsoft SQL Server Configuration Window, in the left pane expand your server group.
- Right-click TCP/IP and then click Enable.
- Click OK.
- Restart the SQL Server service.
Re-run the Symantec Critical System Protection install.
3. The SQL Browser service is stopped.
Start the SQL Browser service from services.msc
4. The SQL database is offline.
To verify that your database is online
- In the Microsoft SQL Management console, in the left pane expand your server group.
- Look at the icon for your server and verify that the icon for it has a green circle with a white arrow
- If it does not have the green circle with a white arrow, right click and select Start.
Stopped 
to Started .
5. The communication between the CSP Management Server and the SQL Server is blocked.
To verify the communication
In SQL Server 2005, the below command is preferred:
- Open a command prompt.
- Run the command:
OSQL –U sa –P <sa password> -S <hostname or IP address of SQL box>\SCSP (or database instance name used during the install)
-
If successful, 1> will be returned.
In SQL Server 2008, the below command is preferred:
sqlcmd -U sa -P <password> -S tcp:<computer name>\<instance name>
6. Mixed mode for the authentication mode is not selected
To verify the authentication mode
- In the Microsoft SQL Server Enterprise Manager console, in the left pane expand your server group.
- Right-click the your server and then click Properties.
- In the Instance Properties dialog box, on the Security tab, verify that the SQL Server and Windows option button is selected.
- Click OK.
Re-run the Symantec Critical System Protection install.
7. Incorrect instance name used
Make sure to use the correct instance name during the installation
8. Previous installation leftovers.
Manually delete all the files/folders in C:\Program Files (x86)\Common Files\Symantec Shared\SCSP\MSSQL.1\MSSQL\ directory before doing fresh SCSP server installation.
Logs
- %ProgramFiles%\Symantec\Critical System Protection\Server\SISManagementInstallWrapper.txt
- %ProgramFiles%\Symantec\Critical System Protection\Server\SISManagerSetup.txt
- %ProgramFiles%\Symantec\Critical System Protection\Server\msde-dbStatus.txt
Related articles
How to install SCSP with Microsoft SQL Server 2008 R2 Express Edition
SCSP - Error "Database population FAILED"
How to install SCSP agent on Windows, UNIX and Solaris
How to use the SCSP Agent Configuration Tool
How to upgrade SCSP to a newer release
How to import, create and update default policies in SCSP
Configuring Virtual Agents in SCSP 5.2 RU8
How to install the SCSP SymIDS ISAPI filter on Windows Server 2008 R2
Symantec Critical System Protection 5.2 RU9 Docs