You are browsing the archive for 2009 December.

Avatar of alkin

by alkin

System Center Service Manager 2010: Error when registering the Datawarehouse

4:57 pm in Uncategorized by alkin

While registering a Datawarehouse with Service Manager 2010 I got the following error in the eventviewer of the Datawarehouse server…

A module of type "Microsoft.SystemCenter.Orchestration.Module.WorkflowWorkItemModule" reported an exception System.FormatException: String was not recognized as a valid DateTime.
   at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles)
   at System.DateTime.Parse(String s, IFormatProvider provider)
   at Microsoft.SystemCenter.Orchestration.WorkItem.ShredReader(XmlReader wiInstance)
   at Microsoft.SystemCenter.Orchestration.WorkItem..ctor(XmlReader wiInstance)
   at Microsoft.SystemCenter.Orchestration.WorkItem.GetWorkItem(String processCategory, String process)
   at Microsoft.SystemCenter.Orchestration.Module.WorkflowWorkItemModule.PollForNextWorkItemItem()
   at Microsoft.SystemCenter.Orchestration.Module.WorkflowWorkItemModule.OnDataItem(DataItemBase dataItem, DataItemAcknowledgementCallback acknowledgedCallback, Object acknowledgedState, DataItemProcessingCompleteCallback completionCallback, Object completionState) which was running as part of rule "WorkflowOrchestration.DeploymentRule" running for instance "Deployment Workflow Target" with id:"{0B09E978-69C6-709F-5D5E-B03C5477393C}" in management group "xxxxxx".

The problem here was that the system locale from the service account used wasn’t set to English-US

After that change (and rebooting the server) the job succeeded



Avatar of kurtvh

by kurtvh

Importing data into SCSM (part4) – The manual & CSV import CI creation

2:46 pm in Uncategorized by kurtvh

To make the “Importing data into SCSM” blog list complete we also have to provide information about the manual and CSV file import. Previous blog posts have listed the “automated” ways to import CI’s in SCSM from AD, SCCM & SCOM. AD is a source for CI’s that in most cases can be used. SCCM and SCOM add information to existing CI’s and both create new CI’s who are not available in SCSM. In cases where both System Center products are not available, a manual or CVS import can be used for adding CI’s in SCSM.

Manual creation of CI’s:

Computers, printer, Users & Services can be imported via the manual way. (Default mgmt. console folders – other items can be imported and made visible via SCSM View’s.

In brief, the manual procedure (As example, a computer CI is added)

1. In the Service Manager console, select Configuration Items.

2. In the Configuration Items pane, expand Configuration Items, and then expand Computers. In order to create a new printer, User or service, select the appropriate folder.

3. Select All Computers, and then in the Tasks pane, under Computers, click Create Computer.

4. In the form that appears, create a configuration item for a computer. Use the General, Software and Related Items tabs to fill in the information about the computer.


5. Click OK to save the new configuration item.

For your information, some form screenshots of the creation of the other CI’s.

Note: Not all fields can be provided with data via the CSV file import. In certain cases it is mandatory to have SCCM or SCOM to add the required data.

  • Form for new printer CI’s


  • Form for New service CI’s


  • Form for New User CI’s


CSV import

Configuration items contained in a comma-separated values (CSV) file can be imported into the Service Manager database by using the Import from CSV file feature. This feature allows you to bulk-import instances of any class type or projection type that is defined in the Service Manager database. This feature can be used to:

  • Create Configuration Item or Work Item instances from data stored in a tabular format.
  • Bulk-edit existing database instances.
  • Populate the Service Manager database with data exported from an external database.
  • Circumvent data entry through forms when many class instances must be created at once.

Two files are required to import a set of instances by using the CSV import feature:

  • A data file that consists of a series of comma-delimited object instances. The data file must end with the ".csv" file name extension.
  • A format file that specifies the class type or projection type of the instances present in the data file. Every instance in the data file is assumed to be of this type. The format file also specifies
    • The subset of properties (and in the case of projections, components) being imported for the indicated type.
    • The order in which those properties appear (as columns) in the associated data file. The format file must have the same file name as the "csv" file that it describes, and it must end with the ".xml" file name extension.

Note: For more information about CSV import and class type or projection types, see the blog post Using the CSV import feature ( and download the file CSVImport.docx. Very good explanation about the topic…

The creation of the CSV data file

To use the CSV Importer, we first need to save the spreadsheet as a “.csv” file. The first row of the spreadsheet is assumed to contain an object instance (and not a header), so we remove this line and save the spreadsheet in a file named "import.csv".

Example of a csv file


Creating the format file

The data file “import.csv” is now created. Next step is the creation of a format file that is suitable for importing the rows contained in the import.csv file. The first step in writing the format file is identifying the class type or projection type to be used for the instances in the CSV file.

Microsoft.Windows.Computer is the most appropriate choice for the object type and property set that we wish to import. We begin by declaring the class of the object being imported:


<Class Type="Microsoft.Windows.Computer">



In our example the format file should look like this:


When these files are created, we can import this information into SCSM.

Import of the data in SCSM

With the format and data files prepared, we are ready to use the CSV Import task.

1. To access it, navigate to the Administration page in SCSM console

2. Click on the Connectors folder and select the Import from CSV file… task


3. On the Import Instances from CSV file page, provide the path to the xml format file and the actual CSV file.


4. Click Import to start the creation of the CI’s in SCSM.

5. After the import a summary page is provided with the results of the import.

6. All done…imported items should be visible in the Configuration items page in SCSM (corresponding folders)

Update of a CI via CSV

The update of a CI in SCSM goes in a similar way. Creation of the CSV file with a correct format file is required. When we re-use the example from above, the CSV and format files need to be updated with the additional information.

For example, we add the required Properties.


FYI: List of possible Property ID’s for the Microsoft.Windows.Computer class


After the update on the format file we need to add the proper information in the CSV file.


Import the CSV file and job done!


Kurt Van Hoecke

Part 1: (Importing data into SCSM (part 1) – the SCSM AD & SCCM connectors)

Part 2: (Importing data into SCSM (part2) – the SCSM OpsMgr Alert connector)

Part 3: (Importing data into SCSM (part3) – the SCSM OpsMgr CI connector)

Avatar of kurtvh

by kurtvh

Importing data into SCSM (part3) – the SCSM OpsMgr CI connector

10:06 pm in Uncategorized by kurtvh

As specified in previous blog, two OpsMgr connectors are available in Service Manager:

  • Operations Manager Alert connector: The OpsMgr alert connector is used to automatically generate incidents that are based on Operations Manager alerts.
  • Operations Manager CI connector: This connector will import objects that were discovered by Operations Manager into the Service Manager database. (For example, distributed apps or SQL databases.)

This blog will handle the Operations Manager CI Connector.

There are two steps that need to be followed for the installation of the OpsMgr CI connector:

  • Import of the management packs: In order to import objects discovered in Operations Manager, Service Manager will need a list of class definitions for these objects that we can obtain from the Operations Manager management packs.
  • Installation of the OpsMgr CI connector in SCSM: The actual installation and configuration of the connector in the SCSM mgmt console.

Import the management packs

Download the file InstallOMMPs.exe from the Connect Web site

1. On the SCSM server, create a folder for the file InstallOMMPs.exe. (for example D:\MP)

2. Double-click InstallOMMPs.exe to extract the files.

3. In the Unzip to folder field, type the location of the folder that you created in step 1, and then click Unzip. (D:\MP)

4. On the Windows desktop, click Start, click Programs, click Windows PowerShell 1.0, right-click Windows PowerShell, and then click Run as administrator.

5. Change directories to folder you created in step 1, and then click ENTER. (D:\MP)

6. In the Windows PowerShell window, run the following commands:

1. set-ExecutionPolicy unrestricted

2. .\installOMMPs.ps1


1. Type exit and then press ENTER.

If you have installed additional management packs in Operations Manager and you want to add the data from those additional management packs to Service Manager, you can edit the Operations Manager CI Connector to add the additional management packs.

  • Copy the OpsMgr Mgmt pack to the folder where InstallOMMPs.exe is extracted (In this example D:\MP)
  • Add a line with the mgmt pack name on the en of the following section of the Powershell script.


Import of the mgmt packs can be verified in the Management pack folder in Administration pane of the SCSM console.

Installation of the OpsMgr CI connector in SCSM

Follow this procedure to create an Operations Manager 2007 CI Connector:

1. In the SCSM console, click Administration.

2. In the Administration pane, expand Administration, and then click Connectors.

3. In the Tasks pane, under Connectors, click Create Connector, and then select Operations Manager CI Connector.


4. On the General page, in the Name box, type a name for the new connector. Make sure that Enabled is selected, and then click Next.


5. On the Server Details page, in the Server name box, type the name of the server that is hosting the Operations Manager root management server.

Under Credentials, either select the Run As account you created for the Alert connector and proceed, or click New and in the User name, Password, and Domain fields, type the credentials for the Run As account, and then click OK.

Test the connection before preceding the wizard.


6. On the MP Selection page, either click Select all or select the management packs which define the configuration items you would like to import, and then click Next.


7. On the Schedule page, adjust the Synchronization schedule as needed and click Next.


8. On the Summary page, review the configuration and then click Create.

9. On the Completion page, click Close.


To validate the creation of an Operations Manager 2007 CI Connector

  • Objects discovered by Operations Manager are listed as Configuration Items in Service Manager.
  • Confirm the status of a connector by viewing the columns in the Connector pane where you will find information such as Start Time, Finish Time, Status, and Percentage.


Create Views for the imported CI’s

Configuring the OpsMgr CI Connector indicates that additional Configuration Items are required in SCSM. SCSM does not have system-defined views or forms for some items, like imported items via the OpsMgr CI Connector. Own created views can make this CI’s visible in the SCSM console.

Follow the procedures below to create a view for imported SQL Server database configuration items.

1. In the Service Manager console, select Configuration Items.

2. In the Configuration Items pane, right click Configuration Items, and then click Create folder. (This is an optional step, you can create own views in existing folders)


3. In the Create folder page, provide a name for the folder and the management pack to store the information. Keep in mind to organize your information in the proper mgmt. packs. In this example we use an own created mgmt. pack for Views.


4. Back in the Configuration Items pane, select on the just created folder. In the Tasks pane, click Create View.

5. In the Create View dialog box, on the General page, in the Name text box, type a name for the new view. For example, type SQL Databases.

In the Description box, enter a description of the view you are creating. Click OK.


6. Drill down to the Criteria section,Search for objects of specific class, click Browse.

7. In the Choose Class dialog box, in the View list select All basic classes.

8. In the Search text field, type SQL, and then click the search button (blue magnifying glass).

9. In the Class list, select SQL database, and then click OK.


10. No further criteria are required for this example and we can remove the existing criteria from the box.


11. Click the Display tab then in the Columns to display list, select Database Name, Database Size (MB) String, and other items that could be interested for as console info. Click OK.


12. Select the new view named SQL Server Databases to see the list of the imported SQL databases.


All done…



Kurt Van Hoecke

This is a second post in the importing data into SCSM series:

Part 1: (Importing data into SCSM (part 1) – the SCSM AD & SCCM connectors)

Part 2: (Importing data into SCSM (part 2) – the SCSM OpsMgr Alert connector)