After installing Dec 14 CU and updating the WF farm to CU2 I tried to run the cmdlets as per here - https://technet.microsoft.com/en-us/library/dn133867.aspx?f=255&MSPPError=-2147217396
$credential = [System.Net.CredentialCache]::DefaultNetworkCredentials
$site = Get-SPSite https://teams.sharepoint.com
$proxy = Get-SPWorkflowServiceApplicationProxy
$svcAddress = $proxy.GetWorkflowServiceAddress($site)
Copy-SPActivitiesToWorkflowService -WorkflowServiceAddress $svcAddress -Credential $credential -Force $true
This errors:
Copy-SPActivitiesToWorkflowService : An internal error occured. For more details, please see the server logs. Client
ActivityId : cb2a40af-2c50-4e5c-8ac2-c5436c351b89.
At line:1 char:1
+ Copy-SPActivitiesToWorkflowService -WorkflowServiceAddress $svcAddress -Credenti ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (Microsoft.Share...WorkflowService:CopySPActivitiesToWorkflowService) [Copy
-SPActivitiesToWorkflowService], InternalServerException
+ FullyQualifiedErrorId : Microsoft.SharePoint.WorkflowServices.PowerShell.CopySPActivitiesToWorkflowService
I then ran get-WFFarmstatus on the WF server (3 in the farm) and see that the service is stopped on all the WF servers with a warning:
WFserver1 WorkflowServiceBackend
Stopped
WARNING: Endpoint https://WFserver1:12290/ is not responding: The remote server returned anerror: (500) Internal Server Error.
WFserver1 WorkflowServiceFrontEnd
Stopped
Checked the underlying services and IIS on the 3 WF servers and these are all now started but the WF service cannot be started:
net start WorkflowServiceBackend
The Workflow Manager Backend service is starting.
The Workflow Manager Backend service could not be started.
A system error has occurred.
System error 1067 has occurred.
The process terminated unexpectedly.
The WF operational logs show this:
Unhandled exception in AppDomain:
Microsoft.Workflow.Common.FatalException: An unrecoverable error occurred. For
diagnostic purposes, this English message is associated with the failure: 'A
required Workflow Manager configuration
'WorkflowServiceScopeSnapshotProcessBatchSize' is not present. Please add this
configuration value.'. ---> System.IO.InvalidDataException: A required
Workflow Manager configuration 'WorkflowServiceScopeSnapshotProcessBatchSize'
is not present. Please add this configuration value. <o:p></o:p>
at
Microsoft.Workflow.Common.AsyncResult.End[TAsyncResult](IAsyncResult result) <o:p></o:p>
at
Microsoft.Workflow.Service.WorkflowServiceBackendHost.OnStartCompleted(IAsyncResult
result) <o:p></o:p>
There is a suggested fix for this here -
http://www.guideushow.com/sharepoint/solved-workflowservicescopesnapshotprocessbatchsize-is-not-present/
(http://www.guideushow.com/sharepoint/solved-workflowservicescopesnapshotprocessbatchsize-is-not-present/)
<o:p></o:p>
Id like to at least get some feedback as to whether this is safe/supported (MS doesnt like
any tinkering with the DBs) or whether we should go down the uninstall/reinstall
the Workflow farm route - thanks
J
- Edited by jonjames 23 hours 36 minutes ago more detail and formatting
Other recent topics
