2015-03-27 10:35 AM
I wonder if this is something error others are experiencing too and if there's a solution to it:
In my workflow, I want to query the jobID in one of the command so I have a line of script (copied from sample command "Send Email"):
$jobID = Get-WfaRestParameter "jobId"
Randomly, I am getting the error back with the 404 not found message. Sometimes when I resume the failed workflow, it shows the same error again, and some other times it goes on just fine.
I cannot repeat this error in the same environment, the occurance is very random to me.
To my understanding, the 404 error means WFA app can connect with WFA server but cannot find the jobID, which seems confusing because the job id exists as soon as the workflow is scheduled...
I found a post regarding similar issue here: http://community.netapp.com/t5/OnCommand-Storage-Management-Software-Discussions/The-remote-server-returned-an-error-404-Not-Found/td-p/32346
The solution from the post is to stop the " World Wide Web Publishing" Service
However, I am not able to fine such a service to stop...
2015-03-31 02:31 AM
No No IIS is not required. I was just asking because IIS and W3SVC are some services present by default on Windows server 2008, 12 and they can ( no always but some rare cases) interrupt the WFA services if WFA services are installed in default ports i.e.HTTP: 80 and HTTPS: 443.
2015-11-05 06:11 AM
Were you able to identify a solution for this problem. I've recently ran across the same issue and I'm currently running WFA v 3.01 where there are no IIS or W3MC services enabled.