A new version of the SharePoint 2013 management packs has been released which fixes the report deployment bug which causes the following error “Failed to deploy reporting component to the SQL Server Reporting Services server. The operation will be retried.”
This version is 15.0.4557.1000 and can be downloaded below:
As of 2013-09-06 a new management pack has been released for SQL:
2013-09-12 Note: Issues are currently being reported with with this version of the SQL MP: Error ID 11052 “
Module was unable to convert parameter to a double value Original parameter: ‘$Data/Property[@Name=’CPUUsage’]$’ Parameter after $Data replacement: ‘-1.#IND’ Error: 0x80020005 Details”
Below is the new feature information from the site / guide, there are several new rules and monitors which offer a deeper look into your SQL environments:
The Management pack for SQL Server provides the capabilities for Operations Manager 2007 R2 and Operations Manager 2012 to discover SQL Server 2005, 2008, 2008 R2, and SQL Server 2012. It monitors SQL Server components such as database engine instances, databases, and SQL Server agents.
The monitoring provided by this management pack includes performance, availability, and configuration monitoring, performance data collection, and default thresholds. You can integrate the monitoring of SQL Server components into your service-oriented monitoring scenarios.
In addition to health monitoring capabilities, this management pack includes dashboard views, diagram views and extensive knowledge with embedded inline tasks, and views that enable near real-time diagnosis and resolution of detected issues.
Important Prerequisite Notes:
Clusters: In order to ensure that all monitoring works correctly for clustered instances of SQL Server ensure that your OpsMgr agents on the physical nodes of the cluster are running either OpsMgr 2007 R2 or OpsMgr 2007 SP1 with the most recent cumulative update for OpsMgr 2007 SP1 applied or OpsMgr 2012.
Feature Summary:
The following list gives an overview of the features of the SQL Server management pack. Refer to the SQL Server management pack guide for more detail.
New features:
New Dashboard for SQL Server 2012 DB
New Monitors and Rules – only for SQL 2008 and SQL 2012
Collect DB Active Connections count
Collect DB Active Requests count
Collect DB Active Sessions count
Collect DB Active Transactions count
Collect DB Engine Thread count
Thread Count monitor
Transaction Log Free Space (%) monitor
Transaction Log Free Space (%) collection
Collect DB Engine CPU Utilization (%)
CPU Utilization (%) monitor for DB engine
Buffer Cache Hit Ratio monitor
Collect DB Engine Page Life Expectancy (s)
Page Life Expectancy monitor
Collect DB Disk Read Latency (ms)
Collect DB Disk Write Latency (ms)
Disk Read Latency monitor
Disk Write Latency monitor
Collect DB Transactions per second count
Collect DB Engine Average Wait Time (ms)
Average Wait Time monitor
Collect DB Engine Stolen Server Memory (MB)
Stolen Server Memory monitor
Collect DB Allocated Free Space (MB)
Collect DB Used Space (MB)
Collect DB Disk Free Space (MB)
SQL Re-Compilation monitor
Run As configuration changes to support Low privilege for SQL Server 2012 Cluster
Additional features:
AlwaysOn Monitoring
Automatically discover and monitor availability groups, availability replicas, and availability databases for hundreds of computers.
Health roll-up from availability database to availability replicas.
Detailed knowledge with every critical health state to enable faster resolution to a problem.
Seamless integration with Policy based management (PBM)
Auto-discover custom PBM polices targeting AlwaysOn and database components.
Rollup of health of policy execution within the SQL monitoring pack under extended health.
Support for Mirroring and Replication Monitoring (only applicable to SQL Server 2008 and 2008 R2 version of management pack)
Discover mirroring databases, witness, and mirroring group.
Custom diagram view to visually represent the primary and the mirrored databases.
Approximately twenty rules to detect replication events.
Improved Freespace monitoring with mount point support
Support for Enterprise, Standard and Express editions of SQL Server 2005, 2008, 2008 R2, and 2012 and 32bit, 64bit and ia64 architectures.
Support for both simple and complex SQL Server configurations such as clustered installations, multiple instances and 32bit roles running on a 64bit OS. For full details on supported configurations refer to the guide included with the management pack.
Discovery and monitoring of SQL Server roles such as DB Engine, Reporting Services, Analysis Services, Integrations Services.
Discovery of SQL Server components such as databases, the SQL Agent and SQL jobs.
Views covering areas such as database free space, SQL Server related performance, SQL Server related alerts, and lists of the various SQL Server roles and components which are discovered and their related state.
Discovery and basic monitoring for SQL Server Reporting Services and Integration Services.
Reports for longer-term analysis of common problem areas related to SQL Server such as SQL Server lock analysis and top deadlocked databases, SQL Server service pack levels across discovered roles, user connection activity. Likewise the generic reports from the Microsoft Generic Report Library can be used against the roles and components discovered by the SQL MPs to review availability and performance across many systems and over longer periods of time.
Role and component specific tasks which provide access to common tools, triage information, or corrective actions without needing to leave the Operations Console in most cases.
Monitoring of databases covers database status, database free space, log shipping monitoring for both the source and destination, and transaction log free space.
Monitoring of key SQL Server related services.
Monitoring for persistent SPID blocking.
Monitoring of numerous SQL Server events and performance data points. Alerts bring the issue to your attention and provide knowledge on the impact and possible resolutions.
A low-privilege configuration for discovery and monitoring that eliminates the need for SQL Server sysadmin, dbo, db_owner, and box admin privileges
Sometimes with your SCOM environments you might come across an email relay that does not allow Anonymous authentication. When this happens your notification subscriptions will not be able to send email.
All you need to do is create a windows run as account using credentials which have access to the mail relay and then assign that account to the Notification Account Run as Profile.
Note: The AD account which you use will need an email address which will send your notifications.
Having come across another patch recently which can cause critical issue with SCOM I’ve decided to create a page to record the KB numbers on as well as any relevant additional information.
1.KB2585542 2.KB2775511
1. KB2585542 – This patch will break Unix monitoring due to causing WS-Management connections to UNIX/Linux agents to fail. If this patch is installed on your management servers you can either uninstall it or perform one of the following:
Edit the registry to add this 32bit DWORD value:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\ SendExtraRecord = 2
Or there is a “FixIt” package is available in the KB article under the Known Issues section that can be used to disable the security update
2.KB2775511 – Marnix Wolf has a great article on thisissue. “After installing KB2775511 on Operations Manager Management Servers, agents or servers may be affected by a deadlock. Once in deadlock, Management Servers will generate Heart Beat failures and will go into a “greyed out” state. grayed out. As a result, devices managed by these Management Servers will also go into a “greyed out” or “not monitored state.””
This patch is a combination of 89 hot fixes so ideally you want to avoid installing it. Even though the issue doesn’t occur on all SCOM system it would be advisable to wait for an updated bulletin from the MS System Center team before installing it.
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.
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.
A colleague of mine came across a situation where SCOM performance reports were not working due to corrupt performance counters on a particular server. This situation can be easily resolved by rebuilding the performance counters using the lengthly procedure outlined at http://support.microsoft.com/kb/300956/en-us
Sympton:
Event 10102:
In PerfDataSource, could not resolve counter LogicalDisk, Free Megabytes, C:. Module will be unloaded.
One or more workflows were affected by this.
The short version:
On the affected server open an elevated command prompt
Navigate to c:\windows\system32
Type lodctr /R and press enter
Shortly you should see the following message:
Info: Successfully rebuilt performance counter setting from system backup store.
Something I came across with SCOM 2007 but still seems to be an issue with SCOM 2012. In rare cases when an agent exits maintenance mode it will reprocess all events in the event log and generate alerts for old events.
Adding the following registry key will correct this issue:
