While troubleshooting a Workflow 2013 Farm outage I noticed the below event log errors. The fix was to execute Workflow 2013 PowerShell cmdlets to “sync” the binary front end with SQL database backend. Similar to how SharePoint Config Wizard does this after CU EXE installation with SharePoint Farms, we may need to run similar “SPFarmUprgade” steps for Workflow 2013 Farms.
Cheers!
Resolution
# Update Service Bus Farm Database $mycert = ConvertTo-SecureString -string "workflow-farm-password-here" -Force –AsPlainText $mypassword = ConvertTo-SecureString -string "workflow-farm-password-here" -Force –AsPlainText $sbfarm = Get-SBFarm Remove-SBHost Invoke-SBFarmUpgrade -SBFarmDBConnectionString $sbfarm.SBFarmDBConnectionString -CertificateAutoGenerationkey $mycert Add-SBHost -SBFarmDBConnectionString $sbfarm.SBFarmDBConnectionString -RunAsPassword $mypassword -EnableFirewallRules $false -CertificateAutoGenerationKey $mycert
Symptom
Microsoft.ServiceBus – 102
The description for Event ID 102 from source Microsoft.ServiceBus cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An unrecoverable error occurred. For diagnostic purposes, this English message is associated with the failure: ‘Messaging Host Aborted’.
at Microsoft.ServiceBus.Common.ExceptionTrace.TraceFailFast(String message, EventLogger logger)
at Microsoft.ServiceBus.Common.ExceptionTrace.TraceFailFast(String message)
at Microsoft.ServiceBus.Common.Fx.AssertAndFailFastService(String description)
at Microsoft.Cloud.ServiceBus.MessageContainerHost.MessageContainerHostComponent.Abort()
at Microsoft.Cloud.HostingModel.ComponentHost.CloseComponent(IComponent component, RequestTracker tracker)
at Microsoft.Cloud.HostingModel.ComponentHost.Close()
at Microsoft.ServiceBus.MessageBroker.Backend.OnStart(String[] args)
at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
Microsoft.ServiceBus.MessageBroker
24680
Application Error – 1000
Faulting application name: Microsoft.ServiceBus.MessageBroker.exe, version: 2.0.30904.0, time stamp: 0x5227aa71
Faulting module name: KERNELBASE.dll, version: 6.2.9200.21815, time stamp: 0x56eafa38
Exception code: 0xe0434352
Fault offset: 0x0000000000024650
Faulting process id: 0x2d9c
Faulting application start time: 0x01d29d7381132061
Faulting application path: C:\Program Files\Service Bus\1.1\Microsoft.ServiceBus.MessageBroker.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: bfa8f2cc-0966-11e7-9482-0050569927e2
Faulting package full name:
Faulting package-relative application ID:
