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

Question

Question

Invoke Workflow on non default port

asked on October 6, 2015

Client is on Workflow 8.3.  At some point they must have switched workflow to a different port.  In the Workflow designer we wanted to make a change to a running workflow.  When I tried to re-publish I got an error on the Invoke Workflow step.  It said "could not connect to net tcp://Laserfiche:8085/Management Service".

We noticed that workflow is running on 8087.  When you go to Tools- Connected to workflow server we get this popup:

Hitting Test works just fine.  There are currently published and active workflows that are working.  So it seems that the port change was made while the workflow was published.  Now trying to modify that workflow and re-publish seems to cause an error with the Invoke Workflow activity.  We have tried deleting the activity and re-adding but when we try and pick the workflow we wish to invoke in the properties of the Invoke Workflow activity we get the error first mentioned.  How do we go about telling the Invoke Workflow activity to connect using 8087 instead of default?  

 

Thanks

0 0

Answer

SELECTED ANSWER
replied on October 6, 2015

The screenshot if from setting the WF Server the Designer is connecting to. I think you want to set the WF Server in the Invoke Activity instead.

0 0
replied on October 6, 2015

Ah, I seem to have missed the cog wheel icon near the top.  I see it on my version 9 workflow and assume that is also present in 8.  I'll have access to their server tomorrow to confirm.  Thank you for the response.  

0 0

Replies

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

Sign in to reply to this post.