IBM Support

invalid username/password and "Authentication failed because the remote party has closed the transport stream" attempting to authenticate with Engineering Test Management (ETM) Excel Import Utility

Troubleshooting


Problem

Attempting to authenticate the Engineering Test Management (ETM) Excel Import Utility (formerly Rational Quality Manager (RQM) Excel Import Utility) to an ETM server configured with the TLSv1.2 protocol fails with an invalid username/password error and "Authentication failed because the remote party has closed the transport stream" in the ETM Excel Import Utility Mso2Rqm_Debug.log

Symptom

Attempting to authenticate the Engineering Test Management (ETM) Excel Import Utility (formerly Rational Quality Manager (RQM) Excel Import) to an ETM server configured with TLSv1.2 fails with an invalid username/password error and "Authentication failed because the remote party has closed the transport stream" in the ETM Excel Import Utility Mso2Rqm_Debug.log
Below is a full stack trace from the ETM Excel Import Utility Mso2Rqm_Debug.log. The Mso2Rqm_Debug.log. log can be found at C:\Users\<USERS>\AppData\Roaming\Mso2Rqm

4/14/2021 8:10:09 PM: ERROR: <Unknown Caller Context>: failed to get from server: Unable to connect to the remote server
4/14/2021 8:10:09 PM: INFO: <Unknown Caller Context>: Send Status: ConnectFailure
4/14/2021 8:17:49 PM: INFO: <Unknown Caller Context>: RQMConnector: Logout - Error logging out:https://itprojmgmt.penfed.org:9443/qm
4/14/2021 8:17:49 PM: INFO: <Unknown Caller Context>: The underlying connection was closed: An unexpected error occurred on a send.
4/14/2021 8:17:49 PM: EXCEPTION: : The underlying connection was closed: An unexpected error occurred on a send.
4/14/2021 8:17:49 PM: at System.Net.HttpWebRequest.GetResponse()
at Mso2Rqm_Common.RQMConnector.LogOut(String url)
4/14/2021 8:17:49 PM: EXCEPTION: : Authentication failed because the remote party has closed the transport stream.
4/14/2021 8:17:49 PM: at System.Net.Security.SslState.StartReadFrame(Byte[] buffer, Int32 readBytes, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
at System.Net.TlsStream.CallProcessAuthentication(Object state)
at System.Threading.ExecutionContext.runTryCode(Object userData)
at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.ConnectStream.WriteHeaders(Boolean async)

Document Location

Worldwide

[{"Type":"SW","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSUVV6","label":"IBM Engineering Test Management"},"ARM Category":[{"code":"a8m0z0000001j1CAAQ","label":"Test Management-\u003EUtilities-\u003EETMExcelWordImporter Utility"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
12 August 2022

UID

ibm16451645

Page Feedback