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

Question

Question

Error consuming workflow web service

asked on January 29, 2015 Show version history

When I try to set a reference to the workflow web service I get an error stating:

There was an error downloading 'http://myserver/workflow/api/RestWorkflowAPI.svc?wsdl/_vti_bin/ListData.svc/$metadata'.

The request failed with HTTP status 404: Not Found.
Metadata contains a reference that cannot be resolved: 'http://myserver/workflow/api/RestWorkflowAPI.svc'.
The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '

 

I've tried accessing a bunch of different ways, but can't figure out what the problem is ...

/workflow/api/RestWorkflowAPI.svc

/workflow/api/RestWorkflowAPI.svc?wsdl

 

0 0

Answer

APPROVED ANSWER
replied on January 29, 2015

Hi Rich,

Are you attempting to reference the rest services via visual studio? There are a couple of basic things to check if you're getting a 404 error. It sounds like the webservice isn't running.

Workflow Installation - Have the webservices been installed?

Workflow Config - Have you run through this? Is everything roses? The last item is for testing the web services, are they running?

IIS - Is World Wide Web services installed and is it running?

After that has been checked, when you connect you might get a security error. In which case, enable anonymous and Windows Auth. for the API folder and restart WWW services. 

 

Good luck!

 

0 0
replied on August 11, 2015

Ben,

I am having a similar issue when trying to access this through Visual Studio.  Is that causing the issue?  I've checked the list you provided above but could not get any different result than what Rich explained in his initial question.  Any help is much appreciated!  

Nate

0 0

Replies

replied on February 3, 2015

Resolved:  Windows Authentication was not enabled on IIS for this site

1 0
replied on February 13, 2015

I have the same issue here but Windows Authentication is already enabled. I've been through the settings on a machine that does work and checked with mine but it doesn't seem to want to play ball. I get the error when trying to add the service reference or browse via a web browser.

0 0
replied on March 13, 2019

I'm experiencing the same issue. I've ensured the Workflow/API website in IIS has both Anon and Windows Auth enabled and continue to get a 404 error when browsing to server/Workflow/API/RestWorkflowAPI.svc

Please advise on a solution.

0 0
replied on August 15, 2019

I've been encountering the same issues lately as well whereas I don't have these issues with other implementations. Has there been a solid direction anyone has found?

-HB

0 0
replied on February 9, 2022 Show version history

If anyone still has this issue.  Adding this line to your workflow server web.config file in the system.webser>handler section> 

Obviously, don't add the system.webser or handlers as they are already there...

 

<system.webServer>
  <handlers>
     <remove name="svc-Integrated" />
     <add name=".svc" verb="*" path="*.svc" type="System.ServiceModel.Activation.ServiceHttpHandlerFactory, 
        System.ServiceModel.Activation, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />

 

 

 

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

Sign in to reply to this post.