- Translation jobs submitted previously displays status "Error Retrieving" - After resubmitting, jobs gives same status. - From the Notifications tab of a failing job, below stacktrace can be seen The underlying connection was closed: An unexpected error occurred on a receive. at System.Web.Services.Protocols.WebClientProtocol.GetWebResponse(WebRequest request) at Microsoft.Web.Services2.WebServicesClientProtocol.GetWebResponse(WebRequest request) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at Com.Idiominc.Webservices.Data.WSContextService.loginUser(String userName, String password) at Com.Idiominc.Webservices.Client.WSContext.loginUser(String userName, String password) at Com.Idiominc.Webservices.Client.WSContext.login(String userName, String password) at Com.Idiominc.Webservices.Client.WSContext..ctor(String user, String password, String serverURL) at Tridion.TranslationManager.DomainModel.TranslationSystems.WorldServerConfiguration.GetWSContext() at Tridion.TranslationManager.DomainModel.TranslationSystems.WorldServerConfiguration.GetWSWorkflowManager() at Tridion.TranslationManager.DomainModel.TranslationSystems.WorldServerConfiguration.get_WSWorkflowManager() at Tridion.TranslationManager.DomainModel.TranslationSystems.WorldServerConfiguration.InitializeConfiguration() at Tridion.TranslationManager.DomainModel.TranslationSystems.WorldServerConfiguration..ctor(String id, UserContext userContext) at Tridion.TranslationManager.DomainModel.TranslationSystems.TranslationSystemConfiguration.GetTranslationSystemConfiguration (String translationSystemConfigurationId, UserContext userContext) at Tridion.TranslationManager.DomainModel.Service.RetrieveFromTranslationTask.Process() ------ Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.TlsStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.PooledStream.Read(Byte[] buffer, Int32 offset, Int32 size) at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead) An existing connection was forcibly closed by the remote host at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)- Worldserver environment had earlier encountered an outage due to Java heap space. |
Issue resolved after restarting the Translation Manager service on Tridion CM environment. Note that restarting the Translation Manager service does not affect inflight jobs, as this is just polling. If issue persists after restarting the Translation Manager service, configure Translation Manager debug logging as outlined in below KB article and retry retrieving job again. Review the debug log and submit a ticket to SDL Support if assistance is needed. How to enable 'Verbose' logging for SDL Translation Manager |