Recently when working on a Windows 7 machine I realized it was not installing Windows Updates deployed from the SUP in SCCM 2012 R2.
When checking WUAHandler.log or UpdatesDeployment.log I kept seeing the error 0x8007000e
The error 0x8007000e translates to Not enough storage is available to complete this operation.
The fix was to update the Windows Update Agent from https://support.microsoft.com/en-us/kb/3112343
Windows Update Client for Windows 7 and Windows Server 2008 R2: December 2015
Issues that are fixed in this update
- Assume that you use Software Update agent to apply software updates or determine the software update compliance in System Center Configuration Manager 2007 R2. Windows Update agent scans client computers periodically. In this situation, the scan fails and generates a “Not Required” state for all updates. Additionally, you receive an “8007000E” error message.
After installing this and restating the Windows 7 client machine, I initiated a Software Update Scan cycle from the ConfigMgr agent:
The WUAHandler.log on showed that the agent successfully completed the scan and I was able to install all deployed Windows Updates.
On Server 2012 R2 I was unable to synchronize software updates in my ConfigMgr Current Branch environment. Server Manager kept reporting that the WSUS service was stopped. Each time I would restart the service, it would stop again.
When checking the ConfigMgr logs:
Wsyncmgr.log Sync failed: WSUS server not configured. Please refer to WCM.log for configuration error details.. Source: CWSyncMgr::DoSync
WCM.log Remote configuration failed on WSUS Server.
I previously had no issues with my SUP. Last change was that it was patched as it was a new environment. Upon more research I had applied patch KB3159706
To fix this there were some post update tasks to do which I did not do:
Load up cmd prompt:
cd “C:\Program Files\Update Services\Tools\”
“wsusutil.exe postinstall /servicing”
Then open up Server Manager, add roles and features wizard, in the features section under .Net Framework 4.5, then under WCF Services, select to install HTTP Activation
After this I had to restart my ConfigMgr site server which had the WSUS installed and it was fixed (same issue after restarting the WSUS service, I needed to do a full reboot)
I installed a trial of Configuration Manager 2016 Technical Preview 4 and set up and configured the Software Update point. I wasn’t able to synchronize any updates.
I checked wsyncmgr.log and saw Sync failed: WSUS update source not found on site
The workaround was to configure the Software Update Point and disable/remove all Classifications and Products and then to schedule another sync.
After this, I scheduled another sync, and the sync completed.
I then went back and re-configued the Software Update Point for the Classifications and Products I wanted, then scheduled another sync and it worked fine.
I had quite a few servers that were reporting incorrect compliance for Software Updates to our SCCM 2012 server. After doing Software Updates Scan Cycle on the client, the WUAHandler.log would always say successful. When doing a Software Updates Deployment Evaluation Cycle the log UpdatesDeployment.log said:
EnumerateUpdates for action (UpdateActionInstall) – Total actionable updates = 0
So if there were no updates available to be installed, why were my Software Update compliance reports showing the client as non-compliant and the Deployments in the Monitoring node in the console saying the client In Progress for a Software Update group deployment?
This blog post saved me http://blogs.technet.com/b/scotts-it-blog/archive/2015/02/23/refreshing-state-messages-in-system-center-configuration-manager-2012.aspx
This PowerShell script in the blog above forced my client to re-send its compliance to the SCCM 2012 server:
$SCCMUpdatesStore = New-Object -ComObject Microsoft.CCM.UpdatesStore
Then when checking UpdatesStore.log on the client:
Successfully raised Resync state message.
Resend status completed successfully.
I then checked the SCCM 2012 console in 15 minutes and the Deployments section in the Monitoring node showed the client as Successful instead of In Progress, and the SCCM 2012 update compliance reports showed the client as Compliant.
Another day another scan issue on a Windows Server 2008 R2 with SCCM 2012 client installed.
When checking report of which clients had scan issues, I investigated a particular client which had the following error in WUAHandler.log “OnSearchComplete – Failed to end search job. Error = 0x80244019. Scan failed with error = 0x80244019.”
To get more information, I looked into C:\Windows\WindowsUpdate.log and found:
WARNING: GetAuthorizationCookie failure, error = 0x80244019, soap client error = 10, soap error code = 0, HTTP status code = 404
WARNING: Failed to initialize Simple Targeting Cookie: 0x80244019
WARNING: PopulateAuthCookies failed: 0x80244019
WARNING: RefreshCookie failed: 0x80244019
WARNING: RefreshPTState failed: 0x80244019
WARNING: PTError: 0x80244019
WARNING: Reporter failed to upload events with hr = 80244019.
Is this instance, it was a proxy issue. To view the proxy set from CMD:
netsh winhttp show proxy
My particular server did not need to use a proxy so I reset it by:
netsh winhttp reset proxy
However in some cases, some users have had to add a bypass-list using the <local> parameter for their WSUS server so the proxy is bypassed for the WSUS server. A reboot is needed after this. For more information read “set proxy” https://technet.microsoft.com/en-us/library/cc731131(v=ws.10).aspx#BKMK_5
In an SCCM 2012 environment I was running through some reporting on which clients reported back scan errors so I could fully patch all servers. Upon checking the servers which failed to report software update compliance, I checked the C:\Windows\CCM\WUAHandler.log and saw the error “Failed to run BeginSearch() on WUAgent. Error = 0x80070422”
In my case, this was an easy fix. If you check services.msc you will see that the Windows Update service (or Automatic Updates service depending which version of Windows Server you are running) was stopped or disabled.
After starting this service and running a Software Updates Scan Cycle again, the WUAHandler.log reported that the cycle worked fine.
I was told by a client that they were having issues synchronizing software updates using SCCM 2012.
The first thing I checked was the Wsyncmgr.log to find out what was going on. The Wsyncmgr.log showed “Sync failed: The request failed with HTTP status 503: Service Unavailable. Source: Microsoft.UpdateServices.Administration.AdminProxy.CreateUpdateServer”
On the SCCM 2012 server running the SUP role, I opened up IIS Manager, looked at the Application Pools and noticed that the WsusPool was set to “Stopped“. I started it again and thought it was fixed, but the client advised me that it had crashed again shortly later.
I checked Task Manager on the server and noticed that IIS Worker Process was using 1864.1MB of memory.
I then right clicked on the WsusPool back in IIS Manager, then Advanced Settings, and noticed that the memory limit was set to a lower ammount.
I increased this limit to 4GB to be safe, restarted the WsusPool and then the SUP was able to syncrhonize fine. The Wsyncmgr.log looked good and the problem never came back for the client.