Monthly Archives: July 2013

SCOM: Not all objects on a server are discovered / managed

In the case of an agent that is managing a large amount of objects you may find that not all of them are discovered or if they are that some of them remain in a Not Monitored State. This can be caused by a couple of things.

If you find this error in your OpsMgr event log: “The health service has removed some items from the send queue for management group since it exceeded the maximum allowed size of 15 megabytes”

The the below registry keys need to be adjusted:

  • Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HealthService\Parameters\Persistence Version Store Maximum to 80 MB (5120). Default = 60 MB
  • Set HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HealthService\Parameters\Management Groups\<MG Name>\maximumQueueSizeKb to 100 MB. Default = 15 MB
  • Set HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules\Global\PowerShell\ScriptLimit\QueueMinutes to 120 mins

However if you find this error: In memory container (hash table System.Health.EntityStateChangeData) had to drop data because it reached max limit. Possible data loss.

Then the following registry key need to be adjusted:

  • HKLM\System\CurrentControlSet\Services\HealthService\Parameters:”State Queue Items”, the default value for this key is 1024, depending on the server load double this to 2048 or if the error continues to occur to 4096

I have come across instances where both of these errors occur, after the adjustments were made and the heath service restarted all objects were discovered and monitored correctly.

SCOM – The System Center Management service terminated with service-specific error 5 (0x5).

Not a common error by any means and there are several blog posts out there pertaining to other error codes.
Marnix Wolf has a great article about Error 2147500037

If you get error 5 (0x5) however this means that SCOM is unable to create self-signed certificate.

In our case local system did not have full permissions to the server C:\ProgramData\Microsoft\Crypto\RSA\S-1-5-18 directory. Added that and the service started right up.

SQL 2008 – Relocating log files

I needed to move our Data Warehouse and ACS database log files to a new drive, the following is a relatively simple method to move a SQL log file to a new location without needing to detach your database.

ALTER DATABASE DBNAME SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
ALTER DATABASE DBNAME SET OFFLINE;
ALTER DATABASE DBNAME MODIFY FILE ( Name = Log File Name, Filename = ‘Drive Letter:\Log file location.ldf‘);
At this point copy the log file to the new location
ALTER DATABASE DBNAME SET ONLINE;
ALTER DATABASE DBNAME SET MULTI_USER;

The Log file name and file location can be found in the properties of your database under the File Tab.
This method could also be used to move your database file.