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

Question

Question

[0757-wf0] Forms not configured to interact with this Workflow server

asked on September 19, 2018 Show version history

In Forms config:

In Workflow:

I have the FormsConfig successfully applying the same values.  Wondering why Workflow Server isn't interacting.

 

Replies

replied on September 19, 2018

Do you have Workflow and Forms installed on the same server? The reason I ask is that under the Forms configuration for Workflow you have "localhost"

On a side note, it looks like you forgot to redact the URL in the Workflow configuration screenshot like you did in the Forms config screenshot.

replied on September 19, 2018

They are on the same server yes.

By redact are you referring to the Workflow configuration in Forms?

If I enter the URL there, I get the following error:

 

replied on September 19, 2018

Sorry I believe this is the proper URL to place there:

 

replied on September 19, 2018

Sorry, by redact I mean you drew over it to hide the domain in the first screenshot, but you forgot to do that in workflow one. I just thought I would point that out since you probably didn’t want to post it publicly. 

 

replied on September 19, 2018

Ah yes that is true.  Thank you much.

replied on September 19, 2018

No problem. You’ll also want to click the “version history” link and delete it from there too.

As for the error, I’ve never seen that one before. You don’t get any errors in Forms when you change it back to local host, right?

replied on September 19, 2018

I don’t. When the workflow server in forms is set to localhost and SSL is checked it it saves. 

But the Web Service in workflow still reports the same error you see. 

replied on September 20, 2018

What happens when you put "localhost" then click "Test Connection"

We have a test server that has both WF and Forms, but it uses the server name instead of localhost.

The other question would be, is there a reason you're routing them out to a ".com" instead of just internally?

replied on September 20, 2018 Show version history

Because it's asking for the address: In SSL

replied on September 20, 2018

SSL should still work if the server has a certificate. We use SSL for some of our internal LF sites and we can still access them with HTTPS://servername type URLs.

replied on September 20, 2018 Show version history

The server does.  I can use the SSL cert just fine using a browser going to the Forms website.

Workflow is localhost as well.  When I use the normal http://servername/forms 

it is not even resolving to itself:

 

Everything is working except Workflow's Web Service to Forms.

replied on September 20, 2018 Show version history

If you have it set to use HTTPS, then HTTP may not resolve depending on the bindings. The easy way to check that would be in IIS on the hosting server.

However, in our environment if I try to open forms with HTTP it auto-redirects to HTTPS so I know it can work that way.

replied on September 20, 2018

Do you have your FormsConfig set to SSL?  Or are you just allowing all http to redirect to https through the IIS HTTP Redirect?

replied on September 20, 2018

Our Forms instances are configured to use SSL

replied on September 20, 2018

I'm using internal server names in my configurations and it is working for me.  Change your URL references to the actual server names.

You are not allowed to follow up in this post.