The Microsoft Cloud Blog
1 min read
BizTalkSharePoint

BizTalk WSS Adapter: RequestFailed: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF

ShareLinkedInXBlueskyThreadsFacebook

Whilst attempting to set up the WSS adapter for a client I was receiving the following error when trying to call the WSS adapter web service.

“RequestFailed: The server committed a protocol violation. Section=ResponseHeader Detail=CR must be followed by LF”

This seemed to me to be an issue where BizTalk was receiving an error that it could not understand.  Sure enough after installing NetMon and looking at the requests between the BizTalk server and the SharePoint server I noticed that the actual message was a 401.2 authentication error message, but for some reason BizTAlk could not read/display the correct message.

Want more cloud insights? Listen to Cloudy with a Chance of Insights podcast:

Spotify | YouTube | Apple Podcasts

Tags

biztalkErrors
Like this article?

Comments

Richard Hogan

Richard Hogan

Author & Host

Richard is a Microsoft-focused architect and consultant with deep expertise in Azure, Microsoft 365, cybersecurity, and enterprise cloud migration. He is the founder of The Microsoft Cloud Blog and co-host of the Cloudy with a Chance of Insights podcast. All views expressed are his own.

You might also like

BizTalk WSS Adapter: HTTP 401.2 – Unauthorized: Logon failed due to server configuration

Continuing my experience of attempting to configure the WSS adapter for a clients BizTalk/SharePoint integration project.  As mentioned in my previous post I was having an authentication issue between the clients SharePoint and BizTalk instances.  The message I was getting back (not in BizTalk unfortunately) was the following 401.2 message. “HTTP 401.2 – Unauthorized: Logon failed due to server… Continue Reading →

Server Error in ‘/BTSharePointAdapterWS’ Application: Request format is unrecognised

Whilst configuring the SharePoint Adapter for BizTalk for a client today, I came across a couple of issues. The first error made me think that I had really screwed up the installation of the WSS adapter.  I was getting the following error when trying to browse to the web service. “Request format is unrecognized. Description:… Continue Reading →

SharePoint 2013 Error: The filtering process has been terminated

I had just completed a PowerShell scripted deployment of a SharePoint farm and was just performing the final checks when I noticed the following error in the crawl logs. “The filtering process has been terminated” This turned out that because in the PowerShell script I had specified that the SharePoint installation location should be different to… Continue Reading →

Cloudy with a Chance of Insights

In-depth cloud tech discussions from Microsoft experts.

Reaching for the Cloud

Expert insights on Microsoft Azure, cloud architecture, and enterprise technology.

Subscribe on Site →Subscribe on LinkedIn →
← View All Posts