SCSP - Error "Database population FAILED" or "MDAC"

book

Article ID: 156006

calendar_today

Updated On:

Products

Critical System Protection Data Center Security Server Data Center Security Server Advanced

Issue/Introduction

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:

Resolution

Causes & Solutions

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

  1. In the Microsoft SQL Server Configuration Window, in the left pane expand your server group.
  2. Right-click TCP/IP and then click Enable.
  3. Click OK.
  4. 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

 Check the collation was set to Latin 

 

4. The SQL database is offline.

To verify that your database is online

  1. In the Microsoft SQL Management console, in the left pane expand your server group.
  2. Look at the icon for your server and verify that the icon for it has a green circle with a white arrow 
  3. 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:

  1. Open a command prompt.
  2. 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)
  3. 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

  1. In the Microsoft SQL Server Enterprise Manager console, in the left pane expand your server group.
  2. Right-click the your server and then click Properties.
  3. In the Instance Properties dialog box, on the Security tab, verify that the SQL Server and Windows option button is selected.
  4. 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.

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

  1. To confirm if Dyname Ports is disabled:
  2. On the SQL Server open Sql Server Configuration Manager.
  3. Expand SQL Server Network Configuration
  4. Select Protocols for <Your SQL Instance>
  5. In the right pane right-click TCP/IP and click Properties.
  6. Go to the IP Addresses tab.

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.

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

 

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

 

 

 

 

Attachments

defaultcollation.gif get_app