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

Question

Question

An error occurred communicating with the workflow server. View error log for more details.

asked on August 12, 2015

This is something which was working fine some days before but it's not working now.

So I have my LF Server and WF installed on a VM.

I am using WF SDK to connect to the WF Server. (I am connecting using the IP address and IP is correct. Both machines, the VM and my laptop (where I have the code running) are at the same domain and I am logged in with same user on both).

 

When I run this code:

 using (Laserfiche.Workflow.WorkflowConnection connection = Laserfiche.Workflow.WorkflowConnection.CreateConnection(workflowServer, workflowApplication))

it throw the following error message:

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

 

Please see the view details screenshot attached.

I can confirm that:

- The WF server service is running.

- I can connect to the WF using WF Disgner

- I can connect to the rep at the VM using the client at my laptop.

- WF Server and subscriber service are running using Local System account (as since always).

 

Any idea what's happening.

 

Thanks in advance.

View Details.png
View Details.png (23.93 KB)
0 0

Replies

replied on August 12, 2015

What user is the app running under? I'd start there. Unmodified members of the Everyone group has permissions in workflow. However if you've changed that or if somehow the service account you are running is not part of everyone it could cause this issue. Additionally, if it's running under the local service account that's not a domain account so it wouldn't have permissions outside of your machine (i.e. on the server).

In addition, in this thread they had this same issue with designer on a sporadic basis when UAC was enabled: https://answers.laserfiche.com/questions/49235/Workflow-Designer-Connection-Fail-Error0604WFSO0

 

It might be worth turning that off and seeing if it makes a change. 

 

0 0
replied on August 13, 2015

Hi Chris,

I believe it has something to do with the connection to the VM hosting WF server.

I have tried to connect to the WF server in question using WF Designer at another VM and it doesn't connect.

I then tried to access one of the drive at that VM (\\LFWFVM\c$) and i can't. Which clearly means that access to the VM is not open.

 

On a different note, I was running code in Visual Studio 2012 running at my laptop and I wasn't able to run it again the VM with WF server. I then copied the executable to the VM itself and I can run it fine (it does triggers the workflow).

Thanks

0 0
replied on August 13, 2015

Found the reason.

I wasn't logged into my laptop with service account and hence WF at VM was rejecting the connection.

But the strange thing is, it did work when I originally wrote the code and testing it many times. I had the exact same environment setup at that time.

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

Sign in to reply to this post.