Hi There, I've been trying to get R2 SQL Reporting services Point to work and continue to run into issues that won't allow me to move forward with this. Errors are showing up in the component status. Here is my setup: Single Site, SCCM R2 running on Win2k8 x64 Std Ed. (3 different servers to balance roles) Remote SQL 2005 x64 std Edition server on Win2k8 x64. Reporting services is also running on this server and there are 3 instances (My OpsMgr 2007 reports are here as well as sharepoint 2007). Reporting Services Role is installed on the SQL Server There is no "Reporting Point" role installed I have reporting services setup and configured to the best of my knowledge based on the MS articles for doing so. I can get to my SMSReports instance using the browser. When I go to the ConfigMgr Reporting Services Object and pull up the properties, I am unable to actually specify any information in any of the tabs of the dialogue box. I can't specify datasource, server name, or anything else. Its all greyed out and the General Tab simply says "Unavailable" for all items other then the name of the server hosting the reporting services point. Thanks very much for any assistance you can provide. Cheers, -Darryl Here are some logs: Application Event Log on SQL Server where Reporting Service Point is installed: On 10/7/2008 10:51:17 PM, component SMS_SRS_REPORTING_POINT on computer VM-VICSQL reported: SMS SRS web service is not running on SRS Reporting point server "VM-VICSQL". SRSRP.log SMS_EXECUTIVE started SMS_SRS_REPORTING_POINT as thread ID 3304 (0xCE8). $$<SMS_SRS_REPORTING_POINT><Tue Oct 07 22:51:05.245 2008 Pacific Daylight Time><thread=1772 (0x6EC)>This is a SRS Reporting Point Role as SRSRP registry key exists.~ $$<SMS_SRS_REPORTING_POINT><Tue Oct 07 22:51:05.386 2008 Pacific Daylight Time><thread=3304 (0xCE8)>~Waiting for changes for 0 minutes $$<SMS_SRS_REPORTING_POINT><Tue Oct 07 22:51:05.386 2008 Pacific Daylight Time><thread=3304 (0xCE8)>Timed Out...~ $$<SMS_SRS_REPORTING_POINT><Tue Oct 07 22:51:05.386 2008 Pacific Daylight Time><thread=3304 (0xCE8)>STATMSG: ID=7403 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_SRS_REPORTING_POINT" SYS=VM-VICSQL SITE=ABE PID=5452 TID=3304 GMTDATE=Wed Oct 08 05:51:17.651 2008 ISTR0="VM-VICSQL" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 $$<SMS_SRS_REPORTING_POINT><Tue Oct 07 22:51:17.651 2008 Pacific Daylight Time><thread=3304 (0xCE8)>Failures reported during periodic health check by the SRS Server VM-VICSQL. Will retry check in 57 minutes~ $$<SMS_SRS_REPORTING_POINT><Tue Oct 07 22:51:17.651 2008 Pacific Daylight Time><thread=3304 (0xCE8)>~Waiting for changes for 57 minutes $$<SMS_SRS_REPORTING_POINT><Tue Oct 07 22:51:17.667 2008 Pacific Daylight Time><thread=3304 (0xCE8)> SRSRPSetup.log <10-07-2008 22:51:01> ====================================================================<10-07-2008 22:51:01> SMSSRSRP Setup Started....<10-07-2008 22:51:01> Parameters: \\VM-VICSQL\L$\SMS\bin\i386\ROLESE~1.EXE /install /siteserver:VM-VICSCM01 SMSSRSRP<10-07-2008 22:51:01> Installing Pre Reqs for SMSSRSRP<10-07-2008 22:51:01> ======== Installing Pre Reqs for Role SMSSRSRP ========<10-07-2008 22:51:01> Found 0 Pre Reqs for Role SMSSRSRP <10-07-2008 22:51:01> ======== Completed Installion of Pre Reqs for Role SMSSRSRP ========<10-07-2008 22:51:01> Installing the SMSSRSRP<10-07-2008 22:51:01> Invoking process "C:\Windows\Microsoft.NET\Framework\v2.0.50727\RegAsm.exe" "L:\SMS\bin\i386\SRSSERVER.dll"<10-07-2008 22:51:02> Registered DLL L:\SMS\bin\i386\SRSSERVER.dll<10-07-2008 22:51:02> Installation was successful. SMSAdminUI.log [4][10/7/2008 4:07:31 PM] ystem.Management.ManagementException\r\nNot found \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.Initialize(Boolean getObject) at System.Management.ManagementBaseObject.get_wbemObject() at System.Management.PropertyData.RefreshPropertyInfo() at System.Management.PropertyDataCollection.get_Item(String propertyName) at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.RefreshSiteControlFile(ManagementBaseObject managementObject)\r\nManagementException details:instance of __ExtendedStatus{Operation = "GetObject";ParameterInfo = "SMS_SCI_SysResUse.FileType=2,ItemName=\"[\\\"Display=\\\\\\\\VM-VICSQL\\\\\\\"]MSWNET:[\\\"SMS_SITE=ABE\\\"]\\\\\\\\VM-VICSQL\\\\,SMS Distribution Point\",ItemType=\"System Resource Usage\",SiteCode=\"ABE\"";ProviderName = "WinMgmt";};\r\n[4][10/7/2008 4:07:57 PM] ystem.Management.ManagementException\r\nNot found \r\n at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode) at System.Management.ManagementObject.Initialize(Boolean getObject) at System.Management.ManagementBaseObject.get_wbemObject() at System.Management.PropertyData.RefreshPropertyInfo() at System.Management.PropertyDataCollection.get_Item(String propertyName) at System.Management.ManagementBaseObject.GetPropertyValue(String propertyName) at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.RefreshSiteControlFile(ManagementBaseObject managementObject)\r\nManagementException details:instance of __ExtendedStatus{Operation = "GetObject";ParameterInfo = "SMS_SCI_SysResUse.FileType=2,ItemName=\"[\\\"Display=\\\\\\\\VM-VICSQL\\\\\\\"]MSWNET:[\\\"SMS_SITE=ABE\\\"]\\\\\\\\VM-VICSQL\\\\,SMS SRS Reporting Point\",ItemType=\"System Resource Usage\",SiteCode=\"ABE\"";ProviderName = "WinMgmt";};\r\n[4][10/7/2008 4:12:35 PM] :Creating folder name 'ConfigMgr_ABE', path '/'.[4][10/7/2008 4:13:08 PM] :Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.The request failed with the error message:--<html><head><title>SQL Server Reporting Services</title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.3073.00" /><meta name="HTTP Status" content="500" /><meta name="ProductLocaleID" content="9" /><meta name="CountryLocaleID" content="1033" /><style>BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black}H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline}.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray}A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR3366CC; TEXT-DECORATION:none}A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLORFF3300; TEXT-DECORATION:underline}A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR3366CC; TEXT-DECORATION:none}A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; colorFF3300; TEXT-DECORATION:underline} </style></head><body bgcolor="white"><h1>Reporting Services Error<hr width="100%" size="1" color="silver" /></h1><ul><li>An internal error occurred on the report server. See the error log for more details. (rsInternalError) <a href="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInternalError&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.3073.00" target="_blank">Get Online Help</a></li><ul><li>For more information about this error navigate to the report server on the local server machine, or enable remote errors</li></ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span></ul></body>--.

Hi there, Just wondering if anyone had any thoughts on this problem. I haven't really much more to add. All things being equal the reporting service Instance on the SQL Server seems to work, but the SRS component (SRS Web Service) is what fails thereby prevent any connectivity to the CfgMgr console. What I don't understand, when the Role is installed, it doesn't ask for what instance of reporting server to use which I would think is quite critical. If I have 3 instances of reportings services running on that SQL Server, wouldn't it make sense to ask which one to use? Thanks again, -Darryl

I emailed the SRS dude on our team, and here is his response: This looks to be a little bit of a tricky issue and there could be a couple of problems. First, I'm not sure that co-locating the MOM reporting functionality and the ConfigMgr RSP on the same SRS instance won't cause problems. For example, I know that the MOM SRS implementation implements its own security extension on the SRS server which could complicate things. That said, none of the errors seem to indicate that is the problem. The real problem seems to be when our code attempts to connect to the reporting services web service for the SRS instance. The error that is returned is seen in the adminui log below: " An internal error occurred on the report server. See the error log for more details. (rsInternalError)" "For more information about this error navigate to the report server on the local server machine, or enable remote errors" I would recommend that they examine the logs on the SRS server to see what error is really occurring. I know they mention they are able to navigate to the Report Manager web site for SRS but that really contradicts the error we see in the logs because the Report Manager web site uses the Web Service. They should also verify they are able to access the report server web service directly on the local SRS box. The default url for the web service is http://machinename/reportserver but that depends on how they've configured SRS. Sorry I can't be more specific. This certainly looks like a configuration issue but that contradicts the fact that they claim to be able to access the Report Manager web site.. We'd need to see the SRS log. If you want to send the SRS log, feel free to email it to sccmlogs@microsoft.com

Hi Wally, Thanks for the response. So, I have emailed just about every log I could think of to sccmlogs@... In response to your SRS dude, I can get to the following either locally on the SQL server which is also the Report Server and remotely: http://machinename/SMSReports http://machinename/SMSReportServer I'm able to connect to those and browse the contents, set security, create a folder, etc... so that all seems to be working. What I find confusing is that when I install the Reporting Services Component to the SQL server, it asks me for the folder name to store the reports in (I left the default) but it provide no opportunity to indicate which instance of a report server to use... Does it pull this information out of the ether? The SMS database? I have scoured the documentation for any reference to not being able to handle "Multiple Instances" of a report server and only found that in the referenced docs for setting it up with ConfigMgr it explicitly states that you can choose the default or another instance if you wish. From the technet websitedocs: It would appear: 8. On the Instance Name page, specify a name for the instance of SQL Server you are upgrading. If you are upgrading the default instance of SQL Server, select the Default instance check box, and then click Next. In CfgMgr when I go down to Reporting Services, I attempt get the properties up to set the datasource, etc.. however it presents me with only greyed out boxes and "Unavailable" on the general tab. Thanks again for your assistance.

Response: You can't specify the instance, if he has multiple instances of SRS on the box we'll default to the first instance we find in WMI. Maybe http://machinename/smsreports may not be the first instance, and maybe the first instance isn't configured correctly? Hard to say.. but this is a weird error in the logs: w3wp!library!4!10/10/2008-12:46:46:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.UnknownUserNameException: The user or group name 'domain\user' is not recognized., ; I changed the domain\useras some people seem to be sensitive to exposing that information :-)

Hi, Interesting subject as we're (or were) planning a similar setup. We will be applying R2 in the weeks to come andwe're renewing our OpsMgr infrastructure. Inour design we had foreseen a'System Center'SRS with two instances: -1x OpsMgr Reporting - 1x ConfigMgr Reporting The two instances were amongstother because - likeyour SRS dude says - you can't co-locate OpsMgr with anything else on the same instance since it changes the default security model. NowI'm having serious doubts. ...if he has multiple instances of SRS on the box we'll default to the first instance we find in WMI. isn't exactly giving me lots of confidence to continue on that path. Is this the first instance created, alphabetically ... or random. Thanks, Serge

Okay. I'll check to see what my first instance is on that box (it might actually be the OPS Manager instance which SRS Dude implied might be problematic). If that's the case, Then I suppose my only options are to: Allow Access to the OpsManager Reporting services (not ideal); or Create a new report server and ensure that my first instance is generic and not tied to any other System Center Product... Unless there is a way to alter the default instance of Reporting Services that anyone knows of... Once I confirm this to be the issue I'll mark the answer. Also, if this is truly the case, may I humbly suggest that the documentation for installing Reporting Services for Configuration Manager 2007 R2 be updated to reflect this scenario or circumstance. If I new this out of the gate, I would have verified this to be the case and would have been further ahead. (Otherwise, its been great). Thanks Again. I`ll report back with the results after Canadian Thanksgiving (Monday`s a holiday here).

As I suspected, OpsMgr is my default Reporting Instance on my SQL server box. By creating a default instance of Reporting Services (and point it at the SQL Server Database Engine)on another system and then setting the Reporting Services Point to be on that system, I have successfully established the connection and I can connect to the reporting services without issue. Since OpsMgr allows any instance to be used, I would suggest that if you are planning on having OpsMgr, ChangeMgr reside on the same system, I would suggest that you plan on having a named instance of reporting services for OpsMgr and leave your default installation for ChgMgr. It would be nice to have the system center products work similarly in this regard, perhaps another time though. In the meantime, a change to the documentation to make people aware of this would be desirable. Thanks Wally for leading me in the right direction with SRS Dude. -darryl

Darryl, To be absolutely sure, you say that ConfigMgr requires the Default Instance. Say I have2 named instances on the box, for example <SRSServer>\CONFIGMR & <SRSServer>\OPSMGR, this will not work? But <SRSServer>\<Default> & <SRSServer>\OPSMGR would? Can anyone from MSFT confirm this? Thanks, Serge

If you read into what the response was I last had, our guy said we read the first instance out of WMI. So if your Configmgr instance is listed first, then we should work (from what I read into it).

Hi, Well, that is a good question Serge (and thanks Wally for re-emphasizing).I ran a WMI query against my original choice of server and foundthat the first instance was actually my Sharepoint Integrated reporting site. So that solves one problem (why I couldn't connect) WMI Results ==========================================Computer: %ServerName%==========================================EditionID: -1534726760EditionName: STANDARD EDITIONInstanceID: MSSQL.4InstanceName: SPREPORTSIsSharePointIntegrated: TrueReportManagerUrl: ReportServerUrl: http://%ServerName%/spreportserver EditionID: -1534726760EditionName: STANDARD EDITIONInstanceID: MSSQL.3InstanceName: MSSQLSERVERIsSharePointIntegrated: FalseReportManagerUrl: http://%ServerName%/ReportsReportServerUrl: http://%ServerName%/reportserver EditionID: -1534726760EditionName: STANDARD EDITIONInstanceID: MSSQL.5InstanceName: SMSREPORTSIsSharePointIntegrated: FalseReportManagerUrl: http://%ServerName%/SMSReportsReportServerUrl: http://%ServerName%/smsreportserver This is the script that I used to determine this: Code Snippet On Error Resume Next Const wbemFlagReturnImmediately = &h10Const wbemFlagForwardOnly = &h20 arrComputers = Array("%ServerName%")For Each strComputer In arrComputers WScript.Echo WScript.Echo "==========================================" WScript.Echo "Computer: " & strComputer WScript.Echo "==========================================" Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\Microsoft\SqlServer\ReportServer\v9") Set colItems = objWMIService.ExecQuery("SELECT * FROM MSReportServer_Instance", "WQL", _ wbemFlagReturnImmediately + wbemFlagForwardOnly) For Each objItem In colItems WScript.Echo "EditionID: " & objItem.EditionID WScript.Echo "EditionName: " & objItem.EditionName WScript.Echo "InstanceID: " & objItem.InstanceID WScript.Echo "InstanceName: " & objItem.InstanceName WScript.Echo "IsSharePointIntegrated: " & objItem.IsSharePointIntegrated WScript.Echo "ReportManagerUrl: " & objItem.ReportManagerUrl WScript.Echo "ReportServerUrl: " & objItem.ReportServerUrl WScript.Echo NextNext So I think to answer Serge's question, it would be important to create all the instances of Reporting Services that you plan on having and determine which shows up first in WMI (in case what I'm wondering below is in fact, the case) What I find strange (still) though is that my instances are not numbered in sequence. I would have thought that mssql.3 would come before mssql.4. Does this change? If another instance of reporting services gets installed on that server could it potentially modify the order that WMI reports? Cheers, -Darryl

Hi Darryl, Based on your comments, I went to our lab and tried it out ... 1. Created a Named Instance CMReporting 2. Created a Named Instance OMReporting 3. Configured Reporting Services Point in ConfigMgr 4. Configured Reporting in OpsMgr (as usual playing tricks on me). And ... ConfigMgr Reports run fine! I borrowed your WMIQuery and this is the output ==========================================Computer: SRSServer==========================================EditionID: -1534726760EditionName: STANDARD EDITIONInstanceID: MSSQL.4InstanceName: CMREPORTINGIsSharePointIntegrated: FalseReportManagerUrl: http://SRSServer/CMReportsReportServerUrl: http://SRSServer/cmreportserver EditionID: -1534726760EditionName: STANDARD EDITIONInstanceID: MSSQL.5InstanceName: OMREPORTINGIsSharePointIntegrated: FalseReportManagerUrl: http://SRSServer/OMReportsReportServerUrl: http://SRSServer/omreportserver Cheers, Serge

Sorry to resurect this long dead thread but I've just come across a nice simple solution to re-order the objects in the WMI and though it may help a few people out. (Here: http://www.computersplace.com/sccm-how-to-force-sql-reporting-services-point-to-select-a-specific-srs-instance-on-a-machine-with-multiple-instances-an-unsupported-workaround/othersoftware) I used your script to determine that my SharePoint Reporting Instance was being returned before my default instance: ========================================== Computer: %SERVERNAME% ========================================== EditionID: -1534726760 EditionName: STANDARD EDITION InstanceID: MSSQL.4 InstanceName: SHAREPOINTRS IsSharePointIntegrated: True ReportManagerUrl: ReportServerUrl: http://sharepointreports.fusion-group.net EditionID: -1534726760 EditionName: STANDARD EDITION InstanceID: MSSQL.3 InstanceName: MSSQLSERVER IsSharePointIntegrated: False ReportManagerUrl: http://%SERVERNAME%/Reports ReportServerUrl: http://%SERVERNAME%/reportserver I opened regedit and deleted the HKLM\Software\Microsoft\Microsoft SQL Server\Instance Names\RS\SHAREPOINTRS value and recreated it. My query now returns the following results: ========================================== Computer: %SERVERNAME% ========================================== EditionID: -1534726760 EditionName: STANDARD EDITION InstanceID: MSSQL.3 InstanceName: MSSQLSERVER IsSharePointIntegrated: False ReportManagerUrl: http://%SERVERNAME%/Reports ReportServerUrl: http://%SERVERNAME%/reportserver EditionID: -1534726760 EditionName: STANDARD EDITION InstanceID: MSSQL.4 InstanceName: SHAREPOINTRS IsSharePointIntegrated: True ReportManagerUrl: ReportServerUrl: http://sharepointreports.fusion-group.net Cheers, James.