SSRS 2005 : I am writing RDL file in code itself & binding to a custom datasource(DATASET extension) & rendering using report viewer which is working fine. Now I have upgraded the Reporting server to SSRS 2008 R2. When executing the same codebase
(RDL & Dataset) it is throwing error on report viewer.
Error: An error has occurred during report processing query execution failed for dataset 'DataSet1'.
First, did you also upgrade the SQL database to 2008 R2 as well?
If so, try the following to update the report schema:
Open the .rdl in Report Builder 3.0. Expand Data Sources, select your Data Source, and switch to Use a connection embedded in my report
Build a new connection string to your SQL server and database, and ensure that you use Windows Authentication. I'm not sure why, but SQL Authentication errors out sporadically.
Test Connection and press OK.
For each of your Datasets, open them up and Refresh Fields and press OK.
Save the report.
I have experienced this in the past. This will essentially force a schema update of the report. It's a bit of a dirty workaround, but I've found it to be successful. If one of your datasets fails to refresh, you'll receive an error explaining what's wrong with the underlying SQL.
Related
Is it possible to use SSRS - SQL Server Reporting Services for Progress OpenEdge database?
I'm able to built a report via Microsoft SQL report builder however unable to connect database via ODBC when publishing .rdl file to SSRS
Below is screeshot (first) how I have connected to database through odbc and (second & third) other 2 connecting from report builder which works fine.
Report builder and Sql report server are on same machine.
However can't see Progress OpenEdge driver on New data Source for SSRS.
Also posted error that i get for .rdl report file uploaded to SSRS but works on fine on same machine report builder.
Please check below,
This is what i get,
I'm unable to generate a report from the web based interface (Report Manager). The same report in my Visual Studio project works perfectly.
The error which appear when trying to generate the report from the web is
"Cannot create a connection to data source"
The log file error is the fallowing
Cannot get edition information from catalog server.
The report data is retreived from an SQL Azure database.
How come the report can work inside my Visual Studio project but no more once deployed?
I've tried both SQL Server 2012 and SQL Server 2008 on fresh machines and both gives the same result.
Thanks,
After a half day of troubleshooting this issue, I discovered it was because the edition of SSRS I am using does not support Azure SQL Databases as a data source.
I am using 2008 Express Advanced Edition. It appears Standard or above is required for this.
See this article for more information:
http://www.sqlservercentral.com/blogs/sqltact/2016/09/25/sql-ssrs-express-edition-cannot-connect-to-azure-sql-databases/
I have a ssrs report which uses a shared dataset and a shared datasource. I can preview it without problems in my local workspace. Now I have copied the report to a remote computer where I modified the connection properties of the datasource. I cannot preview the report on this system, getting an error:
"error has occurred during report processing. execution error in the shared dataset. Cannot create a connection with datasource of shared dataset." (my translation, message is german)
I can create a connection to the server ("test connection" in datasource is successful) and access the data of the dataset in the query designer. What could be the problem here?
The issue is on the remote computer where the drivers are not installed or installed incorrectly.
I have had issues where the server is not set up but my pc is. As such my query designer worked but when published and run from the server it didn't.
I am new to SSRS. I have developed some reports using BIDS using SQL Server Reporting Services(SSRS) when I run them from my machine reports are running ok. But there are not appearing from SQL Server Reporting Services(SSRS). Even when I open SQL Server Reporting Services(SSRS) in a web broswer
I can not see the reports on SSRS. How can I ensure that these reports are appearing or can be seen on SQL Server Reporting Services(SSRS) URL?
Please help.
Have you deployed them?
Right-Click on the report and go to Deploy
or
In the Build menu select "Deploy projectname"
You may have to set the project properties first for TargetServerURL to something like
http://SSRSserver/reportserver
They can be found in the Project menu under "projectname Properties"
There are two options to deploy your reports on server -
1] You can directly deploy it from your VS by right clicking on your report & selecting deploy option, here you need to mention target server -
http://[server name]/ReportServer
2] If you are able to access report server then web browser provide one option to upload your reports. So you can upload your report directly on report server (.rdl file). Here you need to set proper connnection string & permission rights to access the report.
Hope this will help you..!!
I have SSRS Report being accessed from a Report Server. Is there any way I can give an error message of my own, if my report fails to open there?
I can't think of any way to capture RS errors if you are using SSRS report manager. On the other hand, if you are using the report viewer control, you may have a higher chance of capturing the errors. The same goes if you use custom dataset extension for report rendering.
Browse to Report Manager folder. For SSRS 2005, its typical location
is
DRIVE:\Program Files\Microsoft SQL Server\MSSQL.x\Reporting
Services\ReportManager, where x is the instance; for SSRS 2008 and
SSRS 2008 R2, DRIVE:\Program Files\Microsoft SQL
Server\MSRS10.SSRS\Reporting Services\ReportManager.
Make a copy of the existing Web.config as backup
Open Web.config in a text editor, or in Visual Studio to get
Intellisense support
Under the section, locate the section
Modify the existing section, or insert a new one, with
the appropriate settings
Restart the Report Server
Custom error messages for SSRS 2008 have a look here