The System Center Operations Manager Support Team Blog

This is the OpsMgr 2007 blog for the Microsoft support team. If you were looking for the SCOM 2007 or MOM 2005 blog then you are in the right place.

OpsMgr 2007 Reporting does not support a SQL SRS Instance name with an underscore character in it

OpsMgr 2007 Reporting does not support a SQL SRS Instance name with an underscore character in it

  • Comments 3
  • Likes

InformationHere's a quick note on an issue I saw recently.  When you are trying to install Reporting for System Center Operations Manager 2007 (SCOM 2007), the installation wizard may hang after you select the SQL SRS Instance and click the Next button if the SQL SRS Instance name has an underscore ( _ ) character in the name.  You will probably also see entries like those below in the setup log:

CAPACK: Binding to CLR version v2.0.50727
Calling custom action ReportingCAManaged!Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSPropertiesCA
MSI (s) (00!3C) [11:03:06:833]: PROPERTY CHANGE: Adding SRSPropertiesFailed property. Its value is '0'.
2010-09-21T11:03:06.9957990-04:00 Debug:

*** Trace Started ***

2010-09-21T11:03:07.0124012-04:00 Debug: SetSRSPropertiesCA: Rosetta Server is: <someName>.
2010-09-21T11:03:07.0153310-04:00 Debug: SetSRSPropertiesCA: SRS Instance is: <name_Name2>
2010-09-21T11:03:07.0446290-04:00 Debug: SetSRSPropertiesCA:  Actual SRS reg location is: SOFTWARE\Microsoft\Microsoft SQL Server\MSRS10.S1_W8USSFJVS93\Setup
MSI (s) (00!3C) [11:03:07:048]: PROPERTY CHANGE: Adding SRS_INSTANCE_REGISTRY_LOCATION property. Its value is '<name>'.
2010-09-21T11:03:07.0514652-04:00 Debug: SetSRSPropertiesCA: SRS Instance is: <name_Name2>
2010-09-21T11:03:07.1881892-04:00 Error: SetSRSPropertiesCA error: Invalid namespace .
MSI (s) (00!3C) [11:03:07:191]: PROPERTY CHANGE: Modifying SRSPropertiesFailed property. Its current value is '0'. Its new value: '1'.
2010-09-21T11:03:07.1950254-04:00 Error: StackTrace:    at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
   at System.Management.ManagementScope.InitializeGuts(Object o)
   at System.Management.ManagementScope.Initialize()
   at Microsoft.SystemCenter.Setup.SQLUtils.GetSRSWMIScope(String computerName, Boolean bIsSql2005, String instanceName, String srsWMINamespace, String srsClass)
   at Microsoft.SystemCenter.Setup.SQLUtils.GetSRSWMIInstance(String sqlSRSServer, String srsServerVersion, String srsClass)
   at Microsoft.Reporting.Setup.ReportingManagedCAs.SetSRSPropertiesCA(Session session)
MSI (s) (00:4C) [11:03:07:653]: NOTE: custom action _SetSRSProperties.9B663534_CD9B_41CC_9D93_4E84D3C5E165 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it. The custom action should be fixed to not close that handle.
Action ended 11:03:07: _SetSRSProperties.9B663534_CD9B_41CC_9D93_4E84D3C5E165. Return value 3.
Action ended 11:03:07: INSTALL. Return value 3.

The underscore character is not supported so if you run into this your only recourse is to uninstall the SQL SRS installation and reinstall SQL SRS using an instance name without an underscore character in it.

Hope this helps,

Milan Jajal | System Center Support Engineer

The App-V Team blog: http://blogs.technet.com/appv/
The WSUS Support Team blog: http://blogs.technet.com/sus/
The SCMDM Support Team blog: http://blogs.technet.com/mdm/
The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/
The OpsMgr Support Team blog: http://blogs.technet.com/operationsmgr/
The SCVMM Team blog: http://blogs.technet.com/scvmm/
The MED-V Team blog: http://blogs.technet.com/medv/
The DPM Team blog: http://blogs.technet.com/dpm/
The OOB Support Team blog: http://blogs.technet.com/oob/
The Opalis Team blog: http://blogs.technet.com/opalis

clip_image001 clip_image002

Comments
  • I am having an issue in installing SCOM R2.

    error:  Setup cannot locate the SC Database

    I have 3 servers

    1 DC (Domain Controller, Win 2008 Ent x64)

    1 DB (Database with SQL 2008 SP2, Win 2008 Ent x86)

    1 SCOM (Win 2008 Ent x64)

    I have opened port 1433 on DB, I have checked the TCP/IP and named Pipes settings on SQL, Every thing is in order, But still i am getting this error again and again.

    Please help me out in this regard.

  • Do we have any solution for this kind of problem ???

  • I resolved it by uninstall the SQL reporting services

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment