~20 Office updates failing to install

[krpms]

Working in a domain environment and this affects roughly 350 PCs. When using WSUS or direct MS updates, a number of Office 2010/2013 updates fail to install.

The good news is it doesn't seem to be GP-related, as newly-imaged PCs don't seem to be affected by it. So just leaves our currently-installed base to fix. Obviously reimaging ~350 is out of the question if I want to have a job.

I'm fairly novice as Windows Update is concerned, so bear with me.



edit: error code 80070643.

I've attached the CBS logs, and threw in Windowsupdate.log with them. Couldn't compress the whole CBS folder as there were ~80MB of .CAB files.

 

[Layback Bear]

Noel are expert on such things will need this tutorial completed. It's the same one that is at the top of the page.

http://www.sevenforums.com/windows-...4840-windows-update-posting-instructions.html

 

[NoelDP]

The only error in the CheckSUR or CBS.logs is this

	Line 22159: 2015-09-25 13:56:57, Info                  CSI    0000045a [SR] Repairing 1 components
	Line 22160: 2015-09-25 13:56:57, Info                  CSI    0000045b [SR] Beginning Verify and Repair transaction
	Line 22163: 2015-09-25 13:56:57, Info                  CSI    0000045d [SR] Repairing corrupted file [ml:520{260},l:56{28}]"\??\C:\windows\Help\mui\0409"\[l:22{11}]"diskmgt.CHM" from store

- which SFC seems to have successfully repaired.

The Windowsupdate.log is a different story

2015-09-25	14:47:12:444	4400	d20	Handler	  C:\windows\SoftwareDistribution\Download\1b292d6fcf4a4d84664489f3ac73cabe\img\osfclient-x-none.MSP
2015-09-25	14:47:12:662	4400	d20	Handler	MSP final command line: DISABLESRCPROMPT=1 LOCALCACHESRCRES=0 NOLOCALCACHEROLLBACK=1 REBOOT=REALLYSUPPRESS MSIRESTARTMANAGERCONTROL=Disable
2015-09-25	14:47:12:974	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:13:099	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:13:255	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:13:349	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:13:442	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:13:598	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:13:754	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:14:066	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:14:160	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:14:347	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:17:592	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:18:044	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:18:481	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:18:684	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:18:684	4400	d20	Handler	MSP Error List:
2015-09-25	14:47:18:731	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:18:902	4400	d20	Handler	  No messages in the MSP error list.
2015-09-25	14:47:19:027	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:19:105	4400	d20	Handler	  : MSI transaction completed. MSI: 0x80070643, Handler: 0x8024200b, Source: No, Reboot: 0
2015-09-25	14:47:19:261	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:19:339	4400	d20	Handler	Updating status for update 0.
2015-09-25	14:47:19:448	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:19:557	4400	d20	Handler	  : WARNING: First failure for update {5B8DEF78-F2DF-482B-96C7-C46DECD4839E}, transaction error = 0x8024200b, MSI result = 0x80070643, MSI action = CA_BeginHelpTransaction
2015-09-25	14:47:19:682	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:19:760	4400	d20	Handler	Stopping on first error due to FailOptTerminate.
2015-09-25	14:47:19:947	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:20:103	4400	d20	Handler	Sending completion notification for update 0 ({5B8DEF78-F2DF-482B-96C7-C46DECD4839E}.201).
2015-09-25	14:47:20:213	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:20:337	 460	1594	AU	>>##  RESUMED  ## AU: Installing update [UpdateId = {B8ECB6A7-F583-44E7-9F53-A6D6E4E0BC04}]
2015-09-25	14:47:20:337	4400	d20	Handler	WARNING: Removing sandbox from MSP source list failed. 0x8007066f
2015-09-25	14:47:20:447	 460	1594	AU	  # WARNING: Install failed, error = 0x80070643 / 0x80070643
2015-09-25	14:47:20:462	 460	1d50	Handler	Using CBS interface ICbsSession7
2015-09-25	14:47:20:556	4400	d20	Handler	  : WARNING: Operation failed at update 0, Exit code = 0x8024200B

I suspect that this is a problem with the Office Source Engine - 7Please open an Elevated (Administrator) Command Prompt window and use the following commands....

net start ose
sc qc ose
sc queryex ose
sc qprivs ose
sc qsidtype ose
sc sdshow ose

Copy and paste the output to your reply

Here are some instructions to make life easier
1) To open an Elevated Command Prompt Window (the ECP window), click on Start, All Programs, Accessories – then right-click on Command Prompt, and select Run as Administrator. Accept the UAC prompt.
2) To run the commands easier, highlight the block of commands, and right-click on the highlight – select Copy. In the CP Window, click on the black/white icon at top left – select Paste. The commands will run but may not complete the last command, so hit the Enter Key once.
3) To copy the results... click on the Black/White icon in the top left, and select Edit... 'Select All', and hit the Enter key - then use Ctrl+V or r-click+Paste to paste it into your response.

 

[krpms]

We're on 64-bit office, so I had to change the service name to ose64. In the course of making sure I was right about that, I started the service before running the set of commands you gave me. It started normally, that's why it says the service is already running at the beginning.

Put code tags on it because smilies.

C:\windows\system32>net start ose64
The requested service has already been started.

More help is available by typing NET HELPMSG 2182.


C:\windows\system32>sc qc ose64
[SC] QueryServiceConfig SUCCESS

SERVICE_NAME: ose64
        TYPE               : 10  WIN32_OWN_PROCESS
        START_TYPE         : 3   DEMAND_START
        ERROR_CONTROL      : 1   NORMAL
        BINARY_PATH_NAME   : "C:\Program Files\Common Files\Microsoft Shared\Sou
rce Engine\OSE.EXE"
        LOAD_ORDER_GROUP   :
        TAG                : 0
        DISPLAY_NAME       : Office 64 Source Engine
        DEPENDENCIES       :
        SERVICE_START_NAME : LocalSystem

C:\windows\system32>sc queryex ose64

SERVICE_NAME: ose64
        TYPE               : 10  WIN32_OWN_PROCESS
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, ACCEPTS_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
        PID                : 2324
        FLAGS              :

C:\windows\system32>sc qprivs ose64
[SC] QueryServiceConfig2 SUCCESS

SERVICE_NAME: ose64
        PRIVILEGES       :

C:\windows\system32>sc qsidtype ose64
[SC] QueryServiceConfig2 SUCCESS

SERVICE_NAME: ose64
SERVICE_SID_TYPE:  NONE

C:\windows\system32>sc sdshow ose64

D:(A;;CCLCSWRPLOCR;;;IU)(A;;CCLCSWRPWPDTLOCRRC;;;SY)(A;;CCDCLCSWRPWPDTLOCRSDRCWD
WO;;;BA)(A;;CCLCSWLOCRRC;;;SU)S:(AU;FA;CCDCLCSWRPWPDTLOCRSDRCWDWO;;;WD)

C:\windows\system32>

 

[krpms]

FYI, while digging on this myself I got the idea to try replacing OSE64.exe with one from the installation media. No change.

 

[krpms]

Noel, did you forget me?

 

[NoelDP]

No - just been rather busy both here and in what they call 'real life'
Office problems are a bit of a different ballgame to Windows ones - they follow different rules, and are a lot rarer, so I never get much experience with them.
The data you posted looks fine to me, so we'll have to look elsewhere...

Please open Device Manager.
Click on 'View' > 'Show hidden Devices'

Now look down the listing - are there any devices showing yellow warning triangles or red 'X' error icons?
If so, what's the detail?

 

[krpms]

No, no device errors present.

Also, I've found that I can manually install these patches if I download the installer from the KB article and run it. I could probably implement a dirty fix and deploy each fix individually, but I'd prefer to find and fix whatever is wrong here.

 

[NoelDP]

If the patches are installing OK from the standalone, then whatever was broken is likely fixed already, and you're just catching up on the affected residues - install the other patches the same way, working from the oldest to the newest, and hopefully they'll all go on, and WU will then work normally.