Anything for sysadmins!


WSUS 3.0 SP2 gives error during install

I was trying to install the WSUS 3.0 SP2 patch when it gave me a very non-descriptive error.

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

If you go to


you'll find some log files called wsuspatch####.log that will give you more information. For me it stated that the error occurred in the process



MSI (s) (64:9C) [08:23:13:802]: Note: 1: 1722 2: ExConfigureDb 3: C:\Windows\Installer\MSIFFC2.tmp 4: -S <DBServerName> -F <DBName> -i "C:\Program Files\Update Services\Database\CreateDatabase.sql;C:\Program Files\Update Services\Database\mwus_database_schema.sql;C:\Program Files\Update Services\Database\ServerSync.sql;C:\Program Files\Update Services\Database\ClientWebService.sql;C:\Program Files\Update Services\Database\Setup.sql;C:\Program Files\Update Services\Database\Reporting.sql;C:\Program Files\Update Services\Database\ReportingSummarization.sql;C:\Program Files\Update Services\Database\ReportingRollup.sql;C:\Program Files\Update Services\Database\AdminAPI.sql;C:\Program Files\Update Services\Database\popdb.sql;C:\Program Files\Update Services\Database\EvtNamespaceImport.sql;C:\Program Files\Update Services\Database\SqlSettings.sql;C:\Program Files\Update Services\Database\Inventory.sql;C:\Program Files\Update Services\Database\PublicViews.sql" -l "C:\Users\ADMINI~1.SPI\AppData\Local\Temp\MWusCa.log"

At the end you'll see that the logging option was used (


). This file revealed the next clue:

Changed database context to '&lt;DBName&gt;'.<br/>Msg 1468, Level 16, State 1, Server &lt;DBServerName&gt;,  Line 2<br/>The operation cannot be performed on database "&lt;DBNAME&gt;" because it is involved in a database mirroring session.Msg 5069, Level 16, State 1, Server &lt;DBServerName&gt;,  Line 2<br/>ALTER DATABASE statement failed.<br/>Starting WSUSService...<br/>WSUSService is now started.<br/>StartServer completed successfully.

I'm indeed using mirroring so I disabled it and it installed flawlessly! Don't forget to enable mirroring again afterwards!

Filed under: Microsoft, MSSQL No Comments