Error message "The underlying connection was closed: An unexpected error occurred on a send" when trying to run RSA Authentication Manager 8.1 SDK .NET C# sample on Windows 2003
Originally Published: 2016-06-16
Last Modified: 2023-10-06
Article Number
Applies To
RSA Product/Service Type: Authentication Manager SDK
RSA Version/Condition: 8.1
Platform: Windows Server 2003
Issue
Error: The underlying connection was closed: An unexpected error occurred on a send.
at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at com.rsa.webservice.CommandServerService.executeCommand(String in0, TargetableCommand in1) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\generated-csharp-dotnet20\com.rsa.webservice.cs:line 160
at com.rsa.command.SOAPCommandTarget.executeCommand(TargetableCommand command) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\shared-csharp\CommandHelper.cs:line 478
at com.rsa.command.SOAPCommandTarget.Login(String name, String password, String method) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\shared-csharp\CommandHelper.cs:line 581
at com.rsa.command.SOAPCommandTarget.Login(String name, String password) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\shared-csharp\CommandHelper.cs:line 553
at com.rsa.samples.admin.AdminAPIDemos.Main(String[] args)
at System.Web.Services.Protocols.HttpWebClientProtocol.GetWebResponse(WebRequest request)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at com.rsa.webservice.CommandServerService.executeCommand(String in0, TargetableCommand in1) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\generated-csharp-dotnet20\com.rsa.webservice.cs:line 160
at com.rsa.command.SOAPCommandTarget.executeCommand(TargetableCommand command) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\shared-csharp\CommandHelper.cs:line 478
at com.rsa.command.SOAPCommandTarget.Login(String name, String password, String method) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\shared-csharp\CommandHelper.cs:line 581
at com.rsa.command.SOAPCommandTarget.Login(String name, String password) in c:\jenkins\workspace\am-sdk-build\am\integration\rsaws\target\shared-csharp\CommandHelper.cs:line 553
at com.rsa.samples.admin.AdminAPIDemos.Main(String[] args)
Cause
The SSL handshake is failing because Windows 2003 does not support any of the ciphers used by the Authentication Manager server on port 7002.
Resolution
Related Articles
RSA Identity Governance and Lifecycle fails to start after patching with error "Patching has failed" and "Closed Connection" Number of Views RSA Access Manger error message 'This stream has been closed'. Number of Views Export and Import Closed Requests Number of Views AAoP in websphere and DB2 deleting users could throw an error 'result set is closed. ERRORCODE=-4470' Number of Views Diagnostics and System Data Gathering Feature in RSA Identity Governance & Lifecycle Number of Views
Trending Articles
How to manipulate imported RSA SecurID Software Token(s) on an iPhone or iPad device Reporting on RSA Authentication Manager 8.x users with On-Demand Token, a fixed passcode or a hardware/software token assi… How to Download OTP Token Seed Files from myRSA Anomalix idGenius - SAML Relying Party Configuration - RSA Ready Implementation Guide RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?
