Cannot create a connection to datasource 'DataSource'. (rsErrorOpeningConnection)
I've been chasing my tail on this issue for a while, and I figured I would see if I could find any answers. None of the 'solutions' I've found work for my setup. I'm new to this, so here is the setup: SERVER1 - Has SharePoint 2007 & SQL 2008 Reporting Services SERVER2 - Has the data warehouse, report databases and cubes (SQL 2008 cluster, thus I couldn't load reporting services on it) As myself, domain admin, I have no issues running any reports from anywhere. All works. As a user, they get the message: An error has occurred during report processing. (rsProcessingAborted) Cannot create a connection to data source 'DataSource'. (rsErrorOpeningConnection) The connection either timed out or was lost. Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. An existing connection was forcibly closed by the remote host To be more specific, the user only gets this message when running a report off of the cubes, they can successfully launch reports from the data warehouse data source (even though it's on the same server as the cubes). To make things more complicated (or maybe not), if the user directly logs on to SERVER1 and runs the reports, they run fine. All on same domain. To be clear, the user is a local machine admin. If I login on SERVER1 and authenticate in SharePoint as that user, it fails with the above error. Likely seems to be permissions related somewhere... Thoughts, anyone?
October 4th, 2010 9:07pm
Sometimes thinking outloud helps... I changed the DataSource credentials from windows authentication to stored credentials of the domain account used for reporting services and it is working (so far). I guess I don't know what best practices would be for prod environment (still in dev).
October 4th, 2010 9:13pm
Hi M_Buzz, It seems to be double hop issue in your case. Firstly, go through http://blogs.technet.com/b/askds/archive/2008/06/13/understanding-kerberos-double-hop.aspx to understand the double hop, then try to enable kerberos autentication in your reporting services environment. By the way, using stored credential is a workaround to solve the double hop issue. thanks, Jerry
October 8th, 2010 10:43am