Registry bloat and SBS

Good morning.  I wanted to cover a strange issue I ran into yesterday.


When going to the Computers tab within the Network tab we would receive a popup with the error “The server cannot query power management configuration.”  I did some checking on this and found that if the Windows 7 and Vista GPO (Group Policy Object) was missing that it could cause this issue.  I checked and that GPO was present.  It also had the default settings.

So what could possibly be causing this then?  Anytime there is an error in the SBS (Small Business Server) console the console.log or console2.log should be reviewed.  This log can be found in the C:\Program Files\Windows Small Business Server\Logs directory.  When I checked that log I found this exception:

[45636] 170118.101919.9681: ClientSetup: Handled exception: ErrorCode:0
BaseException: Microsoft.WindowsServerSolutions.ClientSetup.PowerUtilityException: QuerySleepTimeoutOnAC —> Microsoft.WindowsServerSolutions.Common.GroupPolicy.GPOException: GPOperation.OpenDSGPO —> System.Runtime.InteropServices.COMException: Insufficient system resources exist to complete the requested service. (Exception from HRESULT: 0x800705AA)

Now I have the exception code and message.  Insufficient system resources exist to complete the requested service. (Exception from HRESULT: 0x800705AA).  I have seen these types of issues before in SBS, Essentials and Foundation, so I figured we were running out of heap or nonpaged pool memory.  A telltale sign of this is when the SILSVC (Software Infrastructure License service) fails due to a resource issue.  I checked the log for SILSVC and all checks were passing.  I then did some more searching and found that this error is linked to the SOFTWARE registry hive exceeding the size limit of 2GB.  I checked C:\Windows\System32\config and found that the SOFTWARE registry hive was 2,050,657 KB, which is just over 2GB.

With the issue now identified, I figured a fix should be pretty straightforward.  Unfortunately this was not the case.  The registry hive cannot be compacted while it is in use.  Also Microsoft does not have a tool to trim down the size of the registry.  To make matters worse, the latest backup of the registry hives was 3 years old.  So in this case we decided to try a 3rd party registry cleaning utility to trim down the size of the registry and this is where I left the issue.  With any luck my customer will be able to trim down the size of the registry hive.

I hope you found this informative.  If you have any comments or suggestions, please leave them in the comments below.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s