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

Question

Question

Workflow ODBC Operation Timeout

asked on April 5, 2021

I am testing an ODBC that needs to use a specific port. I can read data from it easily using Crystal Reports, but it will not play nice with Workflow. I get the below error message pop up:

 This request operation sent to net.tcp://xyz-workflow:8085/ManagementService did not receive a reply within the configured timeout (00:00:30).  The time allotted to this operation may have been a portion of a longer timeout.  This may be because the service is still processing the operation or because the service was unable to send a reply message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

 

I get this when attempting to view the table drop down list from the query activity.

 

Here is a clip from the Laserfiche whitepaper for Default Ports used:

 

When I add the data source to Workflow, it tests successfully:

 

 

The big question: Can anyone confirm that when using Workflow, all query data goes out port 8085? Or does it go in and out of the port defined in the ODBC connection? 

I believe the same thing is happening with Forms. Which port does Forms use for data lookups? I can't retrieve any data there either. 

 

FYI I am attempting to lookup Skyward SMS from an OpenEdge database using the 64 bit SQL driver provided by the vendor.

 

Thank you in advance!

 

0 0

Answer

SELECTED ANSWER
replied on April 5, 2021

Communication between clients and the WF Server happens on port 8085 or port 80/443 when the web service is used (such as for Forms to WF communication).

ODBC drivers are using the respective ports for the target destination and are not under Workflow (or Forms) control.

1 0

Replies

replied on April 5, 2021

just what I was looking for. Thanks!

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

Sign in to reply to this post.