Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

An error has occurred during report processing.Cannot create a connection to data source .For more information about this error navigate to the report server on... Expand / Collapse
Author
Message
Posted Tuesday, September 29, 2009 10:19 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, October 4, 2010 12:03 PM
Points: 13, Visits: 22
Hi,

An error has occurred during report processing. (rsProcessingAborted).Cannot create a connection to data source .(rsErrorOpeningConnection)For more information about this error navigate to the report server on the local server machine, or enable remote errors

Can I know that this is database accessablity problem or any thing other where database server was remote server.how to resolved this problem
Post #795277
Posted Wednesday, October 21, 2009 1:25 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Sunday, July 24, 2011 2:19 AM
Points: 10, Visits: 120
I have the same issue.

Does anyone have a resolution to this..? Please share.

An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'ExchangeTest'. (rsErrorOpeningConnection)
For more information about this error navigate to the report server on the local server machine, or enable remote errors
Post #806291
Posted Wednesday, October 21, 2009 5:25 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Wednesday, May 9, 2012 10:59 PM
Points: 229, Visits: 870
Run the same report in the server where the report sever is installed and get the exact error information.


-----------------------------------------------------------------------------------------------------------------------------------------------------------
Please feel free to let me know if you are not clear or I’ve misunderstood anything.

Thanks,
Arunkumar S P

Post #806385
Posted Tuesday, July 12, 2011 4:57 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Tuesday, July 12, 2011 5:17 AM
Points: 3, Visits: 13
How to trace the error. There is no log. It just says

Incorrect syntax near <stored procedure>
Post #1140214
Posted Wednesday, February 1, 2012 5:18 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, April 2, 2014 6:40 AM
Points: 11, Visits: 106
In my case deleting and deploying the same on report server fixed the issue.

Try it!!

-Syed
Post #1244985
Posted Friday, September 6, 2013 1:42 AM
Mr or Mrs. 500

Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500Mr or Mrs. 500

Group: General Forum Members
Last Login: Yesterday @ 1:02 AM
Points: 563, Visits: 1,175
Usually this means you've got something wrong with the data source that the report is connected to. Either you hadn't deployed the data source with the report or it was pointing to the wrong place (e.g. still to development when on live server) or it was in the wrong place ( difference between the default \Data Sources folder and \DataSources for example.) Or the username and password in the datasource is wrong. Redeploying often fixes it by deploying the report and its matching data source.

You can use report manager (usually http://servername/reports) to look at the data source associated with a report by looking at the report properties tab to find exactly which data source is being used (never assume anything!) and then go to that location and data source and check it points to the correct server and database and that the login and password is correct - redo the password for a SQL login.

The incorrect syntax error sounds like something wrong with the stored proc your report is calling. Make sure it works in Management Studio first.
Post #1492072
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse