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.
Related
I tried to deploy SSRS report . i created a report on visual studio .. and also i configured report server configuration manager
when i try to deploy report and open this URL
http://localhost/ReportServer
this shows an error
ERROR
"Reporting Services Error
The report server cannot open a connection to the report server database. The log on failed. (rsReportServerDatabaseLogonFailed) Get Online Help
The user name or password is incorrect. (Exception from HRESULT: 0x8007052E)
SQL Server Reporting Services"
whereas when i click reporting services from sql and connect then connected succesfuuly but after when i left click on server name then same error shows as above on sql
This error occurs when Reporting Services (the report server) cannot connect to the "ReportServer" mssql database, It is not a problem in your report but in the server configuration.
To solve it, run the tool "Reporting Services Configuration Manager" in the PC where MSSQL and SSRS are installed, and review everything is ok.
Specially in the Database tab.
The error "The report server cannot open a connection to the report server database. The log on failed" means that:
The database engine that the report server catalog database host is unaccessable.
The Reporting Services service account has insufficient permissions to the access the report server catalog database.
So, to fix the issue, please follow these steps:
Make sure we are able to connect to the database engine from the report server machine.
a) Ping the database engine server.
b) Try to connect to the database engine using SQL Server Mananger Studio(SSMS)(If we have.). Or, create a .UDL file, try to connect the server from this UDL.
Use the Reporting Services Configuration Manager(RSCM) to check the service account. If the report server is on the different server with the database engine, please use a domain account instead of the local account(Built-in account). Make sure the service account has permissions in the database engine.
Final, please check if the report server is configured correctly. We can easily check that by checking if we can open the Report Manager(http:///reports).
Besides, I would suggest you to go through each steps in the RSCM to make sure the configuration is all fine.
For more information, please see:
Configuring a Report Server Installation (Reporting Services in Native Mode): http://msdn.microsoft.com/en-us/library/ms159624.aspx
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 have a SQL Server Reporting Services(SSRS) report which works fine in Visual Studio 2015 report designer version 13.0,1100.286, but once deployed to a report server it keeps throwing the following error:
An error has occurred during report processing. (rsProcessingAborted)
Cannot create a connection to data source 'DummyDataSource'. (rsErrorOpeningConnection)
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
When I attempt to test the connection of the data source in SQL Server Report Builder, I get the same error:
And here is how I set the credentials for my data source. Note that 'myUser' can connect to database 'MyDatabase' in SQL Server Management Studio, and in addition the report works fine in Visual Studio report designer with the same credentials:
I have tried setting the report timeout to 1800 (from initial setting of "Use the system default setting"), but that didn't solve the problem:
I also tried setting the timeout for the data set in the report to 30 and 60 seconds, also with no success. It seems it can't connect to the database at all, because it fails on "Test Connection", before I even attempt to run the report itself.
Any idea why that's happening?
So after much digging and trying everything I came upon while googling this, the answer was the following: recently our IT people added a ton of new IPs to the database server and when a report (on the report server) attempted to connect to the database, it was enumerating all those IPs and was trying to connect to all of them, which resulted in it failing to connect to the right one and hence, the error above.
In order to address this, we added a new DNS entry, mapped solely to the IP address of the database and that finally fixed the issue.
So to summarize, my old connection string (that was trying to connect to all IPs) was:
Data Source=MyDatabase;Initial Catalog=DummyDataSource
The new DNS entry is: sql.MyDatabase.CompanyName.com
And finally, the new connection string that works fine is:
Data Source=sql.MyDatabase.CompanyName.com;Initial Catalog=DummyDataSource
I am using SQL SERVER 2008 R2 and I have a job which runs a DTS daily. When I try to execute the DTS package it works but when I try to use the scheduled job it returns the error:
Error:
-2147467259 (80004005); Provider Error: 18452 (4814) Error string: Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection. Error source: Microsoft OLE DB Provider for SQL Server Help file: Help context: 0. Process Exit Code 1. The step failed.
How can I solve that?
Follow the below steps:
1. Start > Programs > Microsoft SQL Server 2008 > SQL Server Management Studio.
2. In the Object Explorer, right-click the Server and select Properties.
3. In the Server Properties dialog box select the Security page.
4. Under Server authentication, select SQL Server and Windows Authentication Mode.
Then restart the server.
For further reference check this.
I stumbled across this issue and spent lot of time.
Finally found the issue is not in any user settings but my publish settings are overriding my connection string.
In web deploy settings there is an option to override your web.config connection string. Either untick that option or place the correct connection string.
For more details see this post https://dba.stackexchange.com/a/141243
I am placing this answer in case anyone gets stuck like me. :)
I'm Trying to created a shared Data source from a sql server that is not local. the host of SSRS is a sql server 2014 and the DB source is a sql server 2008 R2.
I'm getting the same error whatever I do, which is
"An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"
I know everything is correct because even though I get this error when I run the report, in MSSQL report builder when I create a dataset and go to query designer and run the query it actually runs without any issues.
furthermore also in report builder when I try to do a connection embedded in my report and when I'm in the connection builder (connection properties) and I test the connection from there it gives me "the test connection suceeded" however when I click ok, go back to the datasource properties, and click "test Connection" it fails and gives me the error above.
If I try to test a shared connection on the server it will fail too.
I've tried connecting in many different ways (using windows athentication (my user is admin on the server), SQL server authenticationm, promting, etc) but they all failed.
I've been at this for a while, the server is also accesed by a remote PHP server so I doubt there is any real issue on the SQL server. I've tried deactivating all of the firewalls I saw but I doubt it's a firewall issue since I"m able to do all these connections.
the issue was the port 1433 that didn't work between the SSRS server and the datasource server. however it did work between my computer and the sql server.
what was happening is that when I tested the connections, the first test was a quick test and went through my computer to test the connection thus it was sucessfull. when it did the real test it went through the SSRS server and it failed there.
the same logic applies when I did my requests, when I tested the dataset it worked because in report builder it went directly to the database through my computer, when I tried to run the report it went through the SSRS server and failed there.
so there is some issue with the firewall even though it is turned of on both servers it's the connection between the two that isn't working.