Workflow Manager Cumulative Update (February) error

Question

Hi,
I've downloaded and installed
Workflow Manager 1.0 Cumulative Update and
Service Bus 1.0 Cumulative Update. But after installing the updates, I can't access the Library workflow settings page. I'm getting unexpected error. Then after investigating the workflow manager log in event viewer, I've found the following error messages:
The asynchronous operation has completed with an exception. Exception message is: System.Data.SqlClient.SqlException (0x80131904): The EXECUTE permission was denied on the object 'InsertTrackingAndStatus', database 'DEV_WFInstanceManagementDB', schema 'dbo'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
   at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)
   at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult)
   at Microsoft.Workflow.Management.ExecuteNonQueryAsyncResult.OnEndExecuteSql(IAsyncResult result)
   at Microsoft.Workflow.Management.ExecuteSqlAsyncResult.EndAsyncResult(IAsyncResult result)
   at Microsoft.Workflow.Common.BackoffRetryAsyncResult.IsolateWithRetry(IAsyncResult result)
   at Microsoft.Workflow.Common.AsyncResult.AsyncCompletionWrapperCallback(IAsyncResult result)
ClientConnectionId:2f93882a-8d4c-440d-a3ff-0bd9d1682ad2.
The issue I've found in my Dev environment with Windows Server 2008 R2 SP 1. This is standalone SharePoint farm with DC, SQL Server and SharePoint all installed in the same server. One workaround I have found that if I add the WF user as dbo to the database
as well as  'WFServiceOperators' then the error disappear.
Thanks,
Sohel Rana
http://ranaictiu-technicalblog.blogspot.com

Answer 1

I ran the provided SQL script on our Workflow Manager databases. I commented out the EXEC line and added a 'PRINT @Cmd'. This allowed me to view the actual commands the script would execute. These commands were generated:
GRANT EXECUTE ON [AddDbUserToRole] TO [WFServiceOperators]
GRANT EXECUTE ON [AddLoginAndUser] TO [WFServiceOperators]
GRANT EXECUTE ON [AddUserToServiceAdmins] TO [WFServiceOperators]
GRANT EXECUTE ON [AddUserToServiceOperators] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[DebugTraceRecordValues] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteExpiredInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteInstancesByScopeId] TO [WFServiceOperators]
GRANT EXECUTE ON [DeleteSystemInstances] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[EntityIds] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[EntityNames] TO [WFServiceOperators]
GRANT EXECUTE ON [FormatNTGroupName] TO [WFServiceOperators]
GRANT EXECUTE ON [GetDebugTraces] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceCount] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceDebugTraces] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceDebugTracesByWorkflowId] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceMetadata] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstancesById] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstancesByWorkflowId] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceStatusHistory] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceStatusHistoryRecordsByWorkflowId] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstancesToRestore] TO [WFServiceOperators]
GRANT EXECUTE ON [GetInstanceTelemetryData] TO [WFServiceOperators]
GRANT EXECUTE ON [GetMappedVariables] TO [WFServiceOperators]
GRANT EXECUTE ON [GetStatusHistory] TO [WFServiceOperators]
GRANT EXECUTE ON [GetStillReferencedWorkflows] TO [WFServiceOperators]
GRANT EXECUTE ON [GetStoreVersion] TO [WFServiceOperators]
GRANT EXECUTE ON [GetSystemInstances] TO [WFServiceOperators]
GRANT EXECUTE ON [GetUpdatedInstances] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[Guids] TO [WFServiceOperators]
GRANT EXECUTE ON [HasPermissionToPerform] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertInstanceDebugTraceRecords] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertInstanceStatusHistoryRecords] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertNotStartedInstanceRecord] TO [WFServiceOperators]
GRANT EXECUTE ON [InsertTrackingAndStatus] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[InstanceStatusValues] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[MetadataValues] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[MetadataValuesWithInstanceId] TO [WFServiceOperators]
GRANT EXECUTE ON [OnInstanceEndedWithStatusDetail] TO [WFServiceOperators]
GRANT EXECUTE ON [OverrideTrackingAndStatus] TO [WFServiceOperators]
GRANT EXECUTE ON [ResetInstancesToNotStarted] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[StatusHistoryRecordValues] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[TrackingRecordValues] TO [WFServiceOperators]
GRANT EXECUTE ON [UpdateInstanceWorkflowStatus] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[Variables] TO [WFServiceOperators]
GRANT CONTROL, REFERENCES ON TYPE::[WorkflowIds] TO [WFServiceOperators]
I ran the script against both 'WFInstanceManagementDB' and 'WFResourceManagementDB'. I also ran it against 'WFManagementDB', but the script didn't generate any GRANT commands for that database.
So I enabled the EXEC command and reran the script against both databases. Almost immediately I could see a drop in CPU utilization on our workflow server. Also the errors disappeared from the Event Log. To be safe I also rebooted the server.
This seems to have fixed our problem. I'd still like to have an official KB article or update for this problem, though.