Changing the URL and/or Port of Reporting in Service Manager 2012

So, I have come across this requirement a few times.  Usually this comes as a result of either the URL of Reporting Services needing to be changed to something other than the server name of where it is deployed (Load-balancing), or in order to use SSL certificates with the reporting components.

Since Reporting is part of the Data Warehouse, you might expect that there the Microsoft documentation here might contain all the details.  It does do a great job of explaining how to relocate the Data Warehouse databases. The document does detail where we can find the Reporting Services configuration in the registry on the data warehouse server:

image

So, you might think that to achieve what we set out to here would simply reconfiguring the registry on the Data Warehouse Server and Reporting Services instance.  So let’s walk through it.

In the case of the above example, moving the port from 81 to 80.  To do this we first need to reconfigure Reporting Services to use a different port for the Reporting Services Web Service and Report Manager URLs.  This is done in Reporting Service Configuration Manager.

image

image

Once done, we change the  WebServiceURL registry entry on the Data Warehouse server to reflect the change in port:

image

Then we restart the System Center Data Access Service and System Center Management Configuration services.

image

Now, you might think this will do the trick.  However, every time I have done this in the past, when opening the Service Manager Console the result has always been the same:

image

NO REPORTS!!!!!

So, this got me thinking, there must be something else which references the SSRS web service.

The article for moving the Data Warehouse databases tells us how to locate and move various parts of the Data Warehouse databases.  One of which is the Analysis Services database.  From the document, it tells is to do the following to locate this:

$class= get-scclass –Name Microsoft.SystemCenter.ResourceAccessLayer.ASResourceStore –ComputerName <DWServerName>
$OLAPServer= get-scclassinstance –class $class –ComputerName <DWServerName>
$OLAPServer.Server

So, this to me tells us that there is a Class of object for the Analysis Services database.  If this is the case, then maybe there is a similar class for Reporting also.  To find out I logged onto my Data Warehouse Server and imported the Data Warehouse PowerShell module.  I then issued the following command:

Get-SCClass | where-Object {$_.Name –like “Microsoft.SystemCenter.ResourceAccessLayer*” | Select-Object Name, DisplayName

This gave me the following:

image

As we can see, there is a class for SSRS Resource Store (internal)

Now, the majority of the Data Warehouse configuration is stored in the database named DWStagingAndConfig.  The document describes how we can change the data sources for the Data Warehouse databases.  However, if we look closely we can also see a table for the SSRS Resource Store (internal) class, dbo.MT_Microsoft$SystemCenter$ResourceAccessLayer$SrsResourceStore.

image

Selecting from this table gave the following result:

image

As you can see, the URL for the Reporting Services Web Service is in here, with the old port (81).  I updated this to be the new port (80)  by right-clicking the table and selecting Edit top 200 rows.  I then went to my Service Manager Console, closed it and then re-opened it.  And here is the result:

image

A FULL QUOTA OF REPORTS!!!  Smile

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s

search previous next tag category expand menu location phone mail time cart zoom edit close