January 23, 2018

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!

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

January 18, 2018

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!

Error Symptoms

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

Resolution

RDP to Workflow Manager
Open “C:\Program Files\Workflow Manager\1.0\Workflow\” folder
Open file “wfServerUpgradePolicy.config” and look for <wfupgrade targetVersion=”1.3.0.0”>
Open SQL and execute “SELECT * FROM [StoreVersionTable]” on [WFResourceManagementDB]
Compare CONFIG file to to SQL table versions

They mismatch. This the root cause of errors above.

Open “C:\Program Files\Workflow Manager\1.0\Workflow\” folder
Execute SQL scripts to update

WorkflowServiceInstanceManagementDBUpgradeScript.sql
WorkflowServiceResourceManagementDBUpgradeScript.sql

Register-SPWorkflowService -SPSite http://sharepoint -WorkflowHostUri http://workflowserver:12291 -AllowOAuthHttp -Force
Test to verify

Error Screenshots

Resolution Screenshots

Reference

https://sharepoint.stackexchange.com/questions/196303/workflow-manager-backend-stop-after-insalling-cu3-update

October 3, 2017

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!

Resolution Steps

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

Import-Module WorkflowManager
$wf = Get-WFFarm
$oc = Get-WFOutboundCertificate $wf.Endpoints[0]
$oc
# Expect to be NULL (MISSING)

2) Locate thumbprint of certificate with most forward expiration

gci Cert:\Local Machines\My | sort subject | select thumbprint,subject,notafter | ft

3) Apply thumbprint and certificate

Set-WFNextOutboundCertificateReference -ServiceUri $wf.Endpoints -Thumbprint [ADD REAL CERT THUMBPRINT HERE]
Set-WFNextOutboundCertificateAsCurrent
$oc = Get-WFOutboundCertificate $wf.Endpoints[0]
$oc
# Expect to be NOT NULL (SHOW THUMBPRINT)

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)