We have run for the last 7 years without issue against the same oracle 11g database using SSRS 2008 with an OracleClient data source. As soon as we upgraded to SSRS 2016 and had to switch to ODP.NET, we are randomly getting ORA-12571 errors. It may be important to note that when the error does show up, users can hit refresh and it runs just fine.
The error in the reporting services log looks like this:
"Microsoft.ReportingServices.ReportProcessing.ProcessingAbortedException: An error has occurred during report processing. ---> Microsoft.ReportingServices.ReportProcessing.ReportProcessingException: Query execution failed for dataset 'DataSetOrders'. ---> Oracle.ManagedDataAccess.Client.OracleException: Oracle error ORA-12571 encountered ---> OracleInternal.Network.NetworkException: Oracle error ORA-12571 encountered ---> System.Net.Sockets.SocketException: An established connection was aborted by the software in your host machine"
The error in the browser looks like this:
No loss in performance...this did the trick.
MIN POOL SIZE=0
Related
We have a large SQL Server database that uses agent jobs to insert records of outgoing messages into a MySQL table on another server that is a open queue. Problem is when we get to records that are more than 5000, it starts to lose records. So 7800 transferred, only 5500 will actually be inserted. But the job reports that it successfully ran.
The jobs run a dots file that defines the database connections via the servers ODBC. What's weird is we never had any issues before and I suspect its because of the earlier MySQL drivers. We had to use new ones because the old wouldn't install on the new server platforms.
Here is the error we're getting:
Executed as user: NT Service\SQLSERVERAGENT. Microsoft (R) SQL Server Execute Package Utility Version 11.0.5058.0 for 64-bit Copyright (C) Microsoft Corporation. All rights reserved. Started: 2:58:45 PM Error: 2022-02-18 14:59:46.59 Code: 0xC002F210 Source: Transfer to MySQL Execute SQL Task Description: Executing the query "INSERT INTO OPENQUERY(TABLE, 'SELECT sql_id..." failed with the following error: "Query timeout expired". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 2:58:45 PM Finished: 2:59:46 PM Elapsed: 60.778 seconds. The package execution failed. The step failed.
If it ever fails it happens right at the 60sec mark.
Does anyone have any idea why this would happen? Are there settings that need to be altered to ensure the transfer completes?
Please let me know what I can provide to assist.
Thank you all!!!
I have a report that is connecting to a new server.
When I run the report in Visual Studio, it runs fine but when I deploy the report, the new data source is getting an error:
A network-related or instance-specific error occurred while
establishing a connection to SQL Server. The server was not found or
was not accessible. Verify that the instance name is correct and that
SQL Server is configured to allow remote connections. (provider: Named
Pipes Provider, error: 40 - Could not open a connection to SQL Server)
The Type is MS SQL Server and the Connection String is basic (Data Source=;Initial Catalog=). When I hit Test, it takes about a minute to come up with the error. I also get the error whether using stored credentials or Windows Integrated.
I have recreated the data source by hand without any difference.
I have went through the Microsoft troubleshooting without success. I have numerous other similar data sources but have never had this issue.
MS Docs: Troubleshoot connecting to the SQL Server Database Engine
Don't know what else to try. Any suggestions to fix this?
SSRS 2015 - SQL Server 13.0.5820.21
i am trying to run few reports(MS Reporting server) that can be big if i set time period ALL, but also those report are getting error code 800708CA in RS log if i just set small amount of data.
Error code is:
ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.ClosingRegisteredStreamException:
,
Microsoft.ReportingServices.Diagnostics.Utilities.ClosingRegisteredStreamException:
An error occurred closing a registered stream. --->
Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerHttpRuntimeClientDisconnectionException:
A client has disconnected from the Report Server Web service
application domain ReportServer_SSRS_0-3-131959013894837810. No
corrective action is required. An error code has been submitted to
ASP.NET to release the connection. The error code is 800708CA. --->
System.Runtime.InteropServices.COMException: This network connection
does not exist. (Exception from HRESULT: 0x800708CA)
What can i do to solve this error. Time out in RS is set to 1800 s, that is enough. Running the same report in MS SQL Studio in done in coupled of seconds.
My SSRS runs snapshot in the morning. I noticed some of the reports are not snapshoting once in a while.
I found following error which is random daily for the difrerent report.
The report server cannot open a connection to the report server database.
library!WindowsService_28!1d168!02/23/2018-05:47:42:: e ERROR: Throwing Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: , Microsoft.ReportingServices.Library.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> System.Data.SqlClient.SqlException: Connection Timeout Expired. The timeout period elapsed during the post-login phase. The connection could have timed out while waiting for server to complete the login process and respond; Or it could have timed out while attempting to create multiple active connections. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=0; handshake=11; [Login] initialization=0; authentication=0; [Post-Login] complete=16573; ---> System.ComponentModel.Win32Exception: The wait operation timed out
--- End of inner exception stack trace ---
Thank you,
Kalpesh
Possible reasons could be a network disconnection, blocking due to a firewall or antivirus or possible overload of the database server. What time does it occur? What processes are active at that time? Does the task manager at the database server show any performance flags? Does it happen everyday? Since when are you facing this issue? Was there a software update in the interim? More information will be required to troubleshoot.
while runnig the ssis package i'm calling sp in the ADO.net source,but getting this error
Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.I have set the command timeout to 0(infinite time),but still getting the error.The sp is working fine in sql server and taking approx 31 seconds for executing it,but in ssis its throwing error..please help me on this.Thanks in advance.
Check out this bug report - there is a sp in the SSISDB database in SQL Server 2012 causing packages to time out before they start running. I had error message "Failed to execute IS server package because of error 0x80131904" and "Description: The operation failed because the execution timed out" when calling multiple (more than 10) packages from my scheduling tool via DTExec. Please vote for the issue on the connect site so that MS can release an official fix.
Today, I was experiencing the same error while using the ADO Net Source, my sp works fine on the SSMS, but fails in the package, while In the package, it errors our with a long laundry list of errors, but basically it is timing out.
Solution is Right click on the ADO Net Source - Show Advanced Editor - Component Properties - Custom Properties - CommandTimeout - Increase the time here
I had the same problem in SSAS.
The way I sorted this out was extending the client and server time out settings.
you can see more details in the link below:
routine to backup ssas databases fails with: The XML for Analysis request timed out before it was completed