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

Question

Question

Workflow Designer Connection Fail Error:[0604-WFSO0]

asked on January 27, 2014

When opening Workflow Designer 9.1 or Workflow Administration 9.1 console on my local machine, I receive an error message that communication failed with the Workflow Server. This problem randomly happened to my local machine and no other machines on the network with the Workflow software installed.

 

Error Message:

An error occurred communicating with the workflow server. View error log for more details. [0604-WFSO0]

Description:

Either the target name is incorrect or the server has rejected client credentials.

 

Not sure if this may have been caused by updating from 9.0 to 9.1. Does anyone have any ideas on what may be causing this and how to solve this problem?

0 0

Replies

replied on January 27, 2014

Are you on an active directory network or just a workgroup? Workflow uses Windows Authentication for security, so an active directory is required when you connect from machines other than the WF Server.

0 0
replied on January 27, 2014

We are on an Active Directory network. The Laserfiche Client uses Windows Authentication to open. Does Workflow function similarly?

0 0
replied on January 27, 2014

Yes, the WFDesigner uses Windows Authentication to log into the Workflow Server and check security.

 

Is this on a machine that's connected through VPN or on a laptop that's switching between wireless and wired connections?

0 0
replied on January 28, 2014

This is on a desktop machine connected directly through only a wired connection. Workflow Designer worked without any problems when I had 9.0 installed. I updated to 9.1 and I believe it worked for a week or two before this error came up.

0 0
replied on April 18, 2014

I am having a similar issue, only I am using WF9.0. My error message is [0544-WF0]

I will monitor this thread. Thanks

0 0
replied on April 18, 2014

Chris, is your error intermittent? Do other parts of the Designer work and only the condition editor fails? What if you connect to the WFServer using its fully qualified domain name rather than just the machine name?

0 0
replied on April 21, 2014

Hi Miruna :)

 

My issue is semi-intermittent. It occurs between 11AM and 2PM daily. No backups are currently running and anti-virus was just installed for the first time 4/18/14.

 

The event log-Win logs->System had an error related to DCOM. Is this a clue?

 

DCOM was unable to communicate with the computer XYZLSF.xyzxyz.local using any of the configured protocols.

 

The designer works for activities which do not retrieve data from LFServer. For example, routing decisions are fine, but retrieve field values fails. What got my attention first was that I could not publish a Workflow.

 

Yes, I can connect to the WFServer using its fully qualified domain name. Although, I had not done so previously. Great suggestion.

 

Thank you!

0 0
replied on April 21, 2014

Right, I was thinking it is some sort of name resolution issue on your domain. The DCOM error is probably not from Laserfiche, but it might have the same root cause.

0 0
replied on November 24, 2014

Hi All.

I have the same problem with Workflow. First I could not run my workflow to test as it told me "Could not Connect to the LF Server".

 

Then I restarted the system and it gave me this error.

I am running it on a local machine and all the names resolves properly.

 

Any advice ?

 

Regard

Adam

 

 

0 0
replied on November 25, 2014

Adam,

Is the WF Server service started?

0 0
replied on November 25, 2014

Hi Miruna.

All the services are up and running, and I restarted them to confirm this.

0 0
replied on December 16, 2014

Hi,

When opening Workflow Designer 9.1 or Workflow Administration 9.1 console on my local machine, I receive an error message that communication failed with the Workflow Server. This problem randomly happened to my local machine.

 

Error Message:

An error occurred communicating with the workflow server. View error log for more details. [0604-WFSO0]

LFWF-Error.JPG
LFWF-Error.JPG (104.9 KB)
0 0
replied on March 19, 2015

Disabling the UAC on the workflow server and then restarting it seemed to have worked for this error if it's happening to more than one user. 

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

Sign in to reply to this post.