During the installation or upgrade of the SCSP Managenent Server, it fails while creating the database with the error "Database population FAILED".
Or possibly with the below MDAC error:
1. The SCSPDBA password that was entered during setup was not complex enough.
Specific length must be respected
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
Re-run the Symantec Critical System Protection install.
3. The SQL Browser service is stopped.
Start the SQL Browser service from services.msc
Check the collation was set to Latin
4. The SQL database is offline.
To verify that your database is online
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:
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
7. Incorrect instance name used.
Make sure to use the correct instance name during the installation
8. Previous installation leftovers.
The SQL Instance has Dynamic Ports disabled If the SQL Instance has Dynamic Ports disabled you must specify the port 1433 in the Hostname field during installation. Example: <Hostname Or IP Address>:1433
If TCP Dynamic Ports does not have a value and a port is specified in TCP Port, Dynamic Ports is disabled. 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.
- %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
9. Database owner has been changed
Database owner should be scspdba. If it is set to anything else, change it back to scspdba
Use SQL Management Studio to change the database owner
10. Model Database is too large
Initial database creation begins with copying the Model database. CSP/DCS requires that the Model database be 49MB or less at time of install
Use a different SQL instance with a smaller Model database or Shrink the Model database
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe
Thanks for your feedback. Let us know if you have additional comments below. (requires login)
This will clear the history and restart the chat.