You are viewing limited content. For full access, please sign in.

Question

Question

Email Error Terminating WF: The operation has timed out.

asked on March 11, 2015

Over the last couple of days we have noticed an increase in Workflows being terminated on the Standard WF Email activity with an Error message of "The Operation Timed out."

Today alone thus far there has been just over 100 Workflows terminated with this error. This has been at various times in the morning and not all at once at the same time.

 

Here is an extract of the Error from the Activities log on the WF Server:

Timestamp: 2015-03-11 10:10:44.650

Local Time: 2015/03/11 12:10:44 PM

Category: Activity

Machine: VMISFDMSWF

Severity: Error

Application Domain: Laserfiche.Workflow.Service.exe

Process Id: 5496

Process Name: C:\Program Files\Laserfiche\Laserfiche Workflow 9\Laserfiche.Workflow.Service.exe

Win32 Thread Id: 15576 - 

Thread Name: 

Message: <Exception handlingInstanceId="04d587ca-707a-4639-b1fc-26b9d40d313c">
  <Description>An exception of type 'System.Net.Mail.SmtpException' occurred and was caught.</Description>
  <DateTime>2015-03-11 12:10:44Z</DateTime>
  <ExceptionType>System.Net.Mail.SmtpException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
  <Message>The operation has timed out.</Message>
  <Source>System</Source>
  <HelpLink />
  <Property name="StatusCode">GeneralFailure</Property>
  <Property name="EmailSyncLevel">11</Property>
  <Property name="InstanceId">d1991d71-6e0d-4cdb-bc90-08c5f2af5704</Property>
  <Property name="ActivityName">Email_EmailWithAttachments</Property>
  <Property name="TargetSite">Void Send(System.Net.Mail.MailMessage)</Property>
  <Property name="HResult">-2146233088</Property>
  <StackTrace>   at System.Net.Mail.SmtpClient.Send(MailMessage message)
   at Laserfiche.Workflow.Activities.Email.Runtime.EmailTaskExecutor.Execute(EmailTaskOptions options, TaskExecutorContext status)</StackTrace>
  <additionalInfo>
    <info name="MachineName" value="VMISFDMSWF" />
    <info name="TimeStamp" value="2015/03/11 10:10:44 AM" />
    <info name="FullName" value="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    <info name="AppDomainName" value="Laserfiche.Workflow.Service.exe" />
    <info name="ThreadIdentity" value="" />
    <info name="WindowsIdentity" value="NT AUTHORITY\SYSTEM" />
  </additionalInfo>
</Exception>

 

Has anyone else seen this type of behaviour before or is there any indication what could be causing this?

0 0

Replies

replied on March 12, 2015

Hi Vincent,

 

I've seen this before but the resolution wasn't a Laserfiche workflow thing. The problem I had is that the exchange mail server didn't have an SMTP relay connector setup to allow SMTP relay from the Laserfiche Workflow server IP address. I would check that the Exchange server is correctly configured to allow SMTP relay (anonymous user or authenticated user) from the Laserfiche Workflow server IP address.

 

Hope this helps!

1 0
replied on March 11, 2015

Does the email go out?

If you go through the WF email configuration and test it, does that work?

0 0
replied on March 12, 2015

Hi Raymond, on the Terminated WF no email goes out. If however I restart the WF on the document then it goes through fine. 

testing the configuration works fine. The problem is also not restricted to one Workflow, there are different workflows having the same problem and behavior. 

Today thus far we have had approximately 120 Terminations because of this. It is becoming tedeuos to re-start the terminated Workflows as some is effecting processes stages of documents.  

0 0
replied on March 12, 2015 Show version history

Since it works when you restart it suggests that you have an issue with the SMTP server but more along the lines of a delay than an error.

You can also try adding the error to the Task Error Handler as suggested in this thread.  You can find the instructions here.  Basically the WF will not terminate and it will try sending the email again until the SMTP server becomes available or has more resources to deal with the WF emails.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.