We have a new SSRS 2019 Server. I navigate to the SSRS Report Manager web page, click New and select a Paginated Report which opens Report Builder. I can create a Data Source connecting to another MS SQL Server 2016 database successfully - I'm embedding the data source not using a shared one. I can create a dataset (select * from table) and if I go into the query designer and click the red exclamation point I get results as expected. I add a table to the report, add some of the fields from the query and when I run it I get the error:
Cannot create a connection to the data source.
In the lower left of Report Builder it tells me what report server I'm currently connected to and if I disconnect THEN run it again it works fine.
Any suggestions? I'm positive it's something to do with our new report server but I'm confused why I can connect and run the query in the query designer but it won't connect just running the report. Thanks much!
The connection is working from the machine you are designing on, but not from the Report Server. When Report Builder is connected to the server, it tries running the report using the server version of the connection which is why you get this behavior.
If you look closely, there are two different Test Connection buttons. One in the Connection Properties and one in the Data Source Properties. One of these works, but the other won't (if you are connected to the Report Server).
So it comes down to standard connection troubleshooting on the server: check firewalls, drivers, etc.
Related
I've recently started using Azure Data Studio (Formerly SQL Operations Studio) instead of SSMS. I can't see an obvious way to tell which query windows relate to which connections.
Example:
I have 2 DB servers, and each has the same DB
server1.db1
server2.db1
Let's say I connect to both and open a query for each and run it. Then I get confused and cant remember which connection is for window SQLQuery_1 and which is for SQLQuery_2.
I can see at the top of each window that they are connected to the DB "db1", but I don't know if it is for server1 or server2. SSMS show's the server name.
Is there a way to make the server visible for a query window?
As in the comments, it's shown in the bottom right hand side of the screen:
For example, in this picture, you can see I'm connected to the server qebui and the database Sandbox.
I'm having an issue with an SSRS report using SQL Server Authentication.
I'm creating the report in VS2017 (SSDT), latest update 05/11/2018.
Creating a pretty basic report with 2 data sources. The data sources appear to be valid and passes test.
Test Connection:
When I attempt to preview the report SSRS throws the obtuse error
An error occurred during local report processing
By changing the credentials from SQL Server Authentication to Windows Authentication I can preview the report just fine:
There are no reported login failures in the logs of the target SQL server so it would appear that the report is failing prior to the login.
I'm a little befuddled and appreciate any insights the community could provide.
Convert your data set to shared data set. I also faced the same problem when i upgraded my ssdt.
I am using some SSRS reports in some applications that I developed using Visual Studio.
Recently I noticed that my report server url is giving me the following error message.
"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
For more information about this error navigate to the report server on the local server machine, or enable remote errors"
I can't go delete the encryption details and try to set the data connections again as many posts suggest because there are a lot of SSRS reports in this server and I don't know the username and passwords to connect to all databases.
Further, I noticed the following.
My SSRS home page displays this error message
Some applications using reports hosted in this report server displays the same message
Other few applications using reports hosted in this report server works as expected without any error messages
Where should I look and what should I do about this? Any help is much appreciated.
Thanks in advance.
Replications Steps
I have deploy a report onto Report Manager 2012 and can't seem to run it . It gives me the following error. I checked the connection the the datasource in Report manager and works ok.
I have also set up an execution account on Reporting Services configuration manager.
Error
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DataSource1'.
(rsErrorOpeningConnection) The ConnectionString property has not been
initialized.
Does anyone know how to fix this ?
The execution account is my windows nt account . The datasoource is on another server. Reports works fine in Sql Server data tools 2012.
Solved . Made the datasources and datasets shared and it now works.
Sometimes when trying to setup web.config and connectionstrings.config settings for our .NET applications we get DB errors. Many times due to wrong connection info in the config files. Sometimes we need to find out if the app/web server can even see the DB server.
How would you connect to your DB server to test connectivity before getting the app to run?
The answer that I have found is this:
There's a utility built into windows that will test SQL connections.
Here's a simple way to use it.
Create an empty file called anything.udl and double click on it. Click
the Provider tab, and select "Microsoft OLE DB Provider for SQL
Server". Then click the connection tab, populate your connection
details, and hit the "Test Connection" button.
Credit goes to this poster/forum about 3 posts down they post the above information.
So steps to do so are the following:
On your app/web server create a blank file called test.udl
Double-click this file and at least with Windows Server 2008 R2 it will open up a Data Link Properties window.
Insert your connection string information and hit the test button and it should connection successfully. If it doesn't then make sure your DB info is correct and if it is then your server might not be able to see the SQL server.
Hope this is helpful to others!