CBS.log file HUGE
SFC.exe has not been run on the system. I see in this article that the file is suppoed to be compressed, but that is not happening. I was able to delete CBS.log after stopping the Windows Modules Installer (actually, stopping and restarting the
service seems to generated a new CBS.log file)
September 1st, 2012 8:15am
One other item of note, affected servers so far have all been VMs. (vSphere 5.0)
C:\Users\dhutch>set
ALLUSERSPROFILE=C:\ProgramData
APPDATA=C:\Users\dhutch\AppData\Roaming
CLIENTNAME=7210
CommonProgramFiles=C:\Program Files\Common Files
CommonProgramFiles(x86)=C:\Program Files (x86)\Common Files
CommonProgramW6432=C:\Program Files\Common Files
COMPUTERNAME=PRINT1
ComSpec=C:\Windows\system32\cmd.exe
FP_NO_HOST_CHECK=NO
HOMEDRIVE=C:
HOMEPATH=\Users\dhutch
LOCALAPPDATA=C:\Users\dhutch\AppData\Local
LOGONSERVER=\\DC2
NUMBER_OF_PROCESSORS=1
OS=Windows_NT
Path=C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32
\WindowsPowerShell\v1.0\
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
PROCESSOR_ARCHITECTURE=AMD64
PROCESSOR_IDENTIFIER=Intel64 Family 6 Model 37 Stepping 1, GenuineIntel
PROCESSOR_LEVEL=6
PROCESSOR_REVISION=2501
ProgramData=C:\ProgramData
ProgramFiles=C:\Program Files
ProgramFiles(x86)=C:\Program Files (x86)
ProgramW6432=C:\Program Files
PROMPT=$P$G
PSModulePath=C:\Windows\system32\WindowsPowerShell\v1.0\Modules\
PUBLIC=C:\Users\Public
SESSIONNAME=RDP-Tcp#0
SystemDrive=C:
SystemRoot=C:\Windows
TEMP=C:\Users\dhutch\AppData\Local\Temp\2
TMP=C:\Users\dhutch\AppData\Local\Temp\2
USERDNSDOMAIN=DOMAIN1.NET
USERDOMAIN=DOMAIN1
USERNAME=dhutch
USERPROFILE=C:\Users\dhutch
windir=C:\Windows
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2012 10:32am
I've had low disk space reports generated on (4) 2008 R2 servers so far as a result of the CBS.log file growing to over 7GB in size (c:\windows\logs\CBS\CBS.log)
Most of the entries in the file are similar to these:
2012-08-15 09:17:17, Info CBS Session: 30243568_2899427469 initialized by client WindowsUpdateAgent.
2012-08-15 09:17:17, Info CBS Read out cached package applicability for package: WUClient-SelfUpdate-ActiveX~31bf3856ad364e35~amd64~~7.4.7600.226,
ApplicableState: 64, CurrentState:0
2012-08-15 09:17:32, Info CBS Failed to internally open package. [HRESULT = 0x800f0805 - CBS_E_INVALID_PACKAGE]
2012-08-15 09:17:32, Info CBS Session: 30243568_3047164206 initialized by client WindowsUpdateAgent.
For some reason this file is not being compressed and regenerated like it has in the past.
Two of the servers this has affected are excluded from receiving windows updates through WSUS and two servers do get updates via wsus.
Has anyone seen this behavior?
September 1st, 2012 3:45pm
Hello,
Hmm, that is pretty large, the log file should stop at around 50 meg size( last servicing operation has to complete first), a new log is started, the old log is compressed and saved.
Open an elevated cmd prompt and run the set command, report back output, want to check if something was set.
Thanks, Darrell Gorter [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. VAMT - Volume Activation Management Tool - Download link http://www.microsoft.com/downloads/details.aspx?FamilyID=ec7156d2-2864-49ee-bfcb-777b898ad582&displaylang=en
Free Windows Admin Tool Kit Click here and download it now
September 1st, 2012 10:13pm
Maybe this one helps.
http://social.technet.microsoft.com/Forums/en-CA/winservermanager/thread/997105d3-834c-48c0-929d-20389a0ed0f3
Regards, Dave Patrick ....
Microsoft Certified Professional
Microsoft MVP [Windows]
Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
September 1st, 2012 11:30pm