BAD header errors

I have a couple of my clients calling about a BAD header error they were getting when submitting their infopath based forms to kick-off K2 workflows. In all cases this was due to their environment library configuration pointing to the wrong service. For some reason the connection string for the Workflow Server has the wrong port number (5555) set, instead of the workflow service’s port (5252).

So, if you are facing this issue check your environment library settings first.

Published by jeylabs

Are you ready to Transform your Enterprise?

%d bloggers like this: