Hi All,<o:p></o:p>
We initially had4 WFEs, 1 Application server which has workflow manager and1 DB. 4WFEs have workflow client. Workflows were working that till May 2015.
Last month we expanded the farm and added 1 WFE, 2 Application server (1 for dedicated distributed cache server and 1 dedicated search server) and1 DB.
We also applied some SharePoint CUs after expanding with new servers. <o:p></o:p>
Around 2 weeks back users reported that workflows are not working and received following errors.
- SPD 2013 publishing error.
Users get this error while publishing error.
Errors were found when compiling the workflow. The workflow files were saved but cannot be run.System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8
of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were:
'<!DOCTYPE html>"
![]()
- Suspended status on UI.
User also get this error.
Go to workflow instance of that record and under the Running Workflows section. Click on your workflow name. You can see the “Workflow getting Suspended.
- Troubleshooting steps 3.1 Tried following Blog and
this blog. All results were positive.
3.2 We installedworkflow client on new servers and exported the Workflow Certificate from existing Application server andimported to new servers. However, we are still getting error same error as mentioned above.
3.3 As next step of follow SharePoint’s CU should be in sync as
described here.
Performed in the IIS Reset. But still get error as mentioned above.
3.4Found a blog that mentioned suspended site features
Workflow Task Content Type feature andWorkflows can use app permissions.
The Workflows can use app permissions feature wasnot activated. So we activated the feature and received an “An unexpected error occurred” with correlation ID.
In the ULS Logs, we received a lot of error as described here.
Feature receiver assembly 'Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c', class 'Microsoft.SharePoint.WorkflowServices.SPAppOnlyPolicyManagerFeatureReceiver', method 'FeatureActivated' for feature 'ec918931-c874-4033-bd09-4f36b2e31fef' threw an exception: System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8).
Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type 'System.Web.HttpUnhandledException' was thrown. System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8).
Feature Activation: Threw an exception, attempting to roll back. Feature 'WorkflowAppOnlyPolicyManager' (ID: 'ec918931-c874-4033-bd09-4f36b2e31fef').
Application error when access /_layouts/15/ManageFeatures.aspx, Error=The remote server returned an error: (500) Internal Server Error.
at System.Net.HttpWebRequest.GetResponse()
System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html>
Failed on try1 to load XML document
at path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Features\PowerView\feature.xml
Failed on try2 to load XML document
at path 'C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Template\Features\ReportServerStapling\feature.xml':
Exception returned from back end service. System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder, be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '
Feature Activation: Threw an exception, attempting to roll back. Feature 'WorkflowAppOnlyPolicyManager' (ID: 'ec918931-c874-4033-bd09-4f36b2e31fef').
In 4 WFEs, there are additional features such as
- PowerView, ReportServer, etc. which are not available in new WFE that we have added to farm. and there are lot of missing feature definitions in this Workflows can use app permissionsfeature.
- There are couple of errors: System.ServiceModel.ProtocolException: The content type text/html; charset=utf-8 of the response message does not match the content type of the binding (application/soap+xml; charset=utf-8). If using a custom encoder,
be sure that the IsContentTypeSupported method is implemented properly. The first 1024 bytes of the response were: '<!DOCTYPE html>
- An application error: Application error when access /_layouts/15/ManageFeatures.aspx, Error=The remote server returned an error: (500) Internal Server Error. at
System.Net.HttpWebRequest.GetResponse()
- Exception returned from back end service. System.ServiceModel.ProtocolException:
Q: Can we copy the missing features from exisiting WFE that to new WFE? Any impact of this action.
Q: What could be potential reason that's workflows had stopped after we expanded the servers?
Q:Does reinstalling workflow manager advisable?
Any advice will be highly appreciated.
Thanks.
Sandy