Since the release of ConfigMgr 2007 SP2, I’m running ConfigMgr 2007 SP2 R2 (in Native Mode) on Windows Server 2008 R2. After installing the ConfigMgr Reporting Services Point I noticed that I couldn’t configure the Reporting Services, because the Data Source Settings where grayed out.
After doing some research and searching online I came on the FAQ about Reporting Services from the ConfigMgr Team. For those FAQ’s take a look at this link: http://blogs.technet.com/configmgrteam/archive/2009/05/14/faq-sql-reporting-services-integration-with-system-center-configuration-manager-2007-r2.aspx
One of these FAQ’s is the following: Do we support https enabled report server instances?
There are known issues in the R2 release with https enabled report server instances. There are some methods in the reporting services webservices API that are inherently secure methods and if SSL is configured on a report server instance these methods cannot be invoked via http and require https connections. Internally, since we leverage some of these APIs, we fail to perform some actions.
Workaround: Unfortunately there is no easy workaround for this other than to not use SSL enabled report server instances. However there is a configuration setting that can be tweaked to get around this problem but it is NOT recommended to tweak this setting if the report server instance is hosting other reports (not specific to Configuration Manager).
Open the rsreportserver.config file using notepad and search for the property "SecureConnectionLevel". This value should be set to 3 (or some value > 0) for secured report server URLs. Change this value to 0 and save the rsreportserver.config file. (The default location for the default instance is under [SystemDrive]:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer).
After using this workaround it all worked like a charm!
2 thoughts on “Data Source Settings of the Reporting Services in ConfigMgr 2007 are grayed out”
Thanks for your post. That solved my problem :o)
I had the exact same issue with a Configuration Manager.
Worked like a charm! Thanks bud! Had me stomped for two days!