3

I am using the standard out the box workflow definition “Task Process”. When I add more than 13 items exact to the Bundle, it always fails at the 14th every single time. The error message in the Event log was:

The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. The write operation failed, see inner exception. The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '00:01:00'. An existing connection was forcibly closed by the remote host

Component: Tridion.ContentManager.CoreService

Errorcode: 0 User: NT AUTHORITY\NETWORK SERVICE

StackTrace Information Details: at System.Net.Sockets.Socket.Send(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags) at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.SocketConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.BufferedConnection.WriteNow(Byte[] buffer, Int32 offset, Int32 size, TimeSpan timeout, BufferManager bufferManager) at System.ServiceModel.Channels.BufferedConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.ConnectionStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.Net.Security.NegotiateStream.StartWriting(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.ProcessWrite(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest) at System.Net.Security.NegotiateStream.Write(Byte[] buffer, Int32 offset, Int32 count) at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout) at System.ServiceModel.Channels.StreamConnection.Write(Byte[] buffer, Int32 offset, Int32 size, Boolean immediate, TimeSpan timeout, BufferManager bufferManager) at System.ServiceModel.Channels.FramingDuplexSessionChannel.OnSendCore(Message message, TimeSpan timeout) at System.ServiceModel.Channels.TransportDuplexSessionChannel.OnSend(Message message, TimeSpan timeout) at System.ServiceModel.Channels.OutputChannel.Send(Message message, TimeSpan timeout) at System.ServiceModel.Channels.TransactionDuplexChannelGeneric`1.Send(Message message, TimeSpan timeout) at System.ServiceModel.Channels.RequestContextBase.Reply(Message message, TimeSpan timeout) at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.Reply(MessageRpc& rpc)

I tried to increase the WCF maxReceivedMessageSize and receiveTimeout properties for the main Tridion Web.config files with no luck

Any help is appreciated

  • You increased the maxReceivedMessageSize but the error is about a timeout, not about the data received. You may have to change the Timeout settings instead - anyway, do open a support ticket, this doesn't sound right. – Nuno Linhares Jul 19 '13 at 18:14
  • Thanks Nuno, you are right, the timeout I found in the config files is 10 mins, and the error is saying 1 min , and I read that this message could be misleading, and the size would be the problem specially, the Components I am adding to the bundle are super sized components. – Ashraf Nabih Jul 19 '13 at 18:21
  • OK, I'll try to take a look - I saw timeouts before, but after 200+ components, and also using the default of 1 minute. – Nuno Linhares Jul 19 '13 at 18:25
  • Is this when you add an item or when you start the workflow? – Nuno Linhares Jul 19 '13 at 18:47
  • it happens when finishing the last activity of the workflow. Thanks Nuno for looking into it – Ashraf Nabih Jul 19 '13 at 18:55
3

Thanks for everyone commented, and tried to help to resolve my issue, Finally the issue was resolved by help from SDL Support, and here are the steps taken to resolve the issue:

1. In Tridion\bin\TcmServiceHost.exe.config
-  Change the CoreService_netTcpBinding binding
<binding name="CoreService_netTcpBinding"
transactionFlow="true"
transactionProtocol="WSAtomicTransaction11"
maxReceivedMessageSize="2147483647"
closeTimeout="00:30:00"
openTimeout="00:30:00"
receiveTimeout="00:30:00"
sendTimeout="00:30:00">
2. Add the followig before </behaviour>
<serviceTimeouts transactionTimeout="00:30:00" />
3. To increase the CoreService timeout:
In  %windir%\Microsoft.NET\Framework64\v4.0.30319\Config\machine.config
and %windir%\Microsoft.NET\Framework\v4.0.30319\Config\machine.config
-  Change all instances of allowExeDefinition from "MachineOnly" to "MachineToApplication"
4. In two files mentioned in previous step, before </configuration> add the section below
<system.transactions>
<defaultSettings timeout="01:30:00"/>
<machineSettings maxTimeout="01:30:00" />
</system.transactions>
5. In %Tridion_HOME%\config\Tridion.ContentManager.config
- Provide a value for transactionTimeout in seconds
<session transactionTimeout="3600" />

Thanks everyone

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.