KB: Configuring the SharePoint 2010 Management Pack for System Center Operations Manager

System-Center-Team · ‎Feb 15 2019

First published on TECHNET on Apr 16, 2012

Here’s another new Knowledge Base article we published today. This one goes through some common tips and troubleshooting for the SharePoint 2010 Management Pack for System Center Operations Manager:

=====

Summary

This article describes the steps to troubleshoot or configure the SharePoint 2010 Management Pack for the following scenarios:

No Access to SharePoint Foundation 2010 and SharePoint Server 2010 Databases
Configuring the Run As Account Association
Unable to monitor multiple farms in local domain or remote domains
How to run the Configuration Task
Unable to run the "Configure SharePoint Management Pack" task in System Center 2012 Operations Manager
Unable to monitor SharePoint 2010 Databases
User Education - Isolating Discoveries
User Education - Sync Time Overrides
User Education - Adding Workflows to SharePoint Config file

Scenario 1 - No Access to SharePoint Foundation 2010 and SharePoint Server 2010 databases
Symptom:

Computers are populated in the "Unidentified Machines" view in the Operations Manager console under Monitoring -> SharePoint 2010 Products -> Unidentified Machines

Several views in the Console under Monitoring -> SharePoint 2010 Products are "blank" or "Not Monitored", these views include:
Administration - Not monitored

Content Databases - Blank

Diagram View - Not monitored

Events - Blank

Farms - Blank

Performance - Blank

Servers - Blank

Service Front Ends - Blank

Services - Blank

Shared Services - Blank

SPHA Rules - Blank

Web Applications - Blank

Resolution: Set the proper permissions on the SharePoint Foundation and SharePoint Server 2010 databases. Enable debug tracing to determine where errors may occur.

Required Permissions
The required permissions for the configured run as account on an individual SharePoint farm are:

Local admin on all SharePoint 2010 Front End and Application Servers
Local admin on all SQL machines that host SharePoint 2010 databases
Full Farm Administrator rights within SharePoint 2010
DBO for all SharePoint databases

NOTE All SharePoint Foundation 2010 and SharePoint Server 2010 databases created during initial setup require the above permissions.
Below is a list of some of the databases in SharePoint Foundation 2010 and SharePoint Server 2010 which require DBO permissions. This is not a complete list as it depends on your specific configuration.

Application_Registry_Service
Bdc_Service_DB
Managed Metadata Service
PerformancePoint Service Application
Search_Service_CrawlStoreDB
Search_Service_DB
Search_Service_Application_PropertyStoreDB
Secure_Store_Service_DB
SharePoint_Config
SharePoint_AdminContent
StateService
User Profile Services Application_ProfileDB
User Profile Services Application_SocialDB
User Profile Services Application_SyncDB
User Profile Services Application_ReportingDB
User Profile Services Application_StagingDB
WebAnalyticsServiceApplication_ReportingDB
WebAnalyticsServiceApplication_StagingDB
WordAutomationServices
WSS_Content
WSS_Logging

NOTE The initial installation account for SharePoint 2010 Foundation and SharePoint 2010 Server already has the necessary permissions required in all databases created during initial installation. It is recommended that you use this installation account to configure the SharePoint Foundation 2010 and SharePoint Server 2010 Management Packs. If requirements for security call for the creation of a new account for the management pack administration and discovery, take into account that you will have to duplicate the same permissions already granted to the SharePoint installation account.

NOTE For a clustered installation of the root management server the SharePointMP.config file must exist in the following directory

For x86 bit version of Windows Server Operating Systems %Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us

For 64-bit version of Windows Server 2008 or Windows Server 2008 R2 copy the SharePointMP.config file to the %Program Files\System Center Management Packs from the %ProgramFiles(x86)%\System Center Management Packs directory

To grant a new account full farm administrator rights:

Open SharePoint 2010 Central Administration.
On the left panel click on Security.
In the middle pane right below Users click on “Manage the Farm Administrators Group”.
If the account you initially installed SharePoint is not already there. Then add SharePoint Run As Account to the group.
Adding the Operations Manager SharePoint account - in the top left corner click on drop down arrow next to “New” and choose Add Users.
Click on the small book icon (browse).
Type in the name of the Operations Manager SharePoint Action Account.
Click on the search icon and wait until it returns the Operations Manager SharePoint Action Account.
Click on the Add button.
Click OK.

Enable Debug Tracing
Enabling Debug Tracing will enable debug trace on those agent computers that run Windows PowerShell script based discoveries and SPHA monitors. By default it is turned off. When it is enabled, the script based discoveries and monitors will write debug trace information to Event Log in Operations Manager channel on all agent computers, and all the debug trace events have an event ID of 0.
To enable debug tracing do the following:

In the Operations Console Select Monitoring.
Select SharePoint 2010 Products.
Select Administration view.
On the Actions panel, click the task named “Set DebugTrace for SharePoint Management Pack”. A Run Task window will popup.
To enable debug trace (the default option), click Run. To disable debug trace, click Override.
Set the Enabled parameter value to “False” in the popup dialog.
Click Override to close the dialog.
Click Run.
Wait for the task to finish in Task Status window, and then check the Task Output to ensure that the task completes successfully.
Click Close.

How to use debug tracing
Run the “Set DebugTrace For SharePoint Management Pack” task then rerun the Admin Task, and then go to Operations Manager Event channel on the server and check events with ID = 0. Look for the timestamp in the event log and then check the SharePoint ULS trace log to ensure that it is the case
For more information about the ULS trace log, see the SharePoint Foundation 2010 documentation on TechNet ( http://technet.microsoft.com/en-us/sharepoint/ee263910.aspx ).

Configure the "More Secure Option"
The More Secure option will deliver the configured credentials only to the machines specified in this section. The credentials sent will be for the purpose of discovering and monitoring the SharePoint farms specified. The machines in this list should be the same machines specified in the SharePointMP.config file. The requirement is to have all distributed application components listed for each individual farm. This would include front end server and SQL servers that host the SharePoint databases or any component thereof.

To configure the More Secure Option do the following:

Option 1 - Create the Run As Account and configure

Open the Operations Manager Console.
Go to the Administration tab.
Expand the Security node.
Right-click Run As Accounts.
Select Create Run As Account and Click Next.
Set the Run As Account Type as "Windows", give it a Display Name and Click Next.
Enter in the Credentials for the Active Directory Domain User Account and Click Next.
Select "More Secure" option and add all of the servers that are part of the SharePoint farm. This will include all SharePoint Frontend, Application and SQL Servers for that SharePoint farm.
Click Create.

Option 2 - Configure an already existing account

Open the Operations Manager Console and navigate to the Administration Tab.
Expand the Run As Configuration node and highlight Accounts.
In the middle panel open an existing Run As Account from the middle pane under Type: Windows
right click the account and choose properties.
Click on the Distribution Tab.
Select "More Secure" option and add all of the servers that are part of the SharePoint farm. This will include all SharePoint Frontend, Application and SQL Servers for that SharePoint farm.
Click OK.

NOTE Distribution of Security ensures that all the servers that are part of the SP Farm are selected and included here. We recommend having one set of Operations Manager servers monitor only one SharePoint farm. We do not recommend having multi-homed agent computer (SharePoint servers that are monitored in multiple Operations Manager management groups).

Scenario 2 - Configuring the Run As Account Association
Symptoms

Several views in the Console under Monitoring -> SharePoint 2010 Products are "blank" or "Not Monitored", these views include:

Administration - Not monitored

Content Databases - Blank

Diagram View - Not monitored

Events - Blank

Farms - Blank

Performance - Blank

Servers - Blank

Service Front Ends - Blank

Services - Blank

Shared Services - Blank

SPHA Rules - Blank

Web Applications - Blank

The following error message can be seen when the Run As Account Association is not configured properly due to syntax
Example:

The Event Policy for the process started at 10:44:13 PM has detected errors in the output. The 'StdErr' policy expression:
.+
matched the following output:
Account OpsMgr SharePoint Action Account doesn't exist
Failed to find RunAs account OpsMgr SharePoint Action Account
Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo -NoProfile
-Noninteractive "$ep = get-executionpolicy; if ($ep -gt 'RemoteSigned') {set-executionpolicy
remotesigned} & '"C:\Program Files\System Center Operations Manager 2007\Health Service State\
Monitoring Host Temporary Files 32\9687\AdminTask.ps1"' 'SharePointMP.Config'"
Working Directory: C:\Program Files\System Center Management Packs\
One or more workflows were affected by this.
Workflow name: Microsoft.SharePoint.Foundation.2010.ConfigSharePoint
Instance name: Microsoft SharePoint 2010 Farm Group
Instance ID: {B7E9A5AF-62D1-CF79-0AE8-044AE7CECBD7}
Management group: XXX
Error Code: -2130771918 (Unknown error (0x80ff0032))

Machines that do not have SharePoint Foundation 2010 or SharePoint Server 2010 installed are discovered as SharePoint 2010 Servers.

Resolution - Configure the Run As Account association, configure the Machine Name association and configure the "More Secure Option".

Configure the "More Secure Option"

The More Secure option will deliver the configured credentials only to the machines specified in this section. The credentials sent will be for the purpose of discovering and monitoring the SharePoint farms specified. The machines in this list should be the same machines specified in the SharePointMP.config file. The requirement is to have all distributed application component listed for a specific farm. This would include front end server and SQL servers that host the SharePoint database.

To configure the More Secure Option do the following:

Option 1 - Create the Run As Account and configure

Open the Operations Manager Console.

Go to the Administration tab.

Expand the Security node.

Right-click Run As Accounts.

Select Create Run As Account and Click Next.

Set the Run As Account Type as "Windows", give it a Display Name and Click Next.

Enter in the Credentials for the Active Directory Domain User Account and Click Next.

Select "More Secure" option and add all of the servers that are part of the SharePoint farm. This will include all SharePoint Frontend, Application and SQL Servers for that SharePoint farm.

Click Create.

Option 2 - Configure an already existing account

Open the Operations Manager Console and navigate to the Administration Tab.

Expand the Run As Configuration node and highlight Accounts.

In the middle panel open an existing Run As Account from the middle pane under Type: Windows

right click the account and choose properties.

Click on the Distribution Tab.

Select "More Secure" option and add all of the servers that are part of the SharePoint farm. This will include all SharePoint Frontend, Application and SQL Servers for that SharePoint farm.

Click OK.

NOTE Distribution of Security ensures that all the servers that are part of the SharePoint Farm are selected and included here. We recommend having one set of Operations Manager servers monitor only one SharePoint farm. We do not recommend having multi-homed agent computer (SharePoint servers that are monitored in multiple Operations Manager management groups).

Configuring the Run As Account Association

The Run As Account needs to be associated within the SharePoint Management Pack config file. If not configured correctly you will not be able to discover the SharePoint Servers.

To configure the SharePointMP.config file:

Navigate to <drive>:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us

NOTE For 64-bit version of Windows Server 2008 or Windows Server 2008 R2 copy the SharePointMP.config file to the %Program Files\System Center Management Packs from the %ProgramFiles(x86)%\System Center Management Packs directory

Right click the SharePointMP.config file and choose edit

Locate the section as shown below

Example:

<Association Account="SharePoint Discovery/Monitoring Account" Type="Agent">

Change this section to reflect the “Display Name” of the Run Account you have previously configured as the Run As Account for the SharePoint farm.

Now this section should look like this

<Association Account="SPAdmin" Type="Agent">

or

<Association Account="Domain\SPAdmin" Type="Agent">

NOTE Do not confuse this with the actual active directory domain user account.

Configuration of Machine Names

Configure the machine name of all the servers that are part of the SharePoint Farm and match the "More Secure" section of the Run As Account used for the SharePoint 2010 farm.

NOTE To confirm this name run a hostname command from a command prompt on the servers either locally or remotely for each computer that is part of the farm.

To configure the SharePointMP.config file:

Navigate to <drive>:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us

NOTE For 64-bit version of Windows Server 2008 or Windows Server 2008 R2 copy the SharePointMp.config file to the %Program Files\System Center Management Packs from the %ProgramFiles(x86)%\System Center Management Packs directory.

NOTE For a clustered root management servers the same procedure must be performed on both nodes of the cluster.

Right click the SharePointMP.config file and choose edit.

Find the section as shown below

Example:

<Machine Name="" />

<Machine Name="" />

</Association>

Change this section to include the SharePoint Server names for example:

<Machine Name="SRV1" />

<Machine Name="SRV2" />

</Association>

Confirm the Run As Account has been configured

To confirm the Run As Account has been configured:

Open the Operations Manager event log.

Look for event ID 7026 - open this event - this should indicate that the run as account for the SharePoint MP has successfully logged on.

NOTE: An event ID 7000 in the Operations Manager event log indicates that the run as account for the SharePoint MP has failed to log on.

Log Name: Operations Manager

Source: HealthService

Date:

Event ID: 7000

Task Category: Health Service

Level: Error

Keywords: Classic

User: N/A

Computer:

Description:

The Health Service could not log on the RunAs account contoso\spadmin for management group <MGName>. The error is Logon failure: unknown user name or bad password.(1326L). This will prevent the health service from monitoring or performing actions using this RunAs account

Additionally you may also see the following events

Log Name: Operations Manager

Source: HealthService

Date:

Event ID: 7021

Task Category: Health Service

Level: Error

Keywords: Classic

User: N/A

Computer:

Description:

The Health Service was unable to validate any user accounts in management group <MGName>.

Log Name: Operations Manager

Source: HealthService

Date:

Event ID: 7015

Task Category: Health Service

Level: Error

Keywords: Classic

User: N/A

Computer:

Description:

The Health Service cannot verify the future validity of the RunAs account contoso\spadmin for management group <MGName>. The error is Logon failure: unknown user name or bad password.(1326L).

Scenario 3 - Unable to monitor multiple farms in local domain or remote domains

Symptom:

Only one server farm is discovered as seen from the Monitoring -> SharePoint 2010 Products -> Farms state view. Servers for other farms show up in the Monitoring -> SharePoint 2010 Products -> Unidentified Machines state view

Resolution: Configure the SharePointMP.config to discover more than one servers farm

Required Permissions

The required permissions for each individual SharePoint farm run as account are:

Local admin on all SharePoint Front End and Application servers

Local admin on all SQL boxes that host SharePoint 2010 Databases

Full Farm Administrator rights within SharePoint 2010

DBO for all SharePoint databases

NOTE The initial installation account for SharePoint 2010 Foundation and SharePoint 2010 Server already has the necessary permissions required in all databases created during initial installation. It is recommended that you use this installation account to configure the SharePoint Foundation 2010 and SharePoint Server 2010 Management Packs. If requirements for security call for the creation of a new account for the management pack administration and discovery, take into account that you will have to duplicate the same permissions already granted to the SharePoint installation account.

For a clustered installation of the root management server the SharePointMP.config file must exist in the same directory as described above in each individual node of the cluster.

Configure the "More Secure Option"

The More Secure option will deliver the configured credentials only to the machines specified in this section.

The credentials sent will be for the purpose of discovering and monitoring the SharePoint farms specified. The machines in this list should be the same machines specified in the SharePointMP.config file. The requirement is to have all distributed application component listed for a specific farm. This would include front end server and SQL servers that host the SharePoint database.

To configure the More Secure Option do the following:

Option 1 - Create the Run As Account and configure

Open the Operations Manager Console.

Go to the Administration tab.

Expand the Security node.

Right-click Run As Accounts.

Select Create Run As Account and Click Next.

Set the Run As Account Type as "Windows", give it a Display Name and Click Next.

Enter in the Credentials for the Active Directory Domain User Account and Click Next.

Select "More Secure" option and add all of the servers that are part of the SharePoint farm. This will include all SharePoint Frontend, Application and SQL Servers for that SharePoint farm.

Click Create.

Option 2 - Configure an already existing account

Open the Operations Manager Console and navigate to the Administration Tab.

Expand the Run As Configuration node and highlight Accounts.

In the middle panel open an existing Run As Account from the middle pane under Type: Windows

right click the account and choose properties.

Click on the Distribution Tab.

Select "More Secure" option and add all of the servers that are part of the SharePoint farm. This will include all SharePoint Frontend, Application and SQL Servers for that SharePoint farm.

Click OK.

NOTE Distribution of Security ensures that all the servers that are part of the SP Farm are selected and included here. We recommend having one set of Operations Manager servers monitor only one SharePoint farm. We do not recommend having multi-homed agent computer (SharePoint servers that are monitored in multiple Operations Manager management groups).

Example Scenario: You have 3 farms residing in 2 different domains.

Contoso - SharePoint Farm Administrator 1 is associated with the farm administrator account for the first SharePoint farm in contoso.com domain and uses the Domain Account SPADMIN1

Contoso - SharePoint Farm Administrator 2 is associated with the farm administrator account for the second SharePoint farm in contoso.com domain and uses the Domain Account SPADMIN2

Fabrikam - SharePoint 2010 Farm Administrator is associated with the farm administrator account for the third SharePoint farm in fabrikam.com domain and uses the Domain Account FKSPADMIN

NOTE For the remote domain Fabrikam.com it is assumed that you have a reliable link using an Operations Management Gateway Server or a two way full trust for the domains.

Using the display name of the Run As Account in the Administration -> Run As Configuration -> Accounts -> Type: Windows

To configure the SharePointMP.config file:

Navigate to the:

Drive:\Program Files (x86)\System Center Management Packs\Microsoft SharePoint 2010 Products OpsMgr 2007 MP en-us

NOTE For 64-bit version of Windows Server 2008 or Windows Server 2008 R2 copy the SharePointMP.config file to the %Program Files\System Center Management Packs from the %ProgramFiles(x86)%\System Center Management Packs directory

NOTE For a clustered installation of the root management server the SharePointMP.config must exist in the same directory as described above in each individual node of the cluster.

Right click the SharePointMP.config file and choose edit.

Find the "Association" and "Machine Name" section in the SharePointMP.config file as shown in the example below
</Annotation>
<Association Account="SharePoint Discovery/Monitoring Account" Type="Agent">
<Machine Name="" />
</Association>

Change the "Association" and "Machine Name" section to read as followed in this example:

Confirm the Run As Account has been configured

To confirm the Run As Account has been configured:

Open the Operations Manager event log.

Look for event ID 7026 - open this event - this should indicate that the run as account for the SharePoint MP has successfully logged on.

NOTE An event ID 7000 in the Operations Manager event log indicates that the run as account for the SharePoint MP has failed to log on.

Log Name: Operations Manager

Source: HealthService

Date:

Event ID: 7000

Task Category: Health Service

Level: Error

Keywords: Classic

User: N/A

Computer: SRV1.contoso.com

Description:

The Health Service could not log on the RunAs account contoso\spadmin for management group <MGNAME>. The error is Logon failure: unknown user name or bad password.(1326L). This will prevent the health service from monitoring or performing actions using this RunAs account

Additionally you may also see the following events

Log Name: Operations Manager

Source: HealthService

Date:

Event ID: 7021

Task Category: Health Service

Level: Error

Keywords: Classic

User: N/A

Computer: SRV1.contoso.com

Description:

The Health Service was unable to validate any user accounts in management group <MGNAME>.

Log Name: Operations Manager

Source: HealthService

Date:

Event ID: 7015

Task Category: Health Service

Level: Error

Keywords: Classic

User: N/A

Computer: SP2010SRV1.contoso.com

Description:

The Health Service cannot verify the future validity of the RunAs account contoso\spadmin for management group <MGNAME>. The error is Logon failure: unknown user name or bad password.(1326L).

Scenario 4- How to Run the Configuration Task

Symptom: Unable to run configuration task the following error(s) are generated

Example 1

Exception calling ".ctor" with "1" argument(s): "The user Contoso\SPAdmin does not have sufficient permission to perform the operation."
Failed to connect to local management group
Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo -NoProfile -Noninteractive "$ep = get-executionpolicy; if
($ep -gt 'RemoteSigned') {set-executionpolicy remotesigned} & '"C:\Program Files\System Center Operations Manager 2007\Health Service
State\Monitoring Host Temporary Files 49\5037\AdminTask.ps1"' 'SharePointMP.Config'"
Working Directory: C:\Program Files\System Center Management Packs\
One or more workflows were affected by this.
Workflow name: Microsoft.SharePoint.Foundation.2010.ConfigSharePoint
Instance name: Microsoft SharePoint 2010 Farm Group
Instance ID: {B7E9A5AF-62D1-CF79-0AE8-044AE7CECBD7}
Management group: XXX
Error Code: -2130771918 (Unknown error (0x80ff0032)).

Example 2

The Event Policy for the process started at 10:44:13 PM has detected errors in the output. The 'StdErr' policy expression:
.+
matched the following output:
Account OpsMgr SharePoint Action Account doesn't exist
Failed to find RunAs account OpsMgr SharePoint Action Account
Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo -NoProfile -Noninteractive "$ep = get-executionpolicy; if
($ep -gt 'RemoteSigned') {set-executionpolicy remotesigned} & '"C:\Program Files\System Center Operations Manager 2007\Health Service
State\Monitoring Host Temporary Files 32\9687\AdminTask.ps1"' 'SharePointMP.Config'"
Working Directory: C:\Program Files\System Center Management Packs\
One or more workflows were affected by this.
Workflow name: Microsoft.SharePoint.Foundation.2010.ConfigSharePoint
Instance name: Microsoft SharePoint 2010 Farm Group
Instance ID: {B7E9A5AF-62D1-CF79-0AE8-044AE7CECBD7}
Management group: XXX
Error Code: -2130771918 (Unknown error (0x80ff0032)).

Resolution: Add the Run As Account Operations Manager Administrator Role

To add the Run As Account being used to execute the task

Open the Operations Console.

Navigate to Administration.

Click on Security.

Click on User Roles.

Click on Operations Manager Administrators.

Add the account running the task as part of the Operations Manager Administrators role.

NOTE For 64-bit version of Windows Server 2008 or Windows Server 2008 R2 copy the SharePointMP.config file to the %Program Files\System Center Management Packs from the %ProgramFiles(x86)%\System Center Management Packs directory

NOTE For a clustered installation of the root management server the SharePointMP.config must exist in the same directory as described above in each individual node of the cluster.

Configure SharePoint Management Pack Task

The admin task configures the management pack by ensuring the existence of an override management pack, associating 'RunAs' account(s) to servers, enabling proxy settings, and initiating discoveries.

To run the "Configure SharePoint Management Pack" task do the following

Open the Operations Manager Console.

Click on the Monitoring tab of the console.

Expand the SharePoint 2010 Products view.

Click on the Administration state view.

On the Actions Pane, under Microsoft SharePoint 2010 Farm Group Tasks, click on the Configure SharePoint Management Pack.

Select the appropriate task credentials (preferably the SharePoint Admin Run As Account you have previously setup)

Click Run and wait for the task to finish successfully.

Click Close

Example of successful task

Configure SharePoint Management Pack Task Description

This admin task configures the management pack by ensuring the existence of an override management pack, associating 'RunAs' account(s) to servers, enabling proxy settings, and initiating discoveries.

Status:Success

Scheduled Time:

Start Time:

Submitted By:CONTOSO\SPADMIN

Run As:

Run Location:

Target:

Target Type:Microsoft SharePoint 2010 Farm Group

Category:Operations

Task Output:

Output

Load configuration file SharePointMP.Config

Configure Microsoft.SharePoint.Foundation.2010 version 14.0.4744.1000

Found override management pack Microsoft.SharePoint.Foundation.2010.Override version 1.0.0.0

Change 'SyncTime' configuration override to 20:06 for Microsoft.SharePoint.Foundation.2010.WSSInstallation.Discovery

Microsoft.SharePoint.Foundation.2010.WSSInstallation.Discovery does not have configuration TimeoutSeconds

Change 'SyncTime' configuration override to 20:08 for Microsoft.SharePoint.Foundation.2010.SPFarm.Discovery

Change 'SyncTime' configuration override to 20:14 for Microsoft.SharePoint.Foundation.2010.SPService.Discovery

Change 'SyncTime' configuration override to 20:20 for Microsoft.SharePoint.Foundation.2010.SPSharedService.Discovery

Change 'SyncTime' configuration override to 20:26 for Microsoft.SharePoint.Foundation.2010.SPHARule.Discovery

Change 'SyncTime' configuration override to 20:32 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.Availability

Change 'SyncTime' configuration override to 20:32 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.Security

Change 'SyncTime' configuration override to 20:32 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.Performance

Change 'SyncTime' configuration override to 20:32 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.Configuration

Change 'SyncTime' configuration override to 20:32 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.Custom

Change 'SyncTime' configuration override to 20:38 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.SPServer.Availability

Change 'SyncTime' configuration override to 20:38 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.SPServer.Security

Change 'SyncTime' configuration override to 20:38 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.SPServer.Performance

Change 'SyncTime' configuration override to 20:38 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.SPServer.Configuration

Change 'SyncTime' configuration override to 20:38 for Microsoft.SharePoint.Foundation.2010.SPHARuleMonitor.SPServer.Custom

SharePoint management pack configuration completed successfully

Error

None

Exit Code: 0

Scenario 5 - Unable to run the "Configure SharePoint Management Pack" task in System Center Operations Manager 2012

Symptom: The following error message is generated

The Event Policy for the process started at 6:51:29 PM has detected errors in the output. The 'StdErr' policy expression:
.+
matched the following output:
Exception calling "ImportManagementPack" with "1" argument(s): "This method from the System Center Operations Manager 2007
R2 SDK is not supported to work with System Center Operations Manager 2012. Please migrate to the System Center Operations Manager 2012 SDK."
Failed to create override management pack Microsoft.SharePoint.Foundation.2010.Override
Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo -NoProfile -Noninteractive "$ep = get-executionpolicy;
if ($ep -gt 'RemoteSigned') {set-executionpolicy remotesigned} & '"E:\Program Files\System Center 2012\Operations Manager\Server\Health Service
State\Monitoring Host Temporary Files 11\7481\AdminTask.ps1"' 'SharePointMP.Config'"
Working Directory: C:\Program Files\System Center Management Packs\
One or more workflows were affected by this.
Workflow name: Microsoft.SharePoint.Foundation.2010.ConfigSharePoint
Instance name: Microsoft SharePoint 2010 Farm Group
Instance ID: {B7E9A5AF-62D1-CF79-0AE8-044AE7CECBD7}
Management group: XXX
Error Code: -2130771918 (Unknown error (0x80ff0032)).

Resolution: Call Microsoft Support to provide an updated version of the management pack compatible with the System Center Operations Manager 2012 SDK

Scenario 6 - Unable to monitor SharePoint 2010 Databases

Symptom:

Critical alerts are generated in the active alerts view under Monitoring -> SharePoint 2010 Products -> Active Alerts

SharePoint: Database Connection Failed Alert Description

Source: Configuration Database A critical incident has occurred where the connection to database Data Source=sp2010srv2;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Connect Timeout=15 failed.

Path: Configuration Database

Alert Monitor: SQL Database Connection Failed

Created:

Alert Context:

Date and Time

HRESULT -2147217805

Result Data Source could not be initialized

Error Message Format of the initialization string does not conform to the OLE DB specification.

Initialization Time 23

Open Time 0

Execution Time 0

Fetch Time 0

Result Set Input Data Item

The SQL Database Connection Failed monitors are showing critical under the following views

Monitoring -> SharePoint 2010 Products ->

Configuration Databases

Content Databases

Shared Services

Diagram View

Resolution: Create a new override for the connection string value on the SQL Database Connection Failed monitors

To create the Override needed do the following:

1. From the Monitoring -> SharePoint 2010 Products ->Active Alerts view select an affected monitor

2. Under the Alert Details (bottom pane) take notice of the Alert Description. It should look like this

Example:

Alert Description

A critical incident has occurred where the connection to database Data Source=sp2010srv2;Initial Catalog=SharePoint_Config;Integrated Security=True;Enlist=False;Connect Timeout=15 failed

3. Copy and Paste the text to a text editor such as notepad.exe

4. Right Click on the monitor once again and select View or edit the settings of this monitor

5. In the SQL database Connection Failed Properties windows select the overrides tab and click on the override button

6. Select the option "For a specific object of class: XXX"

Example:

For a specific object of class: SharePoint Configuration Database

7. In the Select Object under matching objects select the appropriate matching object and click OK

Example:

Configuration Database

8. Override ConnectionString parameter value from

Example:

Provider=SQLOLEDB;$Target/Property[Type="Microsoft.SharePoint.Foundation.2010.SPDatabase"]/ConnectionString$

To

Provider=SQLOLEDB;Data Source=SP2010srv2;Initial Catalog=SharePoint_Config;Integrated Security=SSPI;Enlist=False;Connect Timeout=15

9. Create an new override management pack or save to an existing override management pack other than the and save the changes by clicking OK

NOTE Since each individual database needs its own unique database string that corresponds to its database name (Initial Catalog), you will need to modify the previously copied connection string the alert description of the monitor and change Integrated Security from True

Examples:

Data Source=sp2010srv2;Initial Catalog=SharePoint_Config;Integrated Security=SSPI;Enlist=False;Connect Timeout=15

Data Source=sp2010srv2;Initial Catalog=SharePoint_AdminContent_0ada3e0b-a0f6-4af5-a311-34bcedb1c4eb;Integrated Security=True;Enlist=False;Connect Timeout=15

Data Source=sp2010srv2;Initial Catalog=WSS_Content;Integrated Security=SSPI;Enlist=False;Connect Timeout=15

Data Source=sp2010srv2;Initial Catalog=Bdc_Service_DB_17ab85413d424b84ac58ea247e7f5b47;Integrated Security=SSPI;Enlist=False;Connect Timeout=15

Data Source=sp2010srv2;Initial Catalog=Search_Service_Application_CrawlStoreDB_04e2a4bcdb974275954c0ab090d8a0aa;Integrated Security=SSPI;Enlist=False;Connect Timeout=15

User Education - Sync Time Overrides

We recommend using the defaults values in place for sync time. If the default values are not deemed appropriate for our environment take special considerations on the performance impact this may cause by changing these values.

SyncTime overrides are particularly useful during failed discovery troubleshooting. By overriding the default values you can configure the start time of different workflows and isolate discovery problems.

SyncTime (start time) is a property of discoveries and monitors. SyncTime is a string value in the format of "HH:mm". SyncTime, IntervalSeconds and Management Pack Import time together determine the exact run time of a given workflow.

The BaseStartTime attribute can have value in the form of "HH:mm" or integer. "HH:mm" format works as the start time alignment based on which

the cycle repeats. Integer format functions as setting the alignment start time to be the current time plus that many seconds. Be aware that

if you set integer value, every time you rerun the admin task, the cycle start time is recalculated.

The Length attribute specifies the length (in seconds) of each cycle.

The Spacing attribute specifies the spacing time (in seconds) between one workflow's timeout time and the next workflow's start time.

For example, if IntervalSeconds = 21600 (6 hours) and SyncTime = "01:15", the possible run time of the workflow is 1:15AM, 7:15AM, 1:15PM, 7:15PM; if the Management Pack is imported after 1:15AM but before 7:15AM, it will start at 7:15AM, if the Management Pack is imported after 1:15PM but before 7:15PM, it will start at 7:15PM. However, due to other factors such as network delay the actual start time may still vary. Do not change the default SyncTime value unless absolutely required.

So in case you imported the MP at 03:00 PM and the Interval seconds is set to every 8 hrs.=(28,800 seconds) and you configured the sync time to be “03:00” then it will sync at 11:00 PM or 8 hours after the sync time was setup when you imported the MP.

Possible error messages when not configuring this properly are shown below

Example 1

The Event Policy for the process started at 6:46:08 PM has detected errors in the output. The 'StdErr' policy expression:
.+
matched the following output:
Cycle length 60 is not long enough to ensure the order of workflows
Please change cycle length to no less than 360 or decrease times, timeout values, and/or spacing
Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo -NoProfile -Noninteractive "$ep = get-executionpolicy; if
($ep -gt 'RemoteSigned') {set-executionpolicy remotesigned} & '"C:\Program Files\System Center Operations Manager 2007\Health Service
State\Monitoring Host Temporary Files 22\9315\AdminTask.ps1"' 'SharePointMP.Config'"
Working Directory: C:\Program Files\System Center Management Packs\
One or more workflows were affected by this.
Workflow name: Microsoft.SharePoint.Foundation.2010.ConfigSharePoint
Instance name: Microsoft SharePoint 2010 Farm Group
Instance ID: {B7E9A5AF-62D1-CF79-0AE8-044AE7CECBD7}
Management group: XXX
Error Code: -2130771918 (Unknown error (0x80ff0032)).
Example 2

The Event Policy for the process started at 6:42:01 PM has detected errors in the output. The 'StdErr' policy expression:
.+
matched the following output:
Cycle length must be in whole minutes (times of 60)
Length value 500 is undefined or invalid
Command executed: "C:\Windows\system32\cmd.exe" /c powershell.exe -NoLogo -NoProfile -Noninteractive "$ep = get-executionpolicy; if
($ep -gt 'RemoteSigned') {set-executionpolicy remotesigned} & '"C:\Program Files\System Center Operations Manager 2007\Health Service
State\Monitoring Host Temporary Files 21\9314\AdminTask.ps1"' 'SharePointMP.Config'"
Working Directory: C:\Program Files\System Center Management Packs\
One or more workflows were affected by this.
Workflow name: Microsoft.SharePoint.Foundation.2010.ConfigSharePoint
Instance name: Microsoft SharePoint 2010 Farm Group
Instance ID: {B7E9A5AF-62D1-CF79-0AE8-044AE7CECBD7}
Management group: XXX
Error Code: -2130771918 (Unknown error (0x80ff0032)).

User Education - Isolating Discoveries

The following example sets the run time of the discovery to run 5 minutes after running the configuration task for a single workflow that has been failing.

</Annotation>

<WorkflowCycle BaseStartTime="+5" Length="6240" Spacing="15">

<Workflow Id="SPFarm.Discovery" Type="Discovery" Times="1" />

If starting this procedure at 7:35 PM then configure the override as followed when viewed from the Authoring->Management Pack Objects -> Overrides view in the console to start at 7:40 PM

SyncTime Override Value = 19:40

Interval Seconds = 6240

Enable Debug Tracing

Enabling Debug Tracing will enable debug trace on those agent computers that run Windows PowerShell script based discoveries and SPHA monitors. By default it is turned off. When it is enabled, the script based discoveries and monitors will write debug trace information to Event Log in Operations Manager channel on all agent computers, and all the debug trace events have an event ID of 0.

To enable debug tracing do the following:

In the Operations Console Select Monitoring.

Select SharePoint 2010 Products.

Select Administration view.

On the Actions panel, click the task named “Set DebugTrace for SharePoint Management Pack”. A Run Task window will popup.

To enable debug trace (the default option), click Run. To disable debug trace, click Override.

Set the Enabled parameter value to “False” in the popup dialog.

Click Override to close the dialog.

Click Run.

Wait for the task to finish in Task Status window, and then check the Task Output to ensure that the task completes successfully.

Click Close.

How to use debug tracing

Run the “Set DebugTrace For SharePoint Management Pack” task then rerun the Admin Task, and then go to Operations Manager Event channel on the server and check events with ID = 0. Look for the timestamp in the event log and then check the SharePoint ULS trace log to ensure that it is the case

For more information about the ULS trace log, see the SharePoint Foundation 2010 documentation on TechNet ( http://technet.microsoft.com/en-us/sharepoint/ee263910.aspx ).

For Advanced Users:

For further troubleshooting of failed discoveries you can use the Operations Manager 2007 R2 Workflow Analyzer which is part of the Operations Manager 2007 R2 MP Authoring Resource Kit http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=18222as

As well as use enabling diagnostic tracing in System Center Operations Manager 2007 http://support.microsoft.com/kb/942864

User Education - Adding Workflows to SharePoint Config file

If you want to add workflows to discover both SharePoint Foundation 2010 and SharePoint 2010 Products

Default <WorkflowCycle BaseStartTime="+300" Length="28800" Spacing="60">

<Workflow Id="WSSInstallation.Discovery" Type="Discovery" Times="1" />

<Workflow Id="SPFarm.Discovery" Type="Discovery" Times="1" />

<Workflow Id="SPService.Discovery" Type="Discovery" Times="4" />

<Workflow Id="SPSharedService.Discovery" Type="Discovery" Times="4" />

<Workflow Id="SPHARule.Discovery" Type="Discovery" Times="1" />

<Workflow Id="SPHARuleMonitor.Availability;SPHARuleMonitor.Security;SPHARuleMonitor.Performance;SPHARuleMonitor.Configuration;SPHARuleMonitor.Custom" Type="Monitor" Times="8" />

<Workflow Id="SPHARuleMonitor.SPServer.Availability;SPHARuleMonitor.SPServer.Security;SPHARuleMonitor.SPServer.Performance;SPHARuleMonitor.

SPServer.Configuration;SPHARuleMonitor.SPServer.Custom" Type="Monitor" Times="8" />

</WorkflowCycle>

Add the following section to the SharePointMp.config file

<Workflow Id="MOSSInstallation.Discovery;WACInstallation.Discovery;SearchExpressInstallation.Discovery;SearchStandardInstallation.Discovery" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="1" />

<Workflow Id="SPService.Discovery" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="4" />

<Workflow Id="SPSharedService.Discovery" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="4" />

<Workflow Id="SPSharedService.Discovery.WAC" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="4" />

The configuration file should now look like this

<WorkflowCycle BaseStartTime="+300" Length="28800" Spacing="60">

<Workflow Id="WSSInstallation.Discovery" Type="Discovery" Times="1" />

<Workflow Id="MOSSInstallation.Discovery;WACInstallation.Discovery;SearchExpressInstallation.Discovery;SearchStandardInstallation.Discovery" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="1" />

<Workflow Id="SPFarm.Discovery" Type="Discovery" Times="1" />

<Workflow Id="SPService.Discovery" Type="Discovery" Times="4" />

<Workflow Id="SPSharedService.Discovery" Type="Discovery" Times="4" />

<Workflow Id="SPService.Discovery" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="4" />

<Workflow Id="SPSharedService.Discovery" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="4" />

<Workflow Id="SPSharedService.Discovery.WAC" management pack="Microsoft.SharePoint.Server.2010" Type="Discovery" Times="4" />

<Workflow Id="SPHARule.Discovery" Type="Discovery" Times="1" />

<Workflow Id="SPHARuleMonitor.Availability;SPHARuleMonitor.Security;SPHARuleMonitor.Performance;SPHARuleMonitor.Configuration;SPHARuleMonitor.Custom" Type="Monitor" Times="8" />

<Workflow Id="SPHARuleMonitor.SPServer.Availability;SPHARuleMonitor.SPServer.Security;SPHARuleMonitor.SPServer.Performance;SPHARuleMonitor.SPServer.Configuration;SPHARuleMonitor.SPServer.Custom" Type="Monitor" Times="8" />

</WorkflowCycle>

=====

For the most current version of this article please see the following:

2690744 : Configuring the SharePoint 2010 Management Pack for System Center Operations Manager ...

J.C. Hornbeck | System Center & Security Knowledge Engineer

Get the latest System Center news on Facebook and Twitter :

The Forefront Server Protection blog: http://blogs.technet.com/b/fss/

The Forefront Endpoint Security blog : http://blogs.technet.com/b/clientsecurity/

The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/

The Forefront TMG blog: http://blogs.technet.com/b/isablog/

The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/

Products (52)

Special Topics (28)

Video Hub (447)

Most Active Hubs

Most Active Hubs

Video Hub

KB: Configuring the SharePoint 2010 Management Pack for System Center Operations Manager