An Unexpected Error Occurred On A Send Reporting Services
Contents |
(Русский)ישראל (עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) HomeLibraryLearnDownloadsTroubleshootingCommunityForums Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered by: The underlying connection was closed: An an unexpected error occurred on a send vmware unexpected error occurred on a send. SQL Server > SQL Server vsphere client unexpected error occurred on a send Reporting Services, Power View Question 0 Sign in to vote Fala ae galera. tive problemas ao publicar the underlying connection was closed an unexpected error occurred on a send. ssrs meu primeiro report, exibe o seguinte erro:The underlying connection was closed: An unexpected error occurred on a send. Configurações IIS Friday, January 31, 2014 2:08 PM Reply the underlying connection was closed an unexpected error occurred on a send iis | Quote Answers 4 Sign in to vote Hello, Based on the error message, the issue may be related to the “SecureConnectionLevel” in the RSReportServer.config file. When we use HTTP protocol, the value of the “SecureConnectionLevel” attribute should be 0. Usually, we change the value to “1” or “2” only when we configure the Report Server for
The Underlying Connection Was Closed An Unexpected Error Occurred On A Send Powershell
Secure Sockets Layer (SSL) connections. Reference: http://msdn.microsoft.com/en-us/library/ms157273(v=sql.105).aspx Please refer to the following steps try to resolve the issue: 1.Use Notepad to open the RSReportServer.config. By default, in SSRS 2012, it is located in: C:\Program Files\Microsoft SQL Server\MSRS11.MSSQLSERVER\Reporting Services\ReportServer (Note: Please backup the file before modify it.) 2.Search for “SecureConnectionLevel” and make sure its value is set to 0. It looks like this:
open report manager via the browser. This is because of the invalid configuration in reportserver.config file. The default value of the key SecureConnectionLevel has been set as 2, which requires SSL configuration. If you do not use SSL, make
Ssrs An Unexpected Error Occurred While Compiling Expressions
it as 0, making service least secure. Refer BOL for more info. Posted by Dinesh Priyankara the underlying connection was closed an unexpected error occurred on a receive. ssrs at 6:16 PM Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest Learnt: 11 comments: Quang said... have you give this a try as it the underlying connection was closed an unexpected error occurred on a send. ssrs 2012 help me. http://connectionstringexamples.com/article.php?story=underlying-connection-closed March 26, 2009 at 12:48 AM StPatrick said... Thanks! October 25, 2009 at 8:13 AM Karim said... you are the best. spent half a day on it. thanks a lot for the post... December 2, 2010 https://social.msdn.microsoft.com/Forums/sqlserver/en-US/1543a3cb-5d31-49ed-bc40-a01815ab70a3/the-underlying-connection-was-closed-an-unexpected-error-occurred-on-a-send?forum=sqlreportingservices at 1:34 PM Lakshmi said... Thanks a lot it is worked for me also. October 7, 2012 at 9:17 PM Younus Mohammed said... I am also facing same error. I dont find any solution here, can any one among you guide me on this part? February 20, 2013 at 10:49 PM Andrey Paltusov said... Thanks a lot! April 17, 2013 at 12:34 AM Doug Purnell said... Thanks for this post! July 10, 2013 at 5:09 AM Chandra Sekhar http://dinesql.blogspot.com/2009/01/reporting-services-2008-error.html Bodapati said... Hi, I have the same problem now on WIN8, SSRS 2008. But my setting is already 0 as follows and its giving the same errorError:The underlying connection was closed: The connection was closed unexpectedlymy config setting:Please advice..Chandra January 12, 2014 at 9:50 PM atkjedi said... thanks! April 22, 2014 at 10:00 PM atkjedi said... thanks! April 22, 2014 at 10:01 PM Raghwendra Mishra said... Hi Dinesh,M getting same error while doing anything on server like ""Editing data-source, generating report.Can you please help me with this ? June 1, 2015 at 2:00 AM Post a Comment Newer Post Older Post Home Subscribe to: Post Comments (Atom) Search This Blog Loading... About Me Dinesh Priyankara Colombo, Sri Lanka Dinesh Priyankara (MSc IT) is a SQL Server MVP in Sri Lanka with 14 years experience in various aspects of database technologies. Currently he is stationed as a Senior Architect - Specialist at Virtusa. He teaches, consults and runs training programs for various institutes/companies in Sri Lanka and he a co-founders of SQL Server Sri Lanka User Group (SSSLUG): http://www.meetup.com/ssslug/, https://www.facebook.com/groups/sqlserveruniverse/ View my complete profile Pageviews last month Follow by Email Top 50 sql server blogs Top 50 sql server blogs Blog Archive ► 2016 (112) ► October (1) ► September (25) ► August (9) ► July (23) ► May (24) ► April (12) ► February (1) ► January (17) ► 2015 (200) ► December
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta http://stackoverflow.com/questions/981573/why-cant-i-force-ssl-for-sql-server-reporting-services Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, unexpected error helping each other. Join them; it only takes a minute: Sign up Why can't I force SSL for Sql Server Reporting Services? up vote 4 down vote favorite 1 I am trying to setup SSRS 2008 on Windows Server 2008. It seems to work as expected when I access the web interface through HTTP, but when using unexpected error occurred HTTPS the following error is what I get: "The underlying connection was closed: An unexpected error occurred on a send." From a look at the log files, it is revealed that the inner exception is "System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host". This makes me think, that the error occurs during a service call from the Report Manager to the web service. I have configured both the web service and the Report Manager with an SSL-binding on a non-default port (8091), using a certificate signed using my own CA certificate. The server certificate is installed in (and used by) IIS7, and the CA certificate is added to "Trusted Root Certificate Authorities" on the "Local Computer" certificate store. Searching the net for the specific error message(s) gives me a lot of information on how to deal with the problem, if the client application is my own .NET application. The most prevalent solution seems to be about setting the property "ServicePointManager.SecurityProtocol" to "SecurityProtocolType.Ssl3", but I guess t