Issue:
During the install of Shavlik Protect 9.0 Patch 1 install or when patching Shavlik Protect 9.0 with Patch 1 the install fails.
Symptoms:
Protectupdate*.log in the %temp% directory shows "Error 1722"
MSI (s) (2C:C0) [17:53:28:738]: Note: 1: 1722 2: SetupDatabaseAction 3: C:\Program Files\LANDesk\Shavlik Protect\ST.DatabaseConfiguration.exe 4: -quiet -upgrade -consoleId <GUID> -timeout 1800
CustomAction SetupDatabaseAction returned actual error code 1 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (2C:C0) [17:53:32:763]: Product: Shavlik Protect -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SetupDatabaseAction, location: C:\Program Files\LANDesk\Shavlik Protect\ST.DatabaseConfiguration.exe, command: -quiet -upgrade -consoleId <GUID> -timeout 1800
The error occured while running ST.DatabaseConfiguration.exe.
Checking the ST.DatabaseConfiguration.log shows one of the following errors:
ST.DatabaseConfiguration.log error scenario 1
2013-07-08T23:55:09.1875831Z 0005 E DatabaseInstaller.cs:561|SQL install script error: System.Data.SqlClient.SqlException (0x80131904): The operation cannot be performed on database "<DB_Name>" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group.
ALTER DATABASE statement failed.
Fix for ST.DatabaseConfiguration.log error scenario 1:
Remove database from SQL High Availability "Mirroring/Synchronize"
Run install again.
ST.DatabaseConfiguration.log error scenario 2
2013-09-13T14:21:26.0718307Z 0004 E DatabaseInstaller.cs:928|SQL or data conversion error. Failed to execute the installation.: System.Data.SqlClient.SqlException (0x80131904): Only members of the sysadmin role or the database owner may set the database compatibility level.
Fix for ST.DatabaseConfiguration.log error scenario 2:
Ensure that upgrade file is run while logged in as a user that is a member of the sysadmin role or is the database owner
Run install again