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

Question

Question

Error when trying to launch a business process directly from LF Client

Laserfiche Workflow Version 10
Updated September 15, 2022
asked on October 25, 2016

Hello,

 

I have a user who is on LF Client 10.1, LF Server 10.1.1.254, and Workflow 10.0.0.249. When they attempt to start a business process directly from the client, even the client on the WF server, they get the below error:

 

Error Code: 0
Error Message: Error launching Business Process:
    Entry: \Employee Records\zzWork Queue\HR\zzQuickFields\02 Processed\019587-CM
    Error Type: Unknown Error
    Error Message: Connection to the Workflow Server 'localhost' could not be created.

------------ Technical Details: ------------

LF.exe (10.1.1.254):
    Call Stack: (Current)
        LaunchBusinessProcess
        CStartBusinessProcessDialog::OnStartBusinessProcess
        CFolderListCtrl::OnBusinessProcessManager
    Call History:
           CGroupProvider::raw_GetAllGroupIdentifiers
           CGroupProvider::raw_GetAllGroupIdentifiers
           CGroupProvider::raw_GetAllGroupIdentifiers
           CGroupProvider::raw_GetAllGroupIdentifiers
           CGroupProvider::raw_GetAllGroupIdentifiers
           CGroupProvider::raw_GetAllGroupIdentifiers
           CGroupProvider::raw_GetAllGroupIdentifiers
           CBusinessProcessManager::GetStartingInstructionsDocument

 

Work Flow seems to work fine when running automatically. I have seen some other errors that look similar here in Answers but none specifically like the one I am seeing. Does anyone have any insight on this?

 

Thanks!

0 0

Answer

APPROVED ANSWER
replied on October 26, 2016

Charles opened a case with support and we reviewed the Workflow web services configuration.  Turns out that the Workflow web service configuration had an incorrect URL for the Web Application directory:
http://LASERFICHEWEB/workflow while the Web Workflow URL was http://LASERFICHEAPPS/WF".

Changing http://LASERFICHEWEB/workflow to http://LASERFICHEAPPS/Workflow resolved the issue.

1 0

Replies

replied on October 25, 2016

Make sure that the URL used for the Workflow Web Service that's configured in the Workflow Configuration Manager uses the actual Workflow Server name that can be accessible from the workstations and not just "localhost"
 

0 0
replied on October 25, 2016

Hi Raymond,

 

I jumped into the Work Flow Configuration Manager and was able to attain the URL. I was able to browse to the Work Flow Web site on both the server hosting Work Flow and also the Laserfiche Server as well. Is there something else that could be causing this?

 

Thanks!

 

 

0 0
View 6 previous replies
replied on October 25, 2016
0 0
replied on October 26, 2016

Hi Raymond,

 

I have gone through most of the troubleshooting steps. I have confirmed that Installation, Configuration, Authentication, IIS, Firewall, and Port's and Protocols check out. What I am not sure of though is the last one, Work Flow Server Port changes, the example error listed there matches the error that I am seeing. I am not sure though how to check if the Work Flow Server's port has changed. Is that referring to the Work Flow Server Service? If so, how can confirm what port it is on?

 

Thanks!

0 0
replied on October 26, 2016 • Show version history

Hi Raymond,

 

Actually I believe I found that in the Workflow Configuration Manager. The Workflow Port is set to 8085 which matches with what the port is in the Work Flow Config file:

 

<Connection WorkflowServer="localhost:8085" />

 

I am not sure what else could be causing the issue.

 

Thanks

0 0
replied on October 26, 2016

This is caused by the fact that the user who published this workflow was connected to the WF Server using "localhost" rather than the actual server name. So it was published as being located on "localhost" to the Laserfiche server. When a Client on a different machine tries to start it, it's trying to send the message to that machine rather than the Workflow Server.

Connect your WF Designer to the WF Server by using the server name, open and republish the business process.

(Port 8085 is the default port for connections between the Workflow components and the Workflow Server. It has no bearing on the Workflow Web Service which is hosted by IIS, by default on port 80, and which the clients contact directly when starting business processes)

0 0
replied on October 26, 2016

We republished the workflow after updating the server we are connecting to through the workflow server.

We are still receiving the same error. We verified that other workflow business processes do work fine, except for this workflow.

0 0
replied on October 26, 2016

Is the error still referencing "localhost"?

0 0
replied on October 26, 2016

Yes, it is. 

0 0
replied on October 26, 2016

Here is the entire error in event viewer: 

Timestamp: 2016-10-26 16:07:39.299

Local Time: 10/26/2016 10:07:39 AM

Category: Errors

Machine: LASERFICHEAPPS

Severity: Error

Application Domain: Laserfiche.Workflow.Subscriber.exe

Process Id: 10596

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

Win32 Thread Id: 11272 - Subscriber Thread

Thread Name: Subscriber Thread

Message: <Exception handlingInstanceId="9431370e-6330-40a0-9da9-0ecfa6411142">
  <Description>An exception of type 'Laserfiche.Workflow.WFSOException' occurred and was caught.</Description>
  <DateTime>2016-10-26 10:07:39Z</DateTime>
  <ExceptionType>Laserfiche.Workflow.WFSOException, Laserfiche.Workflow.ServerObjects, Version=8.3.0.0, Culture=neutral, PublicKeyToken=d8428ff9263e6cda</ExceptionType>
  <Message>An error occurred communicating with the workflow server. View error log for more details. [0604-WFSO0]</Message>
  <Source>Laserfiche.Workflow.ServerObjects</Source>
  <HelpLink />
  <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.Objects.Settings.GetSubscriberOption(Int32 connectionId, String subscriberName, WorkflowServerOptionType option)
   at Laserfiche.Workflow.Objects.Options.OptionsObject.get_Item(WorkflowServerOptionType option)
   at Laserfiche.Workflow.Objects.Options.OptionsObject.GetData[T](WorkflowServerOptionType optionType)
   at Laserfiche.Workflow.Subscriber.Runtime.LaserficheSubscriber82.StartupRepositoryThread(String repositoryGuid, ConnectionProfile profile, SubscriberRepositoryOptions options)
</StackTrace>
  <additionalInfo>
    <info name="MachineName" value="LASERFICHEAPPS" />
    <info name="TimeStamp" value="10/26/2016 4:07:39 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="ADAMS12\00laserfiche" />
  </additionalInfo>
  <InnerException>
    <ExceptionType>System.ServiceModel.CommunicationObjectFaultedException, System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089</ExceptionType>
    <Message>The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it is in the Faulted state.</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.CommunicationObject.ThrowIfDisposedOrNotOpen()
   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.ExecuteCommand(OperationCommand data)
   at Laserfiche.Workflow.Internal.WorkflowServerClient.ExecuteCommand(OperationCommand data)</StackTrace>
  </InnerException>
</Exception>

 

0 0
replied on October 26, 2016

Hi Miruna,

 

Any new workflow's that we publish as a business process do not work. We tested one older workflow that is a business process and it worked.

 

Thanks

0 0
replied on September 14, 2022

Running into this same exact problem, but in version 10.4 the Windows Client does not use the Workflow Web Services Web Applicaiton configuration because no matter what I enter in there, it always tries to connect to localhost. So this config has been moved somewhere else. Although localhost isn't the issue in my case, it is that workflow is rejecting the connections.

The problem is, the test option in the configuration can say everything is good, but then the windows client continues not to function (again not due to DNS issues).

0 0
View 2 previous replies
replied on September 14, 2022

Please open Workflow Designer and connect to the Workflow Server using its name instead of "localhost". Then open this business process and republish it.

0 0
replied on September 14, 2022

Not sure how someone connects to WF with the WF designer updates all the windows clients connections to WF.

I can't connect with WF designer by it's proper name, it says invalid credentials. Yet when I connect with localhost, it accepts those same credentials.

WF Designer is the app for desingers to build and maintian workflows, this is a problem with Windows Client users connecting to WF to start Business Processes.

I have already cleared up the DNS being a possibility though by installing the Win Client on the local host itself, still get the same error. So the problem is not an inability to resolve the server name.

0 0
replied on September 14, 2022

When a business process is published, in addition to publishing the workflow, a reference is also published in the repository informing it where to direct the clients when they attempt to start business processes. The name used is the name of the Workflow Server the Designer was connected to at publishing time. So if you are connected to "localhost", then that's the name that will be set for this business process in the repository and used by the Windows Client when attempting to start the process. Obviously, "localhost" on the Windows Client machine is not going to resolve to the WF Server.

Is this a workgroup setup or are you on a domain?

0 0
replied on September 14, 2022

I don't seem to experience that happening in other enviornments where I would be connecting in the designer to "localhost" but publishing BPs other users are starting from their workstation.

In this case I am now testing from the client installed on the local host though so I am no longer concerned with the DNS not resolving.

This is on a domain.

0 0
replied on September 15, 2022

What does this message mean? Where do I see the configuration for what server "ownes" a BP? That server isn't even hosting the WF service any longer.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...