SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL
SharePoint, Office 365, Azure, and Front end JS geek. – Chicago IL

Workflow

FIXED – Nintex Workflow “The specified string not in the form required for an e-mail address”

Recently I came across this error, could not find a resolution on discussion boards, and wanted to share.

When using multiple Workflow Variables (TO, CC, CC2, CC3) with Send Mail action, you should NOT have any semi colon at the start or end of each string variable.

Feel free to reference multiple Workflow Variables when composing Send Mail action, but be sure to truncate recipient values neatly with semi-colons ONLY between values, and never at the prefix or suffix.

Cheers! 

shades_smile

Bad Values  (Leading or Trailing)

“jdoe@company.com; user2@company.com;”

“;jdoe@company.com; user2@company.com;”

“;jdoe@company.com; user2@company.com”

Good Values (Between Only)

“jdoe@company.com; user2@company.com”

Screenshot

image
image

FIXED – Workflow Manager Backend – Error 1067 / HTTP 500

Recently I came across Workflow errors and resolved by manually executing TSQL to update Workflow Resource and Workflow Instance tables.  Wild but true.  The SQL files can be found on the C:\ drive of the Workflow Manager server.  After running SQL, the windows service promptly started.

Details below on the error symptom and resolution.  Cheers! 

shades_smile

Error Symptoms

  1. Windows Service.  Error 1067 – The process terminated unexpectedly.
  2. HTTP 500 – Internal Server Error Occurred when opening http://workflow:12291 or https://workflow:12290 in a web browser
  3. Register-SPWorkflowService : An internal error occured. For more details, please see the server logs. Client ActivityId :3033487b-7c53-4f17-ae08-8516c2ec0bef.

Resolution

  1. RDP to Workflow Manager
  2. Open “C:\Program Files\Workflow Manager\1.0\Workflow\” folder
  3. Open file “wfServerUpgradePolicy.config” and look for <wfupgrade targetVersion=”1.3.0.0”>
  4. Open SQL and execute “SELECT * FROM [StoreVersionTable]” on [WFResourceManagementDB]
  5. Compare CONFIG file to to SQL table versions
    1. They mismatch.  This the root cause of errors above.
  6. Open “C:\Program Files\Workflow Manager\1.0\Workflow\” folder
  7. Execute SQL scripts to update
    1. WorkflowServiceInstanceManagementDBUpgradeScript.sql
    2. WorkflowServiceResourceManagementDBUpgradeScript.sql
  8. Register-SPWorkflowService -SPSite http://sharepoint -WorkflowHostUri http://workflowserver:12291 -AllowOAuthHttp -Force
  9. Test to verify

Error Screenshots

image
image
image

Resolution Screenshots

image
image
image
image
image
image
image
image
enter image description here

Reference

FIXED – Workflow 2013 Suspended (Event ID 563) – No valid outbound signing keys were found

Recently I came across a condition where Workflow 2013 instance were not running.   Root cause was a missing outbound certificate.   Below are screenshots and PowerShell steps to resolve.  No Windows service restart, reboot, or IISRESET was needed.   Just apply config and test again.  Cheers!

shades_smile

Resolution Steps

1) Verify outbound certificate missing.  Expect $oc to be null.

2) Locate thumbprint of certificate with most forward expiration

3) Apply thumbprint and certificate

4) Test by running Workflow 2013.  Open web browser and click WF2013 test to run again.   Verify completed without errors.  Bonus points if the workflow has an email step and you receive the email OK.

Errors

  • EventID 563: Private key certificate with thumbprint ‘F4545D83AE81EBA21996B139BB44E614145F9057’ could not be found in the local machine certificate store. This may cause failures for running workflows which depend on this certificate.
  • Details: An unhandled exception occurred during the execution of the workflow instance.  Exception details: System.InvalidOperationexception: No valid outbound signing keys were found. at Microsoft.Activities.Hosting.Runtime.Subroutine.SubroutineChild.Execute(CodeActivityContext context) at System.Activities.CodeActivity.InternalExecute (ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager) at System.Activities.Runtime.ActivityExecutor.Execute.ActivityWorkItem.ExecuteBody (ActivityExecutor exectore, BookmarkManager bookManager, Location resultLocation)

Screenshots

clip_image001
clip_image001[6]
image
clip_image001[8]
image
image

References

FIXED – Workflow Endpoint Not Found Exception: Unable to connect to the remote service

Recently I noticed the below error when viewing Workflow status on SharePoint Server 2013.   Root cause turned out to be a missing IIS binding for both HTTP: 12291 and HTTPS: 12290.   After adding the additional IIS binding the status page was able to render again.  Cheers!

shades_smile

Error

Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> Microsoft.Workflow.Client.WorkflowEndpointNotFoundException: Unable to connect to the remote service at http://sharepointwf:12291/SharePoint/default/c1740af1-82ad-4026-beb5-c6eddaea7d88/4d2c8da0-a0da-41c1-8387-96260df02a62/$Workflows/$Instances/4d10f51f-2e21-4ff7-aa3c-ceadde059a14. See InnerException for more details. Client ActivityId : 69ee049e-ffb2-209a-6826-71aedbaa6db7. —> System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:12291   
  at System.Net.Sockets.Socket.EndConnect(IAsyncResult asyncResult)   
  at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Exception& exception)     –
— End of inner exception stack trace —   
  at Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result)

Screenshots

image
image
image
image

© Copyright 2016
@ SPJeff

Return to Top ▲Return to Top ▲