WMIPing Utility

I am working on a project that needs to connect to the SQL Server Reporting Services WMI Provider on remote machines.  I have had to work with a number of issues around security and needed a simple tool to help me diagnose them.  To that end I wrote a simple command line application in C# that allows me to pass in a target WMI Namespace as well as optional user name, password, and domain name values to test connectivity.  I thought some others might find it useful as well so I am posting it here.

You can download my WMIPing utility and the .NET (Visual Studio 2008) source code here.

If you are learning to use WMI from .NET, this may also server as a simple sample project.

Let me know if you use it, like it, hate it, want to change it, etc. However, I reserve no rights so feel free to change it on your own as you wish.

There is a readme included with the utility, but the usage is:

WMIPing <TargetNamespace> [<UserName>] [<DomainName>]

  <TargetNamespace> = The target WMI namespace to connect to.
                      For example:


                      To ping a namespace on a
                      remote machine start the namespace with the target
                      machine name.  For example:


                      For a remote machine named "MyServer":


  [<UserName>]      = The optional user name to use when connecting remotely
                      You will be prompted for the password to use
  [<DomainName>]    = The domain to use when connecting remotely.
                      Requires <UserName>

FYI, If you are in the same boat as me and need to connect to a SQL Server Reporting Services instance, you can use this utility to test connectivity to the namespace.

WMIPing "\\<ServerName>\root\Microsoft\SqlServer\ReportServer\RS_<InstanceName>\v10" (assuming it is SQL 2008 or SQL 2008 R2)

In my dev environment, my reporting services server name is called “SQLVM” and I have a default instance (MSSQLSERVER) and named instance named “SQL2008”. 

Testing connectivity to the default instance (MSSQLSERVER) on the SQLVM server would look like:

WMIPing "\\SQLVM\root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\v10"

Connecting to the “SQL2008” named instance would look like:

WMIPing "\\SQLVM\root\Microsoft\SqlServer\ReportServer\RS_SQL2008\v10"


The WMIPing utility doesn’t do anything other than test that you can successfully connect from your client machine to the desired WMI namespace on the target server.

Extracting SSRS Content using the SSIS “Export Column” Component

Download the sample project for this blog post (29kb)

UPDATE – An updated version of this project has been published to codeplex at: http://ssrscatalogqueries.codeplex.com/.  The updated version extracts ALL types of content (not just XML, but resources as well) and also exports the folder structure.  It’s really cool!

A couple of months back I posted an article on “Extracting SSRS Report RDL (XML) from the ReportServer Database”.  Recently, Jason Brimhall posted an article that used similar logic to do a “SSRS Export En Masse”.  It’s a great example of how queries against the ReportServer.dbo.Catalog table can be used to recover reports that have been published to the report server, even if you have lost the source files. 

Jason’s blog post used a combination of Transact-SQL, a For Each loop, and VB.NET Script task to do the work.  As I read through his post, I wondered if the SSIS “Export Column” data flow transform help solve the problem and eliminate VB.NET code.  Turns out it can, and it makes for a pretty simple package.

Note, here is the source query I will use for my SSRS content.  This is based on the queries discussed in my “Extracting SSRS Report RDL …” blog post.  I’ll refer to this query as the “Extract Query” in my list of instructions below.

WITH ItemContentBinaries AS
   ,CASE Type
      WHEN 2 THEN ‘Report’
      WHEN 5 THEN ‘Data Source’
      WHEN 7 THEN ‘Report Part’
      WHEN 8 THEN ‘Shared Dataset’
      ELSE ‘Other’
     END AS TypeDescription
   ,CONVERT(VARBINARY(MAX),Content) AS Content
   FROM ReportServer.dbo.Catalog
   WHERE Type IN (2,5,7,8)
–The second CTE determines the appropriate file extension to use
–plus it strips off the BOM if it exists…
ItemContentNoBOM AS
    ,CASE Type
       WHEN 2 THEN ‘.rdl’  –Report Definition Language
       WHEN 5 THEN ‘.rds’  –Report Data Source
       WHEN 7 THEN ‘.rsc’  –Report Server Component (? – Guessing)
       WHEN 8 THEN ‘.rsd’  –Report Server Data (? – Guessing)
     END AS ExportFileExtension
      WHEN LEFT(Content,3) = 0xEFBBBF
    END AS Content
  FROM ItemContentBinaries
–The outer query gets the content in its varbinary, varchar and xml representations…
   Name + ExportFileExtension AS ExportFileName
  ,CONVERT(xml,Content) AS ContentXML         
FROM ItemContentNoBOM

Here are the steps I followed.  You can download my SSIS project here.

  1. Create a new Package in an SSIS BIDS Project. I named my new package “Export SSRS Content.dtsx”
  2. Create a target folder that the SSRS Content will be exported to.  I created a folder named “C:\SSRS Content Extracts”
  3. Add a Variable to the SSIS Package to store the path to the directory you just created as a string.  I created a variable named “OutputDirectory” and set its default value to “C:\SSRS Content Extracts\” (note the that I included the trailing slash)
  4. Add a “Data Flow” task to your control flow.  I named mine “SSRS Content Extract”
  5. Add a Connection Manager that points to the ReportServer database.  I named mine “ReportServer DB”
  6. Add an “OLE DB Source” to your data flow
    1. I named mine “SSRS Content Source”
    2. Set it to use the “ReportServer DB” connection manager we just created
    3. Set the “Data Access Mode” to “SQL Command”
    4. I pasted the “Extract Query” shown above as the “SQL command text”
  7. Add a “Derived Column” transform to the dataflow and name it “Generate Export Path”. Drag the green data path from the “SSRS Content Source” to it.
  8. Double click on the “Generate Export Path” transform and add a derived column with the following properties (don’t include the double quotes around the values shown below):
    1. Derived Column Name: “ExportPath”
    2. Derived Column: “<add as a new column>”
    3. Expression: “(DT_WSTR,2048)(@[User::OutputDirectory] +  [ExportFileName])”
    4. The Data Type and Length will be set for you based on the expression above. (DT_WSTR, 2048)
  9. Add an “Export Column” transform to the dataflow and name it “Export Content”.  Drag the green data path from the “Generate Export Path” transform to it.
  10. Double click on the “Export Content” transform and configure the values as follows (again, don’t include the double quotes):
    1. Extract Column:  “ContentXML”
    2. File Path Column: “ExportPath”
    3. Allow Append: Cleared
    4. Force Truncate: Checked
    5. Write Byte-Order Mark: Cleared

There you have it.  Pretty simple.  A couple of things to note. 

  • The expression I used in step 8.3 assumes that the “OutputDirectory” variable value includes the trailing forward slash.
  • The “Force Truncate” checkbox set in step 10.4 causes existing files to be overwritten

The resulting data flow looks like this:

SSRS Content Extract Data Flow

You can now run this package (and even supply an alternative export path via the OutputDirectory variable) to export all reports, data sources, report parts, and shared datas sets from an SSRS 2008 R2 installation. 

Download the BIDS project here.