0
0 Comments

Hi All,

Background: 
In our environment has an Application server and Workflow Manager installed on the same server (AppsSrv.company.com). The hostname of server is AppsSrv.  Workflow Manager works well.

Problem:
A month ago, there an issue on one of the services and application server was renamed from AppsSrv (Server Name) to AppsSrv.company.com (FQDN). The workflow manager does not seem to work anymore with renamed application server.

Troubleshooting:
A user reported an issue where a SharePoint Designer 2013 has been deployed to SharePoint server.    And when custom workflow’s Internal status is SUSPENDED and have the follows status:

Requestorid: <<GUID>> Details: An unhandled exception occurred during the execution of the workflow instance. Exception Details: System.ApplicationException: HTTP 500 The remote server returned an error: (500) Internal Server Error.

To reproduce the issue, we created a simple Site Workflow reproduce the issue and used a SPD 2013. While publishing the workflow we got an 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>

Followed the troubleshooting steps http://blogs.msdn.com/b/laleh/archive/2014/09/03/sharepoint-2013-workflow-troublehsooting.aspx

  1.  We checked the Workflow status health
    get-WFfarm
    get-WFfarmStatus and Service Status is Running for WorkflowServiceBackend and WorkflowServiceFrontend
  2.  In Application server, Workflow Proxy shows Workflow is connected.
  3.  All the workflow services are running.
  4.  UPS, App Management services are STARTED and in Platform type shows SharePoint 2013 workflow.
  5. Verified https://appsSrv.company.com:12290/ and its active.
  6. We have tried this blogspot http://sharepoint-community.net/profiles/blogs/sharepoint-2013-workflow-manager-possible-issues-and-fixes  and tried Resolution 3

    Register-SPWorkflowService -SPSite “https://sp2013.company.com/” -WorkflowHostUri “https://appsSrv0sf.company.com:12290/” – AllowOAuthHttp -Force -ScopeName “SharePoint”

    but it did not work.

  7. Also tried the following troubleshooting http://blogs.msdn.com/b/vincent_runge/archive/2014/01/07/troubleshooting-actions-for-sharepoint-2013-workflows.aspx  but most of results were positive.

Q) If we rename the application server which hosts Workflow manager, will Workflows will work?
Q) What there steps we can resolve the issue?

Any help would be greatly appreciated.

Thank you.
Aroh

 

(Visited 308 times, 1 visits today)
Add a Comment