Ops Mgr 2007 RC2 reporting installation tips

Several tips for installation of OM 2007 RC2 (reporting component)


Install always on EN-US regional settings (change this at least for installation time)


Set the collation of SQL to SQL_Latin1_General_CP1_CI_AS (I’ve tested this and it works) or  SQL_Latin1_General_CP1_CS_AS (I haven’t tested, but this is according to supported configurations doc)


If at any stage the reporting installation fails and rolls back you are left with unfunctioning SQL Reporting services instance (due to some small issues in RC2 setup rollback process). To roll it back to previous stage perform these steps:

a. Replace the SRS config files with backup files that setup has created (.0 in extension):

<install dir>:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\rsreportserver.config replace with rsreportserver.config.0
<install dir>:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\web.config replace with web.config.0
<install dir>:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\ReportServer\bin\ReportingServicesService.exe.config replace with ReportingServicesService.exe.config.0

b. Delete the SRS DB’s (ReportServer$<Instancename>) manually from SQL.

c. Use Reporting Services Configuration to create a new ReportServer DB with same name as the previous one.In Web Service Identity in the configuration after creating the DB, select ReportServer and then click Apply.

d. In Reporting Services Configuration, delete the existing encryption keys. If you receive an error deleting the encryption keys, go to the Database Setup part, change the Credentials Type to Service Credentials, click Apply.

e. Run iisreset

f. Restart the SRS service.

g. Check if http://localhost/reports$<instancename&gt; is working


If you get such an error in your MSI install log of OM reporting:

ReplaceSRSExtensionsCA error: RestartService: Unable to start the service ReportServer after 10 minutes

Perform following steps:

Monitor MOMReporting.log (in %temp% folder) using e.g. SMS Trace tool and manually start SQL Reporting service when you see that Setup is hung on this step. After that it will continue.


If you get such an error in your MSI install log of OM reporting:

ReplaceSRSExtensionsCA error: System.Web.Services.Protocols.SoapException: An internal error occurred on the report server. See the error log for more details. —> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException: An internal error occurred on the report server. See the error log for more details. —> System.ServiceModel.FaultException`1: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

System.UnauthorizedAccessException: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))

   at Microsoft.Interop.Security.AzRoles.IAzApplication2.InitializeClientContextFromStringSid(String SidString, Int32 lOptions, Object varReserved)

   at Microsoft.EnterpriseManagement.Mom.Sdk.Authorization.AzManHelper.GetScopedRoleAssignmentsForUser(IList`1 roleNames, String userName)

you can add the SDK service account to Windows Authorization Access Group (if your domain is Windows 2003 level). If you are using Local System as the SDK service account, add the RMS computer account to this group. After this change restart the Ops Mgr server to make sure the change applies. There might be some more feasible way to solve it, but this is the one I tested and it worked.


In order to use kerberos to authorize to the reporting web page register the following SPNs:

setspn -A HTTP/<momreportingcomputername> <yourDataWarehouseReadAccount>

setspn -A HTTP/<momreportingcomputerFQDN> <yourDataWarehouseReadAccount>

Then you will be able to connect to http://<momreportingcomputername&gt; and http://<momreportingcomputerFQDN&gt; with Kerberos and not NTLM authentication.

Details: http://blogs.msdn.com/rdoherty/archive/2006/07/26/678841.aspx

This step might also be necessary if you are getting 401 (unauthorized) errors when accessing the reporting page with dns/netbios name, but you get no error when accessing it with ip address or localhost name.


~ by alipka on January 5, 2007.

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 )


Connecting to %s

%d bloggers like this: