setup is SCCM SP2 R2 with SQL 2005 server on separate box. I am using a separate instance on the SQL server to host the sccm database.I can add the Configmgr reporting services point to the site system hosting the SQL server. The SCCM database on the external host is recognised by SCCM (ms-sql\misc instance). However, under reporting services properties, every tab is greyed out as if it can not communicate with the server. How do I fix this?Thanks,-T

Are you running Native Mode? If so, then take a look here: http://www.petervanderwoude.nl/post/Data-Source-Settings-of-the-Reporting-Services-in-ConfigMgr-2007-are-grayed-out.aspxMy Blog: http://www.petervanderwoude.nl/

NO, I am in Mixed mode. in any case SecureConnectionLevel is set to 0 curently. Any more ideas?Thanks,-T

Any chance SQL reporting services is running as a named instance?When you install a SQL Reporting Services Point, Configuration Manager2007 queries Windows Management Instrumentation (WMI) for installed instances of SQL Reporting Services. The report folder is installed on the first instance of SQL Reporting Services found by the WMI query. If you have installed multiple instances of SQL Reporting Services and are unsure about whether the instance on which you want to install the report folder is the first stored in WMI, it is recommended that you install the SQL Reporting Services Point on a computer running only one instance of SQL Reporting Services.Source: http://technet.microsoft.com/en-us/library/cc161824.aspxThe abovementioned wmi query, fails however if no default instance Sql reporting services has been set up. 6) Are named report server instances supported with Configuration Manager 2007 R2 release? With the R2 release there is no explicit way to specify a named report server instance anywhere. What this means is that we query WMI to retrieve the list of report server instances and pick the first instance returned by WMI. Implication: If the report server machine has 2 instances of reporting services running on it (let us say the default instance and another named instance) and if WMI returns the default instance as the first instance then that would be the instance used to host all the Configuration Manager reports. So usage of a named instance is non-deterministic and is dependent on what is returned by WMI. There were some issues that were uncovered after we shipped R2 which introduces a caveat: a) If the report server machine hosts only a named instance, then we will not be able to detect the named instance since the WMI query we use to enumerate instances requires the presence of the default instance. Workaround: So in order to detect the named instance, you should have the default instance installed on the same machine. Source: http://blogs.technet.com/configmgrteam/archive/2009/05/14/faq-sql-reporting-services-integration-with-system-center-configuration-manager-2007-r2.aspx"Everyone is an expert at something" Kim Oppalfens Configmgr expert for lack of any other expertise. http://www.scug.be/blogs/sccm

As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as Answered as the previous steps should be helpful for many similar scenarios. If the issue still persists and you want to return to this question, please reply this post directly so we will be notified to follow it up. You can also choose to unmark the answer as you wish. In addition, wed love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems. Thanks!Jie-Feng Ren - MSFT

sorry the issue still persist. I do have couple of name instances on the SQL server. Adding a default instance and putting SSRS on it did not do anything. The configuration tabs are still grayed out.

Any update/suggestions for this issue? I'm having the same problem described above (all property pages for Reporting Services in the SCCM console are grayed-out, mixed-mode SCCM, R2/SP2, remote SRS and separate SQL DB server. SRS is using the default instance, the DB is on another SQL server). Logging onto the SRS box, I can open the /Reports folder, drill down through the SCCM reports and view them all...from any other machine I can open a browser and hit SRS and run all the SCCM reports successfully. It's just through the console that everything is "unavailable" and/or grayed-out. Thanks in advance,

I could also use an update to this as I am experiencing the same issue described: all property pages for Reporting Services in the SCCM console are grayed-out, mixed-mode SCCM, R2/SP2, SRS is using the default instance - only difference is I'm hosting a local SRS and SQL DB server. Please provide further feedback. Thanks!

I am having the same problem with everything grayed out. My setup is pretty simple I think. SCCM 2007 sp2 r2, win2008 r2, sql 2008, everything installed on the same box and nothing is allocated to or shared with any other program. My sql server name is SCCMp01 \ SCCMSQL Database name is ReportServer$SCCMSQL Report Server Mode: Native Web Services Virtual Directory "ReportServer" Report Manager virtual Directory "Reports" I can browse to both URL's and get a page that kinda looks like sharepoint. When I go into SCCM and add the reporting services point it appears gray. Under my component status it lists SMS_SRS_Reporting_point says warning. No matter how many times I add or delete the reporting services point it always stays grey and won't allow me to copy reports...it says "Unable to communicated with the server"

I also am experiencing the greyed out configuration options. In the event log I'm getting Source: SMS server EventID: 7404 On 07/21/10 17:54:42, component SMS_SRS_REPORTING_POINT on computer SCCM reported: SRS is not installed or properly configured on SRS Reporting point server "SCCM". Presumably this could be because SRS is not configured in SCCM. The workaround suggested above by Kim Oppalfens is to install the default instance on the same machine. I'm an extreme newbie when it comes to both SQL and SCCM. I'm sorry for asking this question but how do I install the default instance? Do I just run setup again and accept all the defaults? Will that harm my existing installation? Thanks for your help. Note: I tried changing SecureConnectionLevel from 0 to 3 (I'm in mixed mode) but that didn't help.

Check if you can browse to http://yourserver/reports and http://yourserver/reportserver.

No, I can't get to either of those sites. I get HTTP Error 404.0 - Not Found The resource you are looking for has been removed, had its name changed, or is temporarily unavailable. So, what does that mean? I'm running on Server 2008 (SCCM and SQL on the same machine). I followed the procedure for running on 2008 (http://technet.microsoft.com/en-us/library/cc431377.aspx) or at least I thought I did it successfully. Thanks for your help.

Have you installed SRS (SQL Reporting Services) at all? That won't happen automatically.

Yes it is installed. It's listed in my Microsoft SQL Server 2008 Setup Discovery Report and, on the start menu I have Reporting Services Configuration Manager which I assume wouldn't be there if SRS was not isntalled.

The key here is to be able to get to the SSRS website. In my experience I've found that once you can get the SSRS site up and assign the right permissions, SCCM falls right into place. just taking a wild guess here: I had a problem with SRS due to a conflict of bit versions of products. I ran into SCCM sp2 r2 installed on server 2008 R2 x64. SQL 2005 x86 was being used to host the SCCM DB on the same machine. x86 SSRS cannot run correctly on a x64 IIS instance with out some modifications to allow 32bit apps to run. see this link: http://msdn.microsoft.com/en-us/library/ms143293%28SQL.90%29.aspx but we could never get any of the clients to communicate after those changes. please see this: http://forums.iis.net/t/1168610.aspx luckily, this was in a DEV/POC environment and we just rebuilt the server. Like I said, wild guess that this may be your issue. But once we started using x64 SQL and OS, it worked like a charm.

Actually, I CAN browse to those sites except the names are http://myserver.mydomain.edu/Reports_SCCM and http://myserver.mydomain.edu/reportserver_SCCM. I needed to append the _SCCM to the site to get it to work. Sorry, I'm a newbie to the max. The Reports_SCCM site give a page with tabs Contents and Properties and the contents tab shows "There are no items in Home ...." The reportserver_SCCM page is more generic in appearance and says "Microsoft SQL Server Reporting Services Version 10.0.1600.22. So, where do I proceed from here? Thanks for your help.

Thanks for the suggestion. SCCM 2007, SQL 2008 and the Windows Server 2008 virtual machine that they are running on are 32-bit. The HyperV host on which the VM is running is Server 2008 R2 64-bit.

I just noticed something that may provide a clue. In the Configuration Manager Console if I go to Site Database\Computer Management\Reporting\Reporting Services and select properties for my server (\\SCCM), on the Data Source Autentication tab there appears to be an error message. Under "Credentials supplied by the user running the report" it says "Display the following text to prompt the user for a user name and password." In the box below that it says "Error connecting to report server 'SCCM'." The option Windows integrated security (not "Credentials supplied by the user running the report") seems to be the selected option although everything is greyed out on the Data Source Authentication tab and all other tabs.

I'm also tearing my hair out with this problem as it is the last thing I need to configure for my SP2 > R3 upgrade is SRS. I've set up 2 W2K8 R2 64-bit Virtual Servers - "V01" is my SCCM Box, and "V03" is My SRS Box. I have MS SQL 2008 64bit installed on both Virutal servers. My SCCM 2007 Database is a named instance, but is the only instance on that server. My SRS Database is a default instance i.e. "MSSQL2008" I've installed SRS on my SRS Box (V03) and configured it using the Reporting Services Configuration Manager. Everthing tested and connected without errors. I created a new Reporting Services Database "ReportServer". All of the steps under the "Progress and finish" section of the database step returned results of "Successful". I can access http://stiga-v03/ReportServer and http://stiga-v03/Reports and get the correct pages to display. I can do this from the SRS box (V03), and also from my SCCM box (V01) as well. However, when I create the Reporting Services Point in ConfigMgr, and expand Computers> Reporting> Reporting Services - the server it shows is my SCCM server "V01", and all of the "Properties Tabs" i.e. Data Source, etc are all blank and greyed out. The "General" tab shows everything on it as being "Unavailable" Why on earth isn't it possible for the ConfigMgr Reporting Point Creation Wizard to have a step in it where it asks you to provide the SQL Server/Instance & account connection details hosting your SRS!? It shouldn't be anywhere near this difficult or convoluted a process. I'm also confused as to whether I need SRS installed and configured on both my SCCM and SRS server, or just my SRS server, in order to get this to work?

I'm also tearing my hair out with this problem as it is the last thing I need to configure for my SP2 > R3 upgrade is SRS. I've set up 2 W2K8 R2 64-bit Virtual Servers - "V01" is my SCCM Box, and "V03" is My SRS Box. I have MS SQL 2008 64bit installed on both Virutal servers. My SCCM 2007 Database is a named instance, but is the only instance on that server. My SRS Database is a default instance i.e. "MSSQL2008" I've installed SRS on my SRS Box (V03) and configured it using the Reporting Services Configuration Manager. Everthing tested and connected without errors. I created a new Reporting Services Database "ReportServer". All of the steps under the "Progress and finish" section of the database step returned results of "Successful". I can access http://stiga-v03/ReportServer and http://stiga-v03/Reports and get the correct pages to display. I can do this from the SRS box (V03), and also from my SCCM box (V01) as well. However, when I create the Reporting Services Point in ConfigMgr, and expand Computers> Reporting> Reporting Services - the server it shows is my SCCM server "V01", and all of the "Properties Tabs" i.e. Data Source, etc are all blank and greyed out. The "General" tab shows everything on it as being "Unavailable" Why on earth isn't it possible for the ConfigMgr Reporting Point Creation Wizard to have a step in it where it asks you to provide the SQL Server/Instance & account connection details hosting your SRS!? It shouldn't be anywhere near this difficult or convoluted a process. I'm also confused as to whether I need SRS installed and configured on both my SCCM and SRS server, or just my SRS server, in order to get this to work?

I'm also tearing my hair out with this problem as SRS is the last thing I need to configure for my SP2 > R3 upgrade to be complete. I've set up 2 W2K8 R2 64-bit Virtual Servers - "V01" is my SCCM Box, and "V03" is My SRS Box. I have MS SQL 2008 64-bit installed on both Virtual servers. My SCCM 2007 Database is a named instance, but is the only instance on that server. V03 (SRS) has a default SQL instance installed i.e. "MSSQL2008" & SRS installed. It is the only instance on that server. I've configured SRS on V03 using the Reporting Services Configuration Manager. Everthing tested and connected without errors. I created a new Reporting Services Database "ReportServer". All of the steps under the "Progress and finish" section of the database step returned results of "Successful". I can access http://V03/ReportServer and http://V03/Reports and get the correct pages to display. I can do this from the SRS box (V03), and also from my SCCM box (V01) as well. However, when I create the Reporting Services Point in ConfigMgr, and expand Computers> Reporting> Reporting Services - the server it shows is my SCCM server "V01", and all of the "Properties Tabs" i.e. Data Source, etc are all blank and greyed out. The "General" tab shows everything on it as being "Unavailable" Why isn't it possible for the ConfigMgr Reporting Point Creation Wizard to have a step in it where it asks you to provide the SQL Server/Instance & account connection details hosting your SRS!? It shouldn't be anywhere near this difficult or convoluted a process. I'm also confused as to whether I need SRS installed and configured on both my SCCM and SRS server, or just my SRS server, in order to get this to work?

I am also having the same issue with greyed out options and I cannot view the report server URL. When I try to load the page I gett the following, and I also do not have the registry key mentioned there: Line 27: <assemblies> Line 28: <clear /> Line 29: <add assembly="ReportingServicesWebServer" /> Line 30: </assemblies> Line 31: </compilation> Source File: C:\inetpub\wwwroot\ReportServer\web.config Line: 29 Assembly Load Trace: The following information can be helpful to determine why the assembly 'ReportingServicesWebServer' could not be loaded. WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. Everything in the configure report server setup has a green checkmark. I've read other posts refer to a wmi default instance query. How can I verify if I've accidentaly created more than one default instance? We only use this server for SCCM along with any of the software it depends on.

I gave up on troubleshooting and did a complete re-install of server 2008 and used this guide to get SQL reporting services working before installing SCCM: http://blogs.technet.com/b/mwiles/archive/2009/02/19/east-setup-of-srs-with-config-manager-r2.aspx This got reporting services to work. However, I later installed Forefront Endpoint Protection 2010 because it needs to be installed on the SCCM server and the reporting services is not working properly again. There's two sections when I open my reports site, one for SCCM and one for Forefront. The Forefront reports show up fine, but the SCCM reports no longer work. I really hope reporting services is a lot more reliable when used with SCCM 2012, it's been the most difficult thing to get working properly and keep it working properly.

Update: If you open up IE and go to your reporting services page and click on the first entry in the list of reports. Mine shows up as {5C6358F2-4BB6-4a1b-A16E-8D96795D8602}. Your connection string should show: Persist Security Info=False;Initial Catalog=sms_YourThreeLetterSiteCode;Data Source=YourSccmServerName; Mine had missing info and I basically copied the format from what showed up on the forefront report.

I had to get the website up and running and next copied some reports over. While the "Properties" - Report Folder, Status, Size and Contains were showing "unavailable", they populated after I've actually RUN one of the copied over reports.