2014-01-28 02:26 PM
I have upgraded to WFA 2.1 recently and am now getting the following error via SOAP calls, only the WFA version has changed. Would anyone be able to tell me where to start looking?
"Exception calling "getAllWorkflows" with "0" argument(s): "The request failed with HTTP status 505: HTTP Version Not Supported"
Solved! SEE THE SOLUTION
2014-01-29 12:01 AM
This issue is a JBoss7.1 issue and this is the JBoss version WFA2.1 is using. I can give you a solution but I need to know how are you calling the SOAP request because not all client throw this error. Example: Using a soapUI4.1 I don't get this error. I have tried with linux curl cli and that too doesn't give any errors. But calling it from Powershell script using New-WebServiceProxy throws this error.
So the solution depends on what is the client that you are using.
2014-01-29 01:10 AM
Found out that this issue is with .net and Jboss7.1. So all clients that use .NET will suffer this Problem.
Solution is to set the Expect100Continue to 0 or false. What is Expect100Continue? Here is a blog post on it. http://alihamdar.com/2010/06/19/expect-100-continue/
Just before calling the New-WebServiceProxy , write the following line.
[System.Net.ServicePointManager]::Expect100Continue = $false
servicePoint.Expect100Continue = false;
Any other .NET client with a config file:
2014-01-29 05:04 AM
Thank you for the prompt response. I have updated the code in our lab and have successfully tested jobs.
We are indeed using powershell, so calling the .NET framework worked perfectly.
2015-07-16 04:22 AM
we are now using WFA 3.0 and the problem is still there. We can not use the workaround since we're initiating from System Center Orchestrator (Invoke REST).
Do you have any idea or experience with this?
2015-08-01 09:30 AM
Its your client which is a part of the problem. Invoke REST from MS System Center Orchestrator is also .NET based and this error is due to .NET with Jboss7.1 ( which is WFA3.0's server ).
You need to add below key-value pair in request header
while makiing HTTP requests.
WFA3.1 has upgraded its Jboss, so this problem might get resolved in wfa3.1. I'll check this and update you.