Just wanted to see if anyone else was having issues printing reports? Seems similar to the issue we had a couple of weeks ago. Getting this in the System Monitor:
—> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host..
—> System.Net.Sockets.SocketException (10054): An existing connection was forcibly closed by the remote host.
I already logged a ticket, but curious to see if others are also having issues right now?
Yes, same issue here! We are logging a case right now, but it seems to be about 90% of all our reports that are ending with this “forcibly closed” message.
: Connection Timeout Expired. The timeout period elapsed while attempting to consume the pre-login handshake acknowledgement. This could be because the pre-login handshake failed or the server was unable to respond back in time. The duration spent while attempting to connect to this server was - [Pre-Login] initialization=12458; handshake=2569; —> System.ComponentModel.Win32Exception: The wait operation timed out
Program Ice.Services.Lib.RunTask when executing task 3539558 raised an unexpected exception with the following message: RunTask:
Ice.Core.SsrsReporting.SsrsCaller.SsrsException: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.
It seems to have calmed down for us over the past few hours, but that might just be where people have left on a Friday afternoon. Still receiving errors as recent as 10 minutes ago. My EpicCare response was that might be resolved by the end of February.
They gave you an estimated resolution date? Mine just told me they see printing is working again and then to confirm (which I did have to reach back out as other people were continuing to have issues)
Below is the response I received from CS0005291944
Hello Billy,
I apologize for the delay in following up with you on this case.
The following error: An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database.
This issue is related to Problem PRB0304935 / Developer Ticket ERPS-296644
Other than manually reprinting any report that results in an ERROR status, Support is not aware of any additional workarounds to this concern.
Development has concluded that one of the main reasons for the issues is due to recent Kinetic reporting framework changes that are intended to make sure a customer’s custom report is correctly deployed in Reporting Services. These changes are having an unintended consequence of Reporting Services being overloaded.
Development is working on code changes and unofficially expect to have something checked into code by the end of February. I will provide you with all updates as they are received.
Let me know if you have further questions.
Kind regards,
Linda
This particular error is different, but the thread is for Reporting Server Issues and has multiple different errors (including the listed forcibly closed by the remote host..) that we have received over the past week and a half.
