Timeout can be only be set to 'System.Threading.Timeout.Infinite' or a value > 0

Issue

When the KTA Core Worker tries to poll MC, the blue arrow remains beside the message indefinitely.  Subsequently, the message is never ingested into KTA.

The below error will be written in the application event log.

Message : The underlying connection was closed: An unexpected error occurred on a receive.
Stack Trace :    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 Agility.Server.Core.MessageConnectorService.tsl1Service.ConfirmMessage(ConfirmMessage ConfirmMessage1)
   at Agility.Server.Core.MessageConnector.MessageConnectorImporter.ConfirmMessage(tsl1Service service, ViewMessageResponse response, MessageImportInterior messageImport, ConfirmMessageStatus status, String statusMessage)
   at Agility.Server.Core.MessageConnector.MessageConnectorImporter.ProcessMessage(MessageImport messageImport)
   at Agility.Server.Core.Worker.WorkerThreads.JobThread.ProcessMessageConnector()

    Inner Exception
    ---------------
    Message : Timeout can be only be set to 'System.Threading.Timeout.Infinite' or a value > 0.
    Stack Trace :    at System.Net.Sockets.NetworkStream.set_ReadTimeout(Int32 value)
       at System.Net.Connection.SyncRead(HttpWebRequest request, Boolean userRetrievedStream, Boolean probeRead)

NOTE: If HTTPS is enabled in MC, then the above error will not be thrown.  Instead the below error will occur.

Message : The request was aborted: Could not create SSL/TLS secure channel.
Stack Trace :    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 Agility.Server.Core.MessageConnectorService.tsl1Service.ConfirmMessage(ConfirmMessage ConfirmMessage1)
   at Agility.Server.Core.MessageConnector.MessageConnectorImporter.ConfirmMessage(tsl1Service service, ViewMessageResponse response, MessageImportInterior messageImport, ConfirmMessageStatus status, String statusMessage)
   at Agility.Server.Core.MessageConnector.MessageConnectorImporter.ProcessMessage(MessageImport messageImport)
   at Agility.Server.Core.Worker.WorkerThreads.JobThread.ProcessMessageConnector()

Cause

This is caused by the fact the Message Connector Service Timeout setting is 0.

Solution

Configure the Message Connector Service Timeout setting is 1200 which is the default value.  Any messages that have the blue arrow in the Transfer to Kofax App column will need to be reactivated.

Level of Complexity 

Easy

Applies to