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

Question

Question

The Workflow service won't start

asked on September 1, 2023

Hello,
I have a problem with one of our customers concerning the Workflow service. I noticed that the service wasn't started, so I restarted it manually. After a few seconds, the service stopped again. I couldn't restart it; it just kept stopping.

I can't get hold of the customer's IT department (which is a service provider) to find out if they've done a maj or something.


In the event viewer, this is what I get:

Timestamp: 2023-09-01 12:00:41.643

Local Time: 01/09/2023 02:00:41

Category: Errors

Machine: SRV-LF

Severity: Error

Application Domain: Laserfiche.Workflow.Subscriber.exe

Process Id: 4960

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

Win32 Thread Id: 6828 - Stats thread

Thread Name: Stats thread

Message: <Exception handlingInstanceId="d960c10d-0736-406d-92ae-5e0d829ca766">
  <Description>An exception of type 'Laserfiche.Workflow.WorkflowServerNotFoundException' occurred and was caught.</Description>
  <DateTime>2023-09-01 02:00:41Z</DateTime>
  <ExceptionType>Laserfiche.Workflow.WorkflowServerNotFoundException, Laserfiche.Workflow.ServerObjects, Version=8.3.0.0, Culture=neutral, PublicKeyToken=d8428ff9263e6cda</ExceptionType>
  <Message>Impossible de créer la connexion au Serveur Workflow 'localhost'.</Message>
  <Source>Laserfiche.Workflow.ServerObjects</Source>
  <HelpLink />
  <Property name="Server">localhost</Property>
  <Property name="Trace" />
  <Property name="IsCommunicationError">True</Property>
  <Property name="ServerExceptionType" />
  <Property name="TargetSite">Laserfiche.Workflow.Connection.ConnectionResults Connect(Laserfiche.Workflow.Connection.ConnectionOptions)</Property>
  <Property name="HResult">-2146233088</Property>
  <StackTrace>Client trace
   à Laserfiche.Workflow.Internal.WorkflowServerClient.Connect(ConnectionOptions options)
   à Laserfiche.Workflow.WorkflowConnection.Connect()
   à Laserfiche.Workflow.WorkflowApplication.ConnectToServer(WorkflowConnection connection)
   à Laserfiche.Workflow.WorkflowApplication.Open()
   à Laserfiche.Workflow.Subscriber.Runtime.WorkflowServerCommandExecutor.RestoreConnection()
</StackTrace>
  <additionalInfo>
    <info name="MachineName" value="SRV-LF" />
    <info name="TimeStamp" value="01/09/2023 12:00:41" />
    <info name="FullName" value="Microsoft.Practices.EnterpriseLibrary.ExceptionHandling, Version=5.0.414.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    <info name="AppDomainName" value="Laserfiche.Workflow.Subscriber.exe" />
    <info name="ThreadIdentity" value="" />
    <info name="WindowsIdentity" value="AUTORITE NT\Système" />
  </additionalInfo>
  <InnerException>
    <ExceptionType>System.ServiceModel.EndpointNotFoundException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
    <Message>Connexion à net.tcp://localhost:8085/ManagementService impossible. La tentative de connexion a duré pendant une période de 00:00:02.2656312. Code d'erreur TCP 10061 : Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée 127.0.0.1:8085. </Message>
    <Source>mscorlib</Source>
    <HelpLink />
    <Property name="TargetSite">Void HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)</Property>
    <Property name="HResult">-2146233087</Property>
    <StackTrace>
Server stack trace: 
   à System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   à System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   à System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   à System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   à System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   à System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   à System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   à System.ServiceModel.Channels.ServiceChannel.CallOpenOnce.System.ServiceModel.Channels.ServiceChannel.ICallOnce.Call(ServiceChannel channel, TimeSpan timeout)
   à System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   à System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   à System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   à System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   à System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   à System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   à System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp; msgData, Int32 type)
   à Laserfiche.Workflow.IWorkflowServerApi.Connect(ConnectionOptions options)
   à Laserfiche.Workflow.Internal.WorkflowServerClient.EnsureChannelReady()
   à Laserfiche.Workflow.Internal.WorkflowServerClient.Connect(ConnectionOptions options)</StackTrace>
    <InnerException>
      <ExceptionType>System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
      <Message>Aucune connexion n’a pu être établie car l’ordinateur cible l’a expressément refusée 127.0.0.1:8085</Message>
      <Source>System</Source>
      <HelpLink />
      <Property name="ErrorCode">10061</Property>
      <Property name="SocketErrorCode">ConnectionRefused</Property>
      <Property name="NativeErrorCode">10061</Property>
      <Property name="TargetSite">Void DoConnect(System.Net.EndPoint, System.Net.SocketAddress)</Property>
      <Property name="HResult">-2147467259</Property>
      <StackTrace>   à System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   à System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   à System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)</StackTrace>
    </InnerException>
  </InnerException>
</Exception>

The C: disk is in the red, but there's still 48G free. On the other hand, one of my workflows needs to copy files to a remote server, which is full. Could this be where the problem lies?

 

Thanks in advance.

Regards

0 0

Answer

SELECTED ANSWER
replied on September 26, 2023

@Miruna Babatie,

You right, the full hard disk was the problem. I deleted some files and now the service don't stop anymore.

1 0

Replies

replied on September 1, 2023

This error is fthe Workflow Subscriber saying the Workflow Server is not running. Errors relevant to why the Workflow Server may not be starting or crashing should be in the Application or System event log, not in the Workflow event log.

2 0
replied on September 5, 2023

Hi Miruna.

Thanks for your help.

I checked the Application and System event log and this is what I found.

 

APPLICATION

Application: Laserfiche.Workflow.Service.exe
Framework version: v4.0.30319
Description: the process was stopped due to an unhandled exception.
Exception information: System.IO.IOException
   to System.IO.__Error.WinIOError(Int32, System.String)
   to System.IO.FileStream.WriteCore(Byte[], Int32, Int32)
   to System.IO.FileStream.FlushWrite(Boolean)
   to System.IO.FileStream.Dispose(Boolean)
   to System.IO.FileStream.Finalize()
Name of failed application: Laserfiche.Workflow.Service.exe, version: 10.4.1.223, timestamp: 0x5cf95718
Name of failed module: KERNELBASE.dll, version: 10.0.14393.5850, timestamp: 0x64253b4c
Exception code: 0xe0434352
Error offset: 0x0000000000026ea8
Failed process ID: 0x243c
Start time of failed application: 0x01d9e048dfbe86e1
Path of failed application: C:\Program Files\Laserfiche Workflow 9\Laserfiche.Workflow.Service.exe
Path of failed module: C:\WINDOWS\System32\KERNELBASE.dll
Report ID: ad61f725-d4b6-48ed-b3c9-81e1a0eaef6f
Full name of failed package : 
Application ID of the failed package : 

 

SYSTEM

The Laserfiche Workflow 10.4 service ended unexpectedly. This has happened 1 time. The following corrective action will be taken in 60000 milliseconds: Restart the service.

I have a workflow that copies data to a hard disk. This hard disk is full. Could this be a reason to automatically stop the service?

0 0
replied on September 12, 2023

Yes, it is possible that scripts throwing errors could crash the service.

1 0
SELECTED ANSWER
replied on September 26, 2023

@Miruna Babatie,

You right, the full hard disk was the problem. I deleted some files and now the service don't stop anymore.

1 0
replied on September 5, 2023

You could also try looking in the Workflow Configuration Manager and see if everything is configured correctly. I had an issue like this when the monitored repository of ours wasn't pointed correctly.

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

Sign in to reply to this post.