Friday, April 13, 2012 2:50 AM
I've question about the size limit on the WMI repository (being 4GB). If this isn't the correct place to post this, apologies and can someone let me know wheere to post this?
I've come across a few servers running Citrix that have reached their limit on the WMI repository size and we need to install the IBM Director agent for HW monitoring. During the install we are getting 'out of disk space' errors entered in the mofcomp.log:
"(Mon Apr 02 04:10:36 2012.172843) : An error occurred while processing item 4:
(Mon Apr 02 04:10:36 2012.172843) : Error Number: 0x8004103b, Facility: WMI
Description: Out of disk space"
When i look up this Error number from http://msdn.microsoft.com/en-us/library/windows/desktop/aa394559%28v=vs.85%29.aspx
I see this:
- 2147749947 (0x8004103B)
Disk is out of space or the 4 GB limit on WMI repository (CIM repository) size is reached.
Windows XP and Windows 2000/NT: Disk is out of space.
I'm just wondering if there is any reason why the limit is set to 4GB or can you increase it as needs be? I can't seem to find any reason for this anywhere.
Or on the other hand, is there any way of identifying the obsolete objects in the repository that could be removed manually?
Cheers to anyone that can advise.
Friday, April 13, 2012 7:32 AMModerator
Based on your description, I suggest you rebuild the WMI repository. For Windows Server 2003, there are no built-in switches to rebuild the Repository, so you must do it manually. Please note that rebuilding the WMI repository has repository has resulted in some 3rd party products not working until their setup is re-run & their MOF –re-added back to the repository.
Follow these steps:
1.Change startup type to Window Management Instrumentation (WMI) Service to disabled
2.Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
3.Rename the repository folder: C:\WINDOWS\system32\wbem\Repository to Repository.old
4.Open a CMD Prompt with elevated privileges
6.for /f %s in ('dir /b /s *.dll') do regsvr32 /s %s
7.Set the WMI Service type back to Automatic and start WMI Service
8.cd /d c:\ ((go to the root of the c drive, this is important))
9.for /f %s in ('dir /s /b *.mof *.mfl') do mofcomp %s
10.Reboot the server
After rebuild the WMI Repository, please also install this Hotfix: http://support.microsoft.com/kb/2257980
In addition, for the detailed WMI Repository issue information, I’d like to share these with you:
WMI: Rebuilding the WMI Repository
Suggested hotfixes for WMI related issues on Windows platforms *Updated December 14th 2011*
TechNet Community Support
Monday, April 16, 2012 2:22 AM
Thanks for the info regarding the issue that i am having.
I have gone through the various tests to see if the repository is corrupted and they all have been successful, so it doesn't look like its corrupted. WMIDiag doesn't show up anything either.
I haven't rebuilt the repository, as you have said some apps (3rd party) may stop working and seeing as this is a Citrix server and there are loads of 3rd party apps installed on it, it may not be such a wise idea.
The hot-fix 2257980 is already installed on the server, so i won't need to install that.
What I may have to do is place a call with MS to see if there's anything they can do.
Thanks for the response,