Hi Ivan, Sherry, These are Windows 7 clients and I’ve noticed my compliance percentage dropping in the last few months. I did look at that google article Sherry sent and thought I really don’t want to make that change as a fair percentage of the boxes are updating correctly so it couldn’t be something on the version of the update going out. I am thinking that they would have gotten the new update agent. That update is approved in September, but is listed as superseded and expired. Windows 8 and 10 clients seem to be fine. I’ll look closer at the update agent and the version on the failed clients. Thanks.
From: [email protected] [mailto:[email protected]] On Behalf Of Lindenfeld, Ivan Sent: Tuesday, December 22, 2015 1:25 PM To: [email protected] Subject: RE: [mssms] mssms: Not enough storage available to complete operation- Scup errors Hi Latisha, That’s the error that the pre-fixed Windows Update Agent from May-ish 2015 gives out. We had to update the WUA everywhere and/or upgrade WSUS so it pushed a newer version of WUA. This was the fix, I am trying to find the blog / article with the symptom https://support.microsoft.com/en-us/kb/3083324 Ivan From: [email protected]<mailto:[email protected]> [mailto:[email protected]] On Behalf Of Sherry Kissinger Sent: Tuesday, December 22, 2015 3:55 PM To: [email protected]<mailto:[email protected]> Subject: Re: [mssms] mssms: Not enough storage available to complete operation- Scup errors Google fu had this: https://social.technet.microsoft.com/Forums/en-US/7e017afd-cdc8-4387-863e-da7bbd74bad8/sccm-2012-r2-wsus-clients-not-updating-after-upgrading-to-cmr2?forum=configmanagersecurity Seems pretty complex, but maybe? Also possibly... some wacked GPO that is hitting 40% of your clients for WSUS settings, but not the other 60%? in windowsupdate.log, what's the EXACT error message there? Especially the 0x800Whatever error code? about 80% of the time when I'm t-shooting strange CM Software Update issues, it's really the WSUS error codes that lead me to the solution, not the CM error codes. Not enough storage usually really means memory issues. there was an update to the Windows Update Agent (for Windows 7) in June, and then another one just a few weeks ago. If these are Win 7 targets, do they have the latest WUAgent (which is supposed to help w/memory issues) ? On Tuesday, December 22, 2015 2:22 PM, "Taxter, Latisha" <[email protected]<mailto:[email protected]>> wrote: Sccm 2012 R2 SP2. About 40 % of clients fail scan with error “not enough storage available to complete operation”. Ran wsus cleanup wizard. Number of updates in deployment package is under 1000. Scanagent.log on a working client has no errors. On a client that failed, “Sources are current, but Invalid. TTL is also invalid.” Any pointers on this will be appreciated. Latisha Taxter Server Administrator III Kootenai Health 2003 Kootenai Health Way Coeur D’Alene, Idaho 83814 • 208-625-4192 [email protected]<mailto:[email protected]> kootenaihealthit.org<http://www.kootenaihealthit.org/> [cid:[email protected]] ________________________________ NOTICE: The information contained in this message is proprietary and/or confidential and may be privileged. If you are not the intended recipient of this communication, you are hereby notified to: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately.
