WSUS 30 SP2 Install Failure - Error 0x80070643: Fatal error during installation

Problem:

I was trying to install WSUS 30 SP2, in preparation of SUP install for  my SCCM 2012 SP1 environment.  As you some of you admins especially SCCM folks aware of that SUP relies on WSUS for SCCM based patching. Install kept failing, whatever method I chose to install, either thru Server Manager Add roles / features or downloaded setup executable WSUS30-KB972455-SP2-x64.exe. Install gets kicked of and accepts all of your selections and throws above error which we don’t like much, as it doesn’t reveal needed info to solve the problem.

How to find the root cause of problem:

Now, the hunt began for more info, precisely the location of log files to find more details of failure. Install logs location may vary based on how you install WSUS

                C:\windows\logs\servermanager.log in case if you use “Add Roles” feature using server manger
                %TEMP% which usually resolves to C:\Users\userid\AppData\Local\Temp in case if you used downloaded executable to kick of install

In my case I used downloaded executable and found 3 related logs, each of which are passing information to other.

WSUSSetup.log: This log is kind oversees and passes same info as what GUI throws and very basic
2013-01-18 15:43:39 Error MWUSSetup InstallWsus: MWUS Installation Failed (Error 0x80070643: Fatal error during installation.)
2013-01-18 15:43:39 Error MWUSSetup CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643: Fatal error during installation.)
2013-01-18 15:43:39 Error MWUSSetup CSetupDriver::LaunchSetup: Setup failed (Error 0x80070643: Fatal error during installation.)
2013-01-18 15:43:53 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80070643: Fatal error during installation.)

WSUSSetupmsi_130118_1541.log: This log possess little more details but couldn’t give all, rather pointed to below log for actual details on failure
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 ExConfigureDb…..C:\Users\UserID\AppData\Local\Temp\2\WSUSCa_130118_1541.log"

WSUSCa_130118_1541.log: This is the log which has given suffice and needed info to resolve the issue
Cannot create file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\SUSDB.mdf' because it already exists. Change the file path or the file name, and retry the operation.Msg 1802, Level 16, State 4, Server ServerName, Line 2
CREATE DATABASE failed. Some file names listed could not be created. Check related errors.

How to Resolve:

WSUSCa_****.log has indicated clearly that setup fails to create a file as a file with same name already exists in SQL DB Files folder. I guess file might have created during my earlier attempt of WSUS either standalone or part of SUP install or sorts and MDF/LDF files got created during. Post deleting the same file, which I did as I know it was less risky in my case and reran the install which went smoothly

· Delete any MDF or LDF files that denote SUS Databases from SQL DB files location (Don’t delete these files if they are used for any other purposes)

· Rerun the setup successfully

Also, this error code might not always results similar root cause, so you will need to act on the problem based on the error clues got from above mentioned log files

--- Thanks, Vasu Miriyala

 

BGB, What is this new component/log in SCCM 2012 SP1

Post install SP1 of SCCM 2012, as usual typical admin task was to check all components logs to find how was site doing. To my surprise there are few logs that weren’t observed in any of previous version of SMS or SCCM. Going through these logs dint reveal much info on what they are all about, but could see it is a new role installed thru and by SCCM only (rolesetup.exe /install /siteserver:MYSERVER SMSBGB 0) .

C:\Program Files\Microsoft Configuration Manager\Logs>dir *bgb*

16-01-2013  18:14           325,900 bgbisapiMSI.log
16-01-2013  17:13           310,868 bgbisapiMSI.log.LastError
16-01-2013  21:38           955,927 bgbmgr.log
16-01-2013  12:12              2,621,583 bgbmgr.lo_
16-01-2013  21:34            55,694 BgbServer.log
16-01-2013  18:14           318,539 BgbSetup.log

I could see from snippet of logs mentioning install of BGB components hence I did try to install it those msi ("C:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi) myself, hoping I will get clue on these app/program, but it started a program with “BGB http Proxy” which I have never heard, guess so is Google. I quit that program as safety measure, please don’t tell anyone J

Ok, I took longer breaths to calm down and to simplify my search with log snippets, msi names etc and finally cracked it……and would like to share with you that this is the new game changing component introduced for the first time in SMS/SCCM versions with SCCM 2012 SP1, that allow us to push notifications (policies as we know them) to SCCM Client with objective of assigning them immediate actions to perform , instead of waiting till its policy interval usually, such push may help fasten tasks like OOB patch etc. This new feature called “Client Notification” is interesting compared to Pull mechanism that SMS/SCCM clients use traditionally and comprises of Notification Server, Notification Manager (on Server) and Notification agent (on Client) components to function. More info and credits to Randy XU’s blog below. Also write up on Client Notification by Randy is one the best articles that I have seen for its quality despite being quantitative. BTW, I still need to explore this feature and will share more from the floor when I do so

http://blogs.technet.com/b/configmgrteam/archive/2012/10/11/3522960.aspx

 

--- Thanks, Vasu Miriyala

System Center Configuration Manager (SCCM) 2012 SP1 & PowerShell

Post installing or upgrading to System Center Configuration Manager (SCCM) 2012 SP1, PowerShell is one of the features you will be excited to try. Though needless to introduce you to the benefits of PowerShell in general, but in short introduction of PowerShell cmdlets (~470) in SCCM 2012 SP1 release, helps to automate otherwise repetitive administrative tasks in SP1 environment. Also it helps to systematic passion to execute of tasks thru such automation, as ruling out manual efforts may eliminate errors.

Though Integrating PowerShell module (importing.. precisely) in SCCM is easier there are few points that helps you to know in advance to save your time, as it sounded little confusing especially when you have Windows Server 64 bit, as PowerShell module that will be loaded is 32 bit.

Prerequisites:

SCCM 2012 SP1, which has prerequisite for its successful install/upgrade i.e. Windows Management Framework 3.0 which in turn brings in PowerShell 3.0. SP1 install or upgrade copies necessary PowerShell Models for SCCM 2012 SP1 sites administration, this file is located under C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin\ ConfigurationManager.psd1. Either this modules needs to imported manually or it will be loaded automatically based on how you connect to PowerShell for SCCM 2012 SP1 administration. So in a way all if you install SP1 successfully PowerShell cmdlets are almost there on your SCCM server but just needs to be imported to use in your PowerShell session  

 How to connect to PowerShell:  

1)  You can use SCCM console to connect to PowerShell, which will import automatically ready to use cmdlets of SCCM 2012 SP1 administration. Connecting to PowerShell this way, takes you to PowerShell context that is ready to use cmdlets of Configuration Manager  

                                                                Or

2)  If you are on 64bit OS, Launch x86 flavor of PowerShell and import SCCM 2012 SP1 module into that session

a.       Start > Run > “%SystemRoot%\syswow64\WindowsPowerShell\v1.0\powershell.exe”

Or Start > PowerShell > Select PowerShell (X86)

b.       Import module below way and you will be connected

                                                               i.      cd ‘.\Program Files (x86)\Microsoft Configuration Manager\AdminConsole\bin’

                                                              ii.      Import-Module .\ConfigurationManager.psd1

                                                            iii.      Set-Location <3 letter sitecode>:    (Example: Set-location CEN if you site code is CEN)

 

How to get started:  

Once you are successfully connected to PowerShell module of ConfigurationManager, context of PowerShell displayes 3 letter site code of your SCCM site. Configuration Manager cmdlets are available for execution in this context only. If you change context to C: drive or so cmdlets of SCCM won’t be available

            PS JAN:\> Get-Command -Module ConfigurationManager   (This gives list of cmdlets available for configuration manager administration)

         
How to get help:
Default cmdlets of help to an extent like get-help, get-help –examples etc but “get-help –online” doesn’t seem to provide much help as online links aren’t going to specific cmdlets but opens up SC tech resources page. Hope MS will fix it shortly

What to try:

Like newbee to SQL or Scripting, it is wise to try all cmdlets that retrieve information from site but not make any changes. They are start with Get, like Get-cmmanagementpoint, for example provides info on MP of that site. Once you are more comfortable then rest of the categories like set, add, remove J etc

You may find below sources help you take your learning’s to next to level get stronger grip on this module. Microsoft has taken great amount efforts to make the job easier as approximately 470 cmdlets should be more than suffice and ideally allow us to automate literally any action on You onfiguration manager administration. I am sure you will enjoy these features as they allows us to focus more on even better and value added tasks for organization… Enjoy !!!

 http://technet.microsoft.com/en-us/library/jj821927.aspx

http://cm12sdk.net/?page_id=1623