Database Population FAILED when install the SCSP server on a SQL Server 2008 cluster

Article:TECH177847  |  Created: 2011-12-28  |  Updated: 2012-07-21  |  Article URL http://www.symantec.com/docs/TECH177847
Article Type
Technical Solution

Product(s)

Issue



when trying to deploy the SCSP server in a SQL Server 2008 cluster environment, the installation was interrupted and threw out error message "Database Population FAILED.."


Error



In SISManagementInstallWrapper.log:

Database Population FAILED..
Copying: from C:\Users\ADMINI~1\AppData\Local\Temp\1\{D24E4C75-63ED-4C34-B822-F37D4F75BC16}\{65A60777-4A68-4691-AB60-FC5621BAFD35}\dbScripts\dbTableLoader.txt to C:\Program Files (x86)\Symantec\Critical System Protection\Server\dbTableLoader.txt
Copying: from C:\Users\ADMINI~1\AppData\Local\Temp\1\{D24E4C75-63ED-4C34-B822-F37D4F75BC16}\{65A60777-4A68-4691-AB60-FC5621BAFD35}\dbScripts\msde-dbStatus.txt to C:\Program Files (x86)\Symantec\Critical System Protection\Server\msde-dbStatus.txt
Leaving LaunchDBScriptInstall()..
Entering FailedInstall()..
The Installation has failed. Click Finish to exit the wizard.
Leaving FailedInstall()..
Deleting directory C:\Users\ADMINI~1\AppData\Local\Temp\1\{D24E4C75-63ED-4C34-B822-F37D4F75BC16}\{65A60777-4A68-4691-AB60-FC5621BAFD35}\
Deleting Registry HKLM\SOFTWARE\Symantec\Symantec Critical System Protection Management Server

In msde-dbStatus.txt

---Database Check - SCSPDB at Fri 12/09/2011  1:30:18.46
Login failed for user 'scspdba'.
Msg 18456, Level 0, State 0:
!!ERROR!! DBINS0600 Database SCSPDB Could Not Be Created - Check Log File "C:\Users\ADMINI~1\AppData\Local\Temp\1\{D24E4C75-63ED-4C34-B822-F37D4F75BC16}\{65A60777-4A68-4691-AB60-FC5621BAFD35}\\dbScripts\dbSetupLogs\msde-createdb-SCSPDB.log" for Error Messages, Fri 12/09/2011  1:30:18.85
--------- Ending   Database (SCSPDB) Install-Upgrade Script at Fri 12/09/2011  1:30:18.87 ------------
 

and some errors related with password validation failed


Environment



SCSP 5.2.X

SQL server 2008 Cluster

Windows server 2008


Cause



If the related services of SQL server can be started normally, and the issue still continued, the possible causes are as below:

1. Invalid IP address

2. Invalid SQL Server instance

3. Invalid password


Solution



1. Be sure to enter a valid IP address of SQL Server in a Cluster environment, here is the IP address of the virtual IP in SQL Server Cluster(the IP address of DTC you created).

2. If there is no extra instance created in the SQL server, keep it blank and continue

3. When the installation wizard ask to input the password of scspdba, Please make sure the password fit the requirements as below:
  Password must be :
- 8 to 18 characters long
- containing only letters, numbers, #, and _
- not begining with _
- containing at least two non-letter characters




Article URL http://www.symantec.com/docs/TECH177847


Terms of use for this information are found in Legal Notices