December 19, 2008 at 12:47 am
Error message as below obtained on running SQL Reporting Services 2005 Report -
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source '******'. (rsErrorOpeningConnection)
Catastrophic failure
Detailed Error Message from Logs
w3wp!processing!b!19/12/2008-15:09:40:: e ERROR: Throwing Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source '******'., ;
Info: Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Cannot create a connection to data source '******'. ---> System.Data.OleDb.OleDbException: Catastrophic failure
The application Database and Analysis Services component is on a remote server on SQL Server 2005 SP1.
The Report Server is on SQL Server 2005 SP2, CU8 and Reporting Meta Data SQL Server also a remote server hosting SQL Server 2005 SP2, CU8.
Pls treat this as an urgent query and revert.
Regards,
Reshmi
December 19, 2008 at 6:47 am
Are you able to connect to the data source using the report user name and password from elsewhere? or from another application on the report server?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 20, 2008 at 2:04 pm
If the report works locally within BIDS, but not once it is deployed to Report Server then it most likely with the connection string settings. Are you specifying the credentials to use for the connection for the data source in Report Manager or are you trying to pass the current users credentials? Since these are on separate servers you would need Kerberos setup in order to pass the security token of the current user to the SSAS server.
----------------------------------------------------------------------------------------
Dan English - http://denglishbi.wordpress.com
December 21, 2008 at 7:58 pm
Jack,
The report uses Windows Authentication, and I am able to connect to the DB as well as Analysis Services thru Management Studio right when the error was occuring on the Report end.
Also, the error existed for around 2-3 hours, and then corrected by itself.
This has become a recurring issue in our application. Would like to hear how it can be corrected/find the root cause of the issue.
Thanks!
Regards,
Reshmi
December 21, 2008 at 8:07 pm
Dan,
The reports are windows authenticated and this is an intermittent error encountered.
The error corrected by itself in a couple of hours times.
Yes, Kerberos Authentication set up correctly and reports were working properly in this mode.
Thanks!
Regards,
Reshmi
December 21, 2008 at 8:40 pm
Do you have any other applications connecting to this data source? Are they having any issues? Any errors in the SQL Server or Windows error logs?
Jack Corbett
Consultant - Straight Path Solutions
Check out these links on how to get faster and more accurate answers:
Forum Etiquette: How to post data/code on a forum to get the best help
Need an Answer? Actually, No ... You Need a Question
December 21, 2008 at 8:50 pm
Hi..please try storing the server credentials for the concerned data source and also check the checkbox for Windows Authentication.
This should solve d issue...:)
Thanks,
Nirakj
December 21, 2008 at 8:55 pm
Jack,
Just one Reporting Application connecting to this data source and Cubes.
We also connect to the data source and Cubes through Excel (using Cubes Excel Add-In) and that was working perfectly at the time of error.
No errors captured on the SQL trace set up.
The Security Event Viewer just captured some failure audits for the Reporting Services Service Account.
- Reshmi
December 22, 2008 at 4:40 am
Do you possibly have the unattended execution setup in the Reporting Services Configuration Manager? If so trying disabling or removing this and restarting the service to see if that resolves your issue.
Are you seeing the correct end-user credentials being passed to the cube with the trace setup? Is the cube having the issues or is it reporting services? If you don't have a trace setup at the time you can also reference the FlightRecorderTrace files setup in your Log directory unless you have disabled this in the SSAS properties. You will only have the last couple of hours to information to go off of, but this might help also.
I would look at the Reporting Services logs to and try and see if you can find anything that might be helpful in those logs in regards to connectivity issues.
----------------------------------------------------------------------------------------
Dan English - http://denglishbi.wordpress.com
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply