Register source systems to the System Center data warehouse in Service Manager
The data warehouse in Service Manager retrieves data from one or more data sources. These data sources are the transactional processing systems that produce and govern data that you will eventually want to measure and analyze. For example, incidents and change requests are created and managed in Service Manager, software updates and power policies are managed in Configuration Manager, and other systems produce and govern other data sets.
Registering the data warehouse creates a relationship between the data warehouse server and the source system so that information can flow between them. In Service Manager, you can register to Service Manager, Operations Manager, and Configuration Manager directly. You can also use the updated software development kit (SDK) layer on top of the data warehouse, which enables you to push data into the data warehouse directly from other sources. For example, you might want to push data from your Human Resources computer system into the data warehouse.
Register the System Center data warehouse to Operations Manager
You can use the following procedures in Service Manager to register the System Center Data Warehouse to Operations Manager and then validate the registration.
To register the data warehouse to Operations Manager, follow these steps:
Register System Center Data Warehouse to Service Manager Source.
Wait for the MPSync job to complete.
Using an account that is a member of the Service Manager and data warehouse management administrators group, sign in to the computer that hosts the Service Manager console.
In the Service Manager console, select Data Warehouse.
In the Administration pane, expand Data Warehouse, and then select Data Sources.
In the Tasks list, select Register data source.
In the Register Data Source Wizard, on the Before You Begin page, select Next.
On the Data Source Type page, select Operations Manager.
Under Specify a Root Management Server area, enter the following information:
For Root Management server name, enter the server name.
For Operational database server, enter the database server name.
For Database name, enter the name of the database.
Select Next.
On the Credentials page, you can accept the default entry in the Run as account list, and select Next, or you can enter credentials from a user or group of your choice.
Important
The account that you specify will be assigned administrative credentials on the Service Manager management server and granted Read permission on the Service Manager database. You can specify different credentials from other Service Manager management groups when you're registering with the data warehouse.
On the Summary page, you can review the settings that you've chosen. Select Finish.
On the Result page, when Data source registration complete. appears, select Finish.
Validate the Operations Manager registration process
- In the Data Sources view, the new data source appears in the list of data sources, with the data source type of Operations Manager. You might have to refresh your view to see the new data source.
Register the System Center data warehouse to Configuration Manager
You can use the following steps in Service Manager to register Configuration Manager with the System Center Data Warehouse and then validate the registration.
To register Configuration Manager with the data warehouse, follow these steps:
By using an account that is a member of the Service Manager and data warehouse management administrators group, sign in to the computer that hosts the Service Manager console.
In the Service Manager console, select Data Warehouse.
In the Administration pane, expand Data Warehouse, and then select Data Sources.
In the Tasks list, select Register data source.
In the Register Data Source Wizard, on the Before You Begin page, select Next.
On the Data Source Type page, select Configuration Manager.
Under Specify a Central Site Server, enter the following information:
For Central Site server name, enter the site server name.
For Database name, enter the name of the database.
Select Next.
On the Credentials page, you can accept the default entry in the Run as account list, and select Next, or you can enter credentials from a user or group of your choice.
Important
The account that you specify will be assigned administrative credentials on the Service Manager management server and granted Read permission on the Service Manager database. You can specify different credentials from other Service Manager management groups when you're registering with the data warehouse.
On the Data Selection page, choose the domains to extract, and select Next. For example, select System Center Configuration Manager Connector Configuration and System Center Configuration Manager Power Management Connector.
On the Summary page, you can review the settings that you've chosen. Select Finish.
On the Result page, when Data source registration complete appears, select Finish.
Validate the Configuration Manager registration process
- In the Data Sources view, the new data source appears in the list of data sources, with the data source type of Configuration Manager. You might have to refresh your view to see the new data source.
Register the System Center data warehouse to a Service Manager source
You can use the following procedures in Service Manager to register the System Center Data Warehouse with a Service Manager management group and then validate the registration. This makes it possible to host multiple Service Manager management groups in a single data warehouse.
Register the data warehouse with another Service Manager management group
By using an account that is a member of the Service Manager and data warehouse management administrators group, sign in to the computer that hosts the Service Manager console.
In the Service Manager console, select Data Warehouse.
In the Administration pane, expand Data Warehouse, and then select Data Sources.
In the Tasks list, select Register data source.
In the Register Data Source Wizard, on the Before You Begin page, select Next.
On the Data Source Type page, select Service Manager.
Under Specify a Service Manager Server, enter the following information:
- For Service Manager server name, enter the server name.
Select Next.
On the Credentials page, you can accept the default entry in the Run as account list, and select Next, or you can enter credentials from a user or group of your choice.
Important
The account that you specify will be assigned administrative credentials on the Service Manager management server and granted Read permission on the Service Manager database. You can specify different credentials from other Service Manager management groups when registering with the data warehouse.
On the Summary page, you can review the settings that you've chosen. Select Finish.
On the Result page, when Data source registration complete. appears, select Finish.
Validate the Service Manager registration process
- In the Data Sources view, the new data source appears in the list of data sources, with the data source type of Service Manager. You might have to refresh your view to see the new data source.
Manage data import jobs for Operations Manager and Configuration Manager
You can use the following procedure to manage data warehouse data import jobs in Service Manager. Data import jobs are like other data warehouse jobs, and you can manage them with the Service Manager console and also with Windows PowerShell cmdlets. Methods of management include:
Revising the processing schedule to hourly, daily, or weekly
Suspending a job
Resuming a suspended, or Not Started, job
Manage data import jobs and change a job schedule
In the Service Manager console, select Data Warehouse, expand Data Warehouse, and select Data Warehouse Jobs.
In the Data Warehouse Jobs pane, select a job name, and then under Tasks, select Properties.
In the job properties dialog that appears, you can view the current schedule. You can change the schedule to one of your choice. For example, change the schedule to Daily and run the job at 1:00 AM, and select OK.
You can optionally Suspend jobs, and you can Resume any that are suspended or Not Started.
Troubleshoot System Center data warehouse errors
This section describes steps you can take to troubleshoot System Center data warehouse errors in Service Manager.
Use the Operations Manager event log on the Data Warehouse server to troubleshoot errors
Service Manager event logs are found in the Operations Manager event log. Evaluating events in the log is useful because most errors from the data warehouse are found in this event log. Events in the log are from two different sources: Deployment and Data Warehouse.
Events with a source of Deployment are generated during management pack deployment, which includes report deployment or assembling the data warehouse; for example, by creating outriggers, dimensions, and fact tables. Errors in the event log include instructions about how to recover from the errors. For example, you might read instructions suggesting that you stop and then restart the Service Manager services. The three services on a data warehouse management server are:
System Center Data Access Service
Microsoft Monitoring Agent
System Center Management Configuration
When you start and stop Service Manager services, you must stop and start all three services.
After the data warehouse is deployed, events are more likely to have a source of Data Warehouse. These events are created by jobs within the normal course of operations like extract, transform, and load (ETL) jobs; the MPSync job; and the DWMaintenance job.
Use the Service Manager console to troubleshoot errors
In the Service Manager console, select Data Warehouse Jobs and you will see ETL job and MPSync job status. If your deployment was successful and your data warehouse is correctly registered to at least one Service Manager management group, you see at least five jobs. Every job should have the status Running or Not Started.
If you see a job status listed as Failed, you can select the job, and then in the Tasks pane, select Modules to find out which job module has failed. Then, you can examine the Operations Manager event log on the data warehouse server to determine why the module failed.
In the Data Warehouse workspace, you can select Management Packs in the left pane. That is where you can view all the management packs in the data warehouse and the status of their deployment. When you import a management pack to Service Manager, the MPSync job synchronizes it to the data warehouse, where the MPSync job derives its name from management pack synchronization. When you get the list of management packs in the data warehouse, you can find out if your management pack has been deployed successfully or not.
If your management pack has defined data warehouse-specific elements, such as outriggers, dimensions, fact tables, or reports, that management pack must be successfully deployed before the new tables and reports will be ready to use.
Use Windows PowerShell to troubleshoot errors
The Windows PowerShell cmdlets in the following table provide detailed information about the data warehouse jobs.
| Command | Description |
|---|---|
| Get-SCDWMgmtGroup | This command tells you which sources are currently registered with the data warehouse. You should expect to see at least two different DataSourceName values. |
| Get-SCDWJob | This command lists the data warehouse job status of the current batch. Using the command, you can check whether the jobs are enabled or not, which jobs are running, and when they started. When the MPSync or DWMaintenance jobs start, they disable all of the ETL jobs. You will see the Is Enabled column set to False for each of the ETL jobs. This means that even if the ETL job status shows it's running, it actually isn't running. When the MPSync or DWMaintenance job completes, the ETL jobs are automatically enabled and resume processing. Jobs normally have the Not Started status, unless the previous batch has completed. If you prefer, you can use the Get-SCDWJob command to view the last few batches of a specific job. |
| Get-SCDWJob -JobName Specific job name -NumberOfBatches number | Use this command to see the latest job, specified by Specific job name, completed, when it started, and when it ended. You can calculate how long it ran and what the next batch ID and status is. The job batch ID is always incremental. |
| Get-SCDWJobModule | This command provides detailed information about the specific modules within the job. This is useful when you see job failures and you want to find out what caused the failure. |
Troubleshoot common data warehouse issues
This list isn't exhaustive, but it covers most of the common problems that you're likely to encounter.
Reports are not deployed after registering the data warehouse
Symptoms
When you open the Service Manager console, a dialog appears indicating that the Reporting Service is unavailable. Another symptom is that the Reporting workspace button appears in the Service Manager console; however, there are no reports displayed in the workspace. Another symptom is that no reports have been deployed to the Reporting Services server.
Other aspects of the data warehouse deployment might appear to have gone smoothly. For example, in the Service Manager console, when you select Data Warehouse, and select Data Warehouse Jobs, you see two extract jobs, a transform and load job, and an MPSync job.
Troubleshooting Steps
To troubleshoot this problem, complete the following steps.
Step 1: Check the deployment status of your management packs:
In the Service Manager console, select Data Warehouse.
Select Management Packs, and in the search Filter box, enter report. This filters results to report-related management packs.
Check the deployment status (last column) of the following management packs. None of the management packs should have a status of Failed.
ServiceManager.ActivityManagement.Report.Library
ServiceManager.ProblemManagement.Report.Library
ServiceManager.IncidentManagement.Report.Libraryxxx
ServiceManager.ConfigurationManagement.Report.Library
ServiceManager.ChangeManagement.Report.Library
Step 2: Check the event log for error messages that mention the assembly Microsoft.EnterpriseManagement.Reporting.Code.dll file.
If any of the above five management packs failed deployment:
On the data warehouse management server, open the Operations Manager event log.
Filter the events with Event Sources as Deployment and Event Level as Error.
If there are error messages in the event log that indicate cannot load Assembly Microsoft.EnterpriseManagement.Reporting.Code.dll, review the following items:
Your installation of SQL Server Reporting Services (SSRS) may be on a different server than the data warehouse management server.
If your SSRS installation is on the same server as the data warehouse management server, restart the SSRS service.
Restart SSRS:
Sign in to the server where SSRS is installed.
Open Reporting Services Configuration Manager.
In the Reporting Services Configuration Connection window, select Connect.
In the Reporting Server Status window, select Stop, and select Start.
Select Exit.
Step 3: Redeploy any failed report management packs:
In the Service Manager console, select Data Warehouse.
Select Management Packs, and then in the search filter, enter report.
For each of the management packs listed in step 1, in the Tasks Pane, select Restart Deployment.
Note
If the deployment status of a management pack is listed as Completed, the Restart Deployment option is unavailable.
After the deployment status of the report management packs has updated from Failed to Completed, open the Service Manager console. Reports should display in the Reporting workspace. You may have to restart the Service Manager console to view the reports because the console caches the list of reports.
Jobs fail after importing a custom management pack
Symptom
One or more data warehouse jobs start failing after importing a custom management pack and synchronizing it to the data warehouse.
Troubleshooting Steps
To troubleshoot this problem, complete the following steps:
Check the event log to ensure that the root cause is the custom management pack:
On data warehouse management server, open the Operations Manager event log.
Find the event that is related to the job failure.
Determine if the failure is related to the custom management pack you imported.
If the failure is related to the custom management pack, you should remove it and let the rest of the data warehouse operate as usual. You can fix the management pack and reimport it later:
Uninstall the custom management pack using the Service Manager console.
Run the MP Sync job.
Verify that the custom management pack is listed in Data Warehouse under Management Packs.
After the MP Sync job is completed, resume the failed job either from the Service Manager console or with a Windows PowerShell cmdlet.
Fix and reimport the custom management pack:
Remove the custom management pack and recover from the failure using step 2, shown previously.
Fix the custom management pack.
Import the fixed custom management pack into Service Manager, and then run the MP Sync job to sync it to the data warehouse.
Data warehouse is not receiving new data, or jobs seem to take too long to complete
Symptom
You don't see data or new data in any of your reports. Another symptom is that ETL jobs are taking too long to run and the jobs don't show a status of Not Started.
Troubleshooting Steps
To troubleshoot this problem, complete the following steps:
Use the Windows PowerShell cmdlet Get-SCDWJob to determine if all the ETL jobs are enabled. Start Windows PowerShell, and then enter Get-SCDWJob.
If the ETL jobs are disabled and either the MPSyncJob or DWMaintenance jobs are running, you will have to wait awhile to get the job status again because these two background jobs disable the ETL jobs. However, if the two jobs are listed as Not Started and the ETL jobs are disabled, you can use the Enable-SCDWJob cmdlet to enable each of them, for example:
Enable-SCDWJob -JobName Transform.CommonIf the MPSync and DWMaintenance ETL jobs are all enabled and running but their individual batch ID hasn't changed for a long time, or if you use the Get-SCDWJobModule cmdlet for specific jobs and you don't see that any module is actually running, check the event log and see if there are any error messages. Sometimes the error message might be many days old and you might need to review many days-worth of events.
Check if the three services: System Center Data Access Service, Microsoft Monitoring Agent, and System Center Management Configuration on the data warehouse management server are actually running. On the data warehouse management server, select Start, select Run, and then enter Services.msc. In Services, verify that the following services are running: System Center Data Access Service, Microsoft Monitoring Agent, and System Center Management Configuration.
If any of the services aren't running, restart all three services. In addition, if all services are actually running, events from the Event Source Data Warehouse and OpsMgr SDK Service are sent to the Operations Manager event log. You can use this information as another source to verify whether all the services are running. If you don't see events from the Event Source Data Warehouse and OpsMgr SDK Service for a long time, you should restart all three services.
Custom data warehouse extensions do not appear in the data warehouse
Symptom
After importing your management pack, which defines some dimensions or fact tables to Service Manager, the MPSync job has run several times, but you still don't see your dimension or fact tables in the DataMart.
Troubleshooting Steps
Ensure that your management pack is sealed. The MPSync Job can import only sealed management packs from Service Manager into the data warehouse. If you haven't sealed your management pack, seal it, and then import it using the Service Manager.
Ensure that your management pack is synced to the data warehouse by completing the following steps:
Open the Service Manager console.
Select Data Warehouse.
Select Management Packs, and then locate your management pack in the list of management packs. To do this, use the search feature by entering your management pack name in the search box. If you don't see your management pack:
It might have failed to import into the data warehouse management server. Go to the data warehouse management server, open the Operations Manager event log and then filter the events with Event Sources as OpsMgr SDK Service.
The MPSync job may not have run yet. It runs on a recurring schedule, which is, by default, once every hour. You can modify the schedule with Windows PowerShell. To speed up management pack synchronization, after you import your management pack you can manually resume the MPSync job, either from the Service Manager console or by using Windows PowerShell.
Check the deployment status of your management pack:
Open the Service Manager console.
Select Data Warehouse.
Select Management Packs, and then find your management pack in the list of management packs. To do this, you can search for your management pack name.
Check the deployment status of your management pack. If the deployment status is Failed:
On the data warehouse management server, open the Operations Manager event log, and then filter the events with Event Sources as Deployment.
If there's an error message, the message usually indicates what went wrong. If after you make any needed fixes to the management pack and the error still occurs, you can uninstall this management pack using the Service Manager console. After the MPSync job runs, the management pack is uninstalled from data warehouse management server.
Management packs are stuck in Pending Association status after registering to the data warehouse
Symptom
Some management packs remain in Pending Association status several hours after registering Service Manager with the data warehouse and several (up to four or more) hours have passed. You can determine the time elapsed by opening the Service Manager console and navigating to Data Warehouse, Data Warehouse Jobs, MPSync Job, and then selecting Details from the Tasks pane.
Troubleshooting Steps
To troubleshoot this problem, complete the following steps:
View the Details of the MPSync job. Review each batch ID for the problem management pack in the MPSyncJob dialog. In the MP Sync Job dialog, select the Management Pack column name to sort the list according to the management pack name. Find any management packs with Pending Association status. In the list of management packs, check to see if, in the later batch, the management pack status is listed as Associated, for example:
For Batch ID 136, Management Pack Microsoft.SystemCenter.ConfigurationManager is Pending Association.
For Batch ID 207, Management Pack Microsoft.SystemCenter.ConfigurationManager is Associated.
This indicates the management pack is associated properly in batch 207, even though it ran into an error in batch 136. Because it recovered in batch 207, the management pack is correctly associated and the synchronization completed successfully.
If in the MP Sync Job dialog, the Pending Association status for a management pack repeats for every batch, you will have to troubleshoot further to determine the reason why the management pack fails to associate. You should start by looking for deployment failures in other management packs that your management pack depends on.
In the Service Manager console, select Data Warehouse, select Management Packs, and select the Deployment Status column heading. If you see any management pack with a deployment status of Failed or Not Started, this is usually due to a management pack dependency. Because management packs can depend on others, any failure can cause other management packs to fail deployment. Any impacted management pack has the Not Started status.
Find the deployment failures in the event log. Open the Operations Manager Event log on the data warehouse, filter the event log to the events where the Event Source is Deployment and Event Level is Warning or Error.
If there is an error message similar to the following message, you will have to unregister the data warehouse from Service Manager, reinstall the data warehouse, and then re-register the Service Manager management server to the data warehouse management server:
Deployment Execution Infrastructure has retried the maximum number of times and is giving up on this execution step. MP Element ID: DerivedManagementPack.SystemDerivedMp.ServiceManager.ActivityManagement.Library.Datawarehouse MP name: ServiceManager.ActivityManagement.Library.Datawarehouse MP version: 7.0.5826.0 Operation: Install Error message: Cannot find resource with ID TransformActivityStatusResource
ETL jobs fail due to login credentials problems
Symptom
Some or all ETL jobs have failed. The Operations Manager event log on the data warehouse management server indicates that the ETL job failure is related to a login user failure.
Troubleshooting Steps
To troubleshoot this problem, check if the password for each Run As account has changed or expired. You can update the account using the following steps:
Navigate to Data Warehouse, Security, Run As Accounts, and select the related run as account. Select Properties in the Tasks pane, update the Password field in the window, and select OK.
If this Run As account is an Operational System Account, you also have to update the services that are running under the account:
On the data warehouse management server, select Start, select Run, and then enter Services.msc.
In Services, update the passwords for the services that run under the account, for example, System Center Data Access Service and System Center Management Configuration.
Restart the services.
Note
The MP Sync job and Extract jobs can use a different Run As account other than Operational System Account. This Run As account is created when Service Manager is registered to a data warehouse.
It's easy to update the password if it's expired. However, it's more difficult to update the system if you change the Run As account. We don't recommend that you modify Run As accounts.
If the job failure isn't related to the password, ensure that the Run As account for the failed job can be used to connect to the target database. For example, ensure that the Extract job Run As account can be used to connect to the Service Manager database. If not, ensure that the Structured Query Language (SQL) service that is hosting the database is running.