I am having a problem with SSRS data sources being mysteriously disabled in a SharePoint 2010, SSRS integrated-mode environment.
When I set up the data source, it is saved and I verify that it is enabled. I can also successfully execute a report that uses that data source. At some point later, it is disabled. I can't figure out why, and it's driving me crazy.
Has anyone else experienced this?
My environment:
SharePoint 2010 Farm
One WFE
Two SharePoint-integrated SSRS app servers
One database server
Read this two articles:
Sharepoint dropping link to Data Source for SSRS reports
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/91016bff-20e7-446a-bb70-7be407096faf/sharepoint-dropping-link-to-data-source-for-ssrs-reports
Reporting Services Data Source are getting disabled when deployed on SSRS Integrated mode
http://connect.microsoft.com/SQLServer/feedback/details/742238/reporting-services-data-source-are-getting-disabled-when-deployed-on-ssrs-integrated-mode
In a nutshell:
It was related to some sort of problem with the Encrytion Keys set up in Reporting Services Configuration Manager .... Sharepoint Integration was also showing as Not Configured (despite the fact that it was working in Integration mode)
When I put in the Windows Account password under Windows Service Identity it once again prompted for saving the Encryption Key to a file ... once this was done Sharepoint Integration shows as Configured and the nightly problem (2AM when the Reporting Services daily maintenance programs run) goes away ....
Related
I have developed SSIS Package to fetch data from SharePoint Lists and importing to the SQL Server Tables. I am going to deploy this package as a Project Deployment Model.
From these SQL Tables, I have built SSRS Reporting Solution including few reports and Deployed it on my Development SharePoint Site.
But now, I have no idea how to send this solution with reports to the Client Side.
I have checked below utilities but not getting the exact idea of what I should do.
http://rsbuild.codeplex.com/
http://msdn.microsoft.com/en-us/library/ms162839%28v=sql.110%29.aspx
SQL Server version I am using is SQL Server 2012 and Data tools version is also 2012.
Please guide me here.
Thank you,
Mittal.
To deploy your reporting objects, you right-click on the project in Visual Studio then select deploy and configure the server to deploy to.
If you are trying to get an already deployed package, you can use the import wizard:
e.g.
http://msdn.microsoft.com/en-us/library/hh270294.aspx
Then the report server can be accessed by the client browser - e.g. in internet explorer, browse to to: http:
//reportserver/reports
Where "reportserver" can either be the server's ip address or reporting server name.
You can also modify these reports using the report builder tool, that will allow you to edit the rdl files on the server - e.g. when you browse to the reports, you can select edit with report builder.
If you are using sharepoint, you can use sharepoint authentication mode or you can set up access based on active directory groups at the folder level, if the client is browsing to the reports using the web browser.
I am a total newbie in SQL/SQL server stuff, and I am using SSRS to make a new reporting server/service and upload some .rdl files to it
I have a reporting server on a machine, which has a lot of reports and data sources uploaded to it's database.
I created a new reporting server with a fresh database on another machine, and what I want to do is to copy the old database content to the fresh one (the reports and the datasources..etc)
I have no copy of the individual reports to upload them to the new server using localhost/reports
is there's a fast solution to what i am having? please do it in detail because I never worked with SQL before.
Different ways to do this:
Report Server Databases
Use the detach/attach or backup/restore instructions here. Both of these methods require a backup of encryption keys on the existing instance, which are then restored to the new report server instance. Instructions on backup/restore of encryption keys here. Migrating the ReportServer and ReportServerTempdb databases is the easiest way to ensure all content is available on the new server.
Report Object Scripting
Reporting Services Scripter is an older (but still working with SSRS 2008R2, not sure about 2012) tool that can be used to transfer objects (folders, shared data sources, shared data sets, reports, etc) between report servers. Good choice if you want to pick and choose what is migrated.
If you are receiving an error regarding unsupported scale-out deployment, this means you are running Standard edition and need to remove the old report server entry from the database in the new location. It can be done using Reporting Services Configuration Manager, or by using rskeymgmt at command line.
Reporting Services Configuration Manager
Open Reporting Services Configuration Manager and connect to the new report server instance.
Click on Scale-out Deployment to view registered report servers.
Select the old report server instance and click the Remove Server button.
Command line and rskeymgmt
Browse to the Tools\Binn folder of your SQL Server client installation.
Run the following to list registered report servers
rskeymgmt -l -i
Using the installation ID (GUID) of the old report server, remove it
rskeymgmt -r -i
More info on scale-out deployments and rskeymgmt here.
To migrate Reporting Services, use migration manual from MSDN (https://msdn.microsoft.com/en-us/library/ms143724(v=sql.120).aspx). If you encounter "the feature: scale-out deployment is not supported in this edition of reporting services. (rsoperation notsupported)" error, go to ReportServer database and remove the old encryption key from table dbo.Keys.
I have a SQL Server 2012 reporting Services in native mode. The report server url is:
http//hodentekwin7/ReportServer_Kailua
This which works fine.
I have SharePoint 2010 installed it is working fine, i.e. I can access Central administration. So far no problem.
I have installed SQL Server 2008 R2 for SharePoint Integrated mode, and have been able in SharePoint Adminsitration to:
Get database access with my login credentials
Successfully added to the WSS_WPG membership
Specified activation and deactivation in all site collections
However, when I try to set the Report Server site settings I get this error:
The report server cannot decrypt the symmetric key that is used to access sensitive or encrypted data in a report server database. You must either restore a backup key or delete all encrypted content. (rsReportServerDisabled) Get Online Help
Bad Data. (Exception from HRESULT: 0x80090005)
Well, SQL Server 2008 R2's Configuration Manager is not even accessed even once to set up any kind of encryption. I cannot even access the server.
The Microsoft link for this error helps is a page which is not available.
The Report Server is working but cannot be configured. The Report server databases are present. SSRS 2008 R2 was never configured through the Configuration Manager of RS.
Some tips on MS Site regarding "deleting all encrypted keys" requires access to SSRS Configuration tool (which is not available for SSRS with SharePoint).
Any workaround?
Finally found the answer. I deleted all encrypted content. The funny thing is it was a fresh installed, never used service, where did the encrypted content come from? Perhaps out of the box item!
Perhaps this was asked before but I can't find a whole lot on this, so I would appreciate some help.
Our architecture is as follows: Win 7 desktop on a domain with VS 2010. MS Sql server R2 on Win Server 2008 R2 Ent; SharePoint 2007 on Win 2003; SharePoint 2010 on Win 2008 R2 Ent; Visual Sourcesafe on yet another separate Win Server 2008 R2 Ent server. On this server I have just installed TFS and was running Advanced Config Wizard.
As I'm new to TFS all my selected options are based on intuition and perhaps common sense but Reporting Services and SharePoint aren't working. With reporting services after I add my sql server name (and I've tried IP address and dns name) neither the Report Server URL nor Report Manager URL is populated. (Note: What do I need reporting services for anyway?)
So I've opted not to use reporting services, which as I said, I don't know what is the benefit of it.
Next, in the SharePoint configuration, I wanted to use the existing SharePoint farm which is installed on a separate servers. Testing the Site and Administration URLs would throw an error: "The following site could not be accessed. ... Either ... not installed the Team Foundation Server Extensions, or Firewall... "
I suspect it is not the firewall so then the TFS Extensions. Having search that topic as well seems to point back to the TFS's configuration, so I'm a completely at a loss.
Any ideas?
Thanks,
Risho
/posted from a smartphone since employer blocks this site/
Edited: I was looking at this article http://msdn.microsoft.com/library/dd631915.aspx but I don't have the options listed in the step-by-step solution. TFS Admin Console has this: Top tear - server name, below is Application Tear then Proxy Server, build Configuration and Logs. Expanding Application Tear shows Team Project Collections, SharePoint Web Applications, Reporting, and Lab Management.
You have to configure the SharePoint extensions on each SharePoint machine you wish to connect to TFS. Install TFS on whichever SharePoint machine (or both, if you plan to use both). In the configuration wizard, you should have the option to configure SharePoint Extensions. Once done, you should be able to re-run the readiness checks in the Advanced Wizard on your Application Tier machine.
We installed SP1 on our Team Foundation Server 2008 server. Everything seems fine after the install, except there is a red X on the Reports folder in the Team Explorer in Visual Studio. If we attempt to access the Reporting Services web site, we get a message that says that the "report server is unavailable". There were no errors during the installation.
The Reporting Services service started up fine and left no errors in the event log. We looked at the Reporting Services Configuration Tool and everything shows as OK. We tried restarting the RS service and rebooting the machine. Again, no errors but still no report availability.
The SQL Server instance where our data lives is up and running fine and we can query the OLAP cube and the relational side with no problem. All of our developer machines are already at VSTS 2008 SP1. Visual Studio is not installed on the server.
We looked at the logs files in the RS folder and the only errors that show are the ones that we get when we try to access the web site from IE, but that don't seem to contain any more info about the root cause.
Any help would be greatly appreciated. I'll post any updates on other things we try here.
UPDATE: There is a login error showing up the ReportServer(timestamp).log file. The login on the reporting services service is not the login that is showing up in this error, so I'm not yet sure what process is actually trying to make the connection to the db.
We got this resolved. It appears that the TFS 2008 SP1 install process decided to change the identity setting of application pool for the Reporting Services web site. To resolve we needed to:
Open Internet Information Server Manager
Go into Application Pools
Right click on the Reporting Services application pool
Click on the Identity tab
Change the account from NetworkService to our TFS domain account
Edit the rsreportserver.config located in "\Program Files\Microsoft SQL Server\MSSQL.1\Reporting
Change the "NT Authority\NetworkService" to "OurDomain\TFSDomainAccount"
Restart IIS
Hope this saves someone else some time.
Check the IIS application pools. My feeling is that reporting services doesn't play nice with other web applications (usually I've fixed this in the past by setting a seperate pool for the other applications).