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

Question

Question

Could not connect to Laserfiche Server in Workflow

Workflow
Updated January 8, 2016
asked on December 15, 2015

Hi,

I have a workflow that works on repeat activity depending on a batch etc. It works fine at times but then intermittently i will get an issue where it says "Could not connect to Laserfiche Server". After restarting the server it works fine. The service is using a local system account and i have never experienced issues like this in over a year. What else could i try to resolve this?

Thanks

Gert

0 0

Replies

replied on December 16, 2015

Is the Laserfiche server working normally at the time you get this message?  Can you connect to it using the Laserfiche client? Check the Application log for LF Server entries when you get this behavior in WF and see what messages you get there.  It may not be a Workflow issue at all but a Laserfiche server one.

0 0
replied on December 16, 2015

Hi Raymond, the server works normal i can login to Laserfiche client and everything. 

 

This is the error i get in WF App log:

 

Timestamp: 2015-12-16 12:54:00.698

Local Time: 12/16/2015 2:54:00 PM

Category: Errors

Machine: ##########

Severity: Error

Application Domain: Laserfiche.Workflow.Subscriber.exe

Process Id: 784

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

Win32 Thread Id: 10172 - Stats thread

Thread Name: Stats thread

Message: <Exception handlingInstanceId="7163b364-1a9f-4b18-a811-2786fca71ee4">
  <Description>An exception of type 'Laserfiche.Workflow.WorkflowServerNotFoundException' occurred and was caught.</Description>
  <DateTime>2015-12-16 14:54:00Z</DateTime>
  <ExceptionType>Laserfiche.Workflow.WorkflowServerNotFoundException, Laserfiche.Workflow.ServerObjects, Version=8.3.0.0, Culture=neutral, PublicKeyToken=d8428ff9263e6cda</ExceptionType>
  <Message>Connection to the Workflow Server 'localhost' could not be created.</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.OperationResult ExecuteCommand(Laserfiche.Workflow.Connection.OperationCommand)</Property>
  <Property name="HResult">-2146233088</Property>
  <StackTrace>Client trace
   at Laserfiche.Workflow.Internal.WorkflowServerClient.ExecuteCommand(OperationCommand data)
   at Laserfiche.Workflow.WorkflowServerClientExtensions.ExecuteCommandInternal(IWorkflowServerApi api, ExecuteOperationCommand command)
   at Laserfiche.Workflow.ServerObject.Update()
   at Laserfiche.Workflow.Subscriber.Runtime.WorkflowServerCommandExecutor.ExecuteCommandInternal(SubscriberCommand command, Int32 retryCount)
</StackTrace>
  <additionalInfo>
    <info name="MachineName" value="########" />
    <info name="TimeStamp" value="12/16/2015 12:54:00 PM" />
    <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="NT AUTHORITY\SYSTEM" />
  </additionalInfo>
  <InnerException>
    <ExceptionType>System.ServiceModel.EndpointNotFoundException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
    <Message>Could not connect to net.tcp://localhost:8085/ManagementService. The connection attempt lasted for a time span of 00:00:02.0436759. TCP error code 10061: No connection could be made because the target machine actively refused it 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: 
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.BufferedConnectionInitiator.Connect(Uri uri, TimeSpan timeout)
   at System.ServiceModel.Channels.ConnectionPoolHelper.EstablishConnection(TimeSpan timeout)
   at System.ServiceModel.Channels.ClientFramingDuplexSessionChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.OnOpen(TimeSpan timeout)
   at System.ServiceModel.Channels.CommunicationObject.Open(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.CallOnceManager.CallOnce(TimeSpan timeout, CallOnceManager cascade)
   at System.ServiceModel.Channels.ServiceChannel.EnsureOpened(TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]: 
   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData&amp; msgData, Int32 type)
   at Laserfiche.Workflow.IWorkflowServerApi.Connect(ConnectionOptions options)
   at Laserfiche.Workflow.Internal.WorkflowServerClient.EnsureChannelReady()
   at Laserfiche.Workflow.Internal.WorkflowServerClient.ExecuteCommand(OperationCommand data)</StackTrace>
    <InnerException>
      <ExceptionType>System.Net.Sockets.SocketException, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
      <Message>No connection could be made because the target machine actively refused it 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>   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
   at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
   at System.ServiceModel.Channels.SocketConnectionInitiator.Connect(Uri uri, TimeSpan timeout)</StackTrace>
    </InnerException>
  </InnerException>
</Exception>

0 0
replied on December 16, 2015

Is anything blocking port 8085?  Are LF and WF in the same machine?

Try rebooting the box and going through all the steps in the WF Configuration Manager.  When you get to the Monitored repository wizard, delete the existing entry and add it again.

0 0
replied on December 16, 2015

While i had a WF running to email 891 times it took a long time which i setup like that. i had to reboot the server numerous times and then it works again for a while. Nothing is blocking port 8085 either.

Microsoft Windows [Version 6.2.9200]
(c) 2012 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>netstat -a -n

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:80             0.0.0.0:0              LISTENING
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:443            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1723           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1801           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:1888           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2103           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2105           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2107           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2179           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5048           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5049           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5051           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5053           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5985           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8085           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8107           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8108           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:8188           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:10050          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:47001          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:56851          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:57959          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:57960          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:58008          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:58009          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:60043          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:64417          0.0.0.0:0              LISTENING
  TCP    10.0.7.51:80           10.0.1.111:60787       ESTABLISHED
  TCP    10.0.7.51:80           10.0.1.111:60788       ESTABLISHED
  TCP    10.0.7.51:80           10.0.7.51:64178        ESTABLISHED
  TCP    10.0.7.51:139          0.0.0.0:0              LISTENING
  TCP    10.0.7.51:445          10.0.7.52:55900        ESTABLISHED
  TCP    10.0.7.51:3389         10.0.7.52:55871        ESTABLISHED
  TCP    10.0.7.51:5051         10.0.7.51:62672        ESTABLISHED
  TCP    10.0.7.51:10050        172.16.10.99:33038     TIME_WAIT
  TCP    10.0.7.51:10050        172.16.10.99:33786     SYN_RECEIVED
  TCP    10.0.7.51:10050        172.16.10.99:60791     TIME_WAIT
  TCP    10.0.7.51:56851        10.0.7.50:53712        ESTABLISHED
  TCP    10.0.7.51:56851        10.0.7.50:53713        ESTABLISHED
  TCP    10.0.7.51:58017        80.79.115.254:5938     ESTABLISHED
  TCP    10.0.7.51:58045        10.0.7.80:445          ESTABLISHED
  TCP    10.0.7.51:62672        10.0.7.51:5051         ESTABLISHED
  TCP    10.0.7.51:64095        188.172.217.41:5938    ESTABLISHED
  TCP    10.0.7.51:64171        10.0.7.51:80           TIME_WAIT
  TCP    10.0.7.51:64173        10.0.7.51:80           TIME_WAIT
  TCP    10.0.7.51:64178        10.0.7.51:80           ESTABLISHED
  TCP    127.0.0.1:5939         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:5939         127.0.0.1:58058        ESTABLISHED
  TCP    127.0.0.1:5939         127.0.0.1:64096        ESTABLISHED
  TCP    127.0.0.1:58058        127.0.0.1:5939         ESTABLISHED
  TCP    127.0.0.1:58070        127.0.0.1:58071        ESTABLISHED
  TCP    127.0.0.1:58071        127.0.0.1:58070        ESTABLISHED
  TCP    127.0.0.1:58088        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:64096        127.0.0.1:5939         ESTABLISHED
  TCP    [::]:80                [::]:0                 LISTENING
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:443               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:1801              [::]:0                 LISTENING
  TCP    [::]:1888              [::]:0                 LISTENING
  TCP    [::]:2103              [::]:0                 LISTENING
  TCP    [::]:2105              [::]:0                 LISTENING
  TCP    [::]:2107              [::]:0                 LISTENING
  TCP    [::]:2179              [::]:0                 LISTENING
  TCP    [::]:3389              [::]:0                 LISTENING
  TCP    [::]:5048              [::]:0                 LISTENING
  TCP    [::]:5049              [::]:0                 LISTENING
  TCP    [::]:5051              [::]:0                 LISTENING
  TCP    [::]:5053              [::]:0                 LISTENING
  TCP    [::]:5985              [::]:0                 LISTENING
  TCP    [::]:8085              [::]:0                 LISTENING
  TCP    [::]:8107              [::]:0                 LISTENING
  TCP    [::]:8108              [::]:0                 LISTENING
  TCP    [::]:8188              [::]:0                 LISTENING
  TCP    [::]:10050             [::]:0                 LISTENING
  TCP    [::]:47001             [::]:0                 LISTENING
  TCP    [::]:49152             [::]:0                 LISTENING
  TCP    [::]:49153             [::]:0                 LISTENING
  TCP    [::]:49154             [::]:0                 LISTENING
  TCP    [::]:56851             [::]:0                 LISTENING
  TCP    [::]:57959             [::]:0                 LISTENING
  TCP    [::]:57960             [::]:0                 LISTENING
  TCP    [::]:58008             [::]:0                 LISTENING
  TCP    [::]:58009             [::]:0                 LISTENING
  TCP    [::]:60043             [::]:0                 LISTENING
  TCP    [::]:64417             [::]:0                 LISTENING
  TCP    [::1]:80               [::1]:64174            TIME_WAIT
  TCP    [::1]:80               [::1]:64175            TIME_WAIT
  TCP    [::1]:80               [::1]:64176            TIME_WAIT
  TCP    [::1]:8085             [::1]:62676            ESTABLISHED
  TCP    [::1]:8085             [::1]:62677            ESTABLISHED
  TCP    [::1]:8085             [::1]:62678            ESTABLISHED
  TCP    [::1]:62676            [::1]:8085             ESTABLISHED
  TCP    [::1]:62677            [::1]:8085             ESTABLISHED
  TCP    [::1]:62678            [::1]:8085             ESTABLISHED
  TCP    [::1]:64177            [::1]:80               TIME_WAIT
  UDP    0.0.0.0:123            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:1434           *:*
  UDP    0.0.0.0:1701           *:*
  UDP    0.0.0.0:1891           *:*
  UDP    0.0.0.0:3389           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5055           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:11548          *:*
  UDP    0.0.0.0:13013          *:*
  UDP    0.0.0.0:13611          *:*
  UDP    0.0.0.0:51969          *:*
  UDP    0.0.0.0:54679          *:*
  UDP    0.0.0.0:56533          *:*
  UDP    0.0.0.0:58383          *:*
  UDP    0.0.0.0:58384          *:*
  UDP    0.0.0.0:59591          *:*
  UDP    0.0.0.0:60945          *:*
  UDP    10.0.7.51:137          *:*
  UDP    10.0.7.51:138          *:*
  UDP    10.0.7.51:1891         *:*
  UDP    10.0.7.51:5353         *:*
  UDP    127.0.0.1:13012        *:*
  UDP    127.0.0.1:52475        *:*
  UDP    127.0.0.1:52788        *:*
  UDP    127.0.0.1:60380        *:*
  UDP    127.0.0.1:60633        *:*
  UDP    127.0.0.1:64223        *:*
  UDP    [::]:123               *:*
  UDP    [::]:500               *:*
  UDP    [::]:1434              *:*
  UDP    [::]:1701              *:*
  UDP    [::]:3389              *:*
  UDP    [::]:4500              *:*
  UDP    [::]:5055              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:60946             *:*
  UDP    [::1]:5353             *:*
  UDP    [::1]:51967            *:*
  UDP    [::1]:51968            *:*

C:\Users\Administrator>

 

i can try and re-add the repository and see if it makes a difference. 

 

0 0
replied on December 16, 2015

Try rebooting the box and going through all the steps in the WF Configuration Manager.  When you get to the Monitored repository wizard, delete the existing entry and add it again.  In that order. Don't skip any steps.  If it is still an issue after that, please open a case.

0 0
replied on December 17, 2015

Hi Raymond, 

 

I will do. 

 

Thanks

Gert

0 0
replied on January 8, 2016

I am getting the same message, did the solution offered on Dec 16th work? Can someone detail the findings and the fix. Thanks

0 0
replied on January 8, 2016 • Show version history

If that did not work for you, please open a case.  We will need to look into the Workflow LOGS (entries in the Communication log but zip up the whole folder and attach it to the case you open anyway.)

0 0
replied on January 8, 2016

Uninstalling the WorkFlow Subscriber Service (WorkFlow Installation), reinstalling and configuring again has worked.

0 0
replied on January 8, 2016

Glad it worked for you!

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

Sign in to reply to this post.

Details
Related Posts
Loading ...