BAD header errors

Posted by

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.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s