Business Data Connectivity Service - BDC validation of Workflow entity failed - Event 3016 (Duet Enterprise)
Applies to: Duet Enterprise for Microsoft SharePoint and SAP
Topic Last Modified: 2012-04-26
Alert Name: Business Data Connectivity Service - BDC validation of Workflow entity failed
Event ID: 3016
The BDC model that is associated with an SAP workflow contains metadata and methods that the SAP application requires to communicate with and run in SharePoint solutions. The BDC model that is associated with the SAP workflow defines the entity for the workflow. The validation of the workflow entity failed.
The workflow entity in a BDC model for an SAP workflow must have the following six fields in this specific order: Action, CorrelationId, Comments, ParentId, Outcome, ReassignedTo. The value of the ParentID field identifies the workflow entity in the BDC model. The Updater method in the BDC model is called when a user updates an SAP workflow. The BDC workflow entity that is configured to be used by an SAP workflow must define an identifier field of type String. The Updater method must also take this field as input as the fourth parameter. Also, the input parameter of the UpdateWorkflow method must be a nested type.
The following symptoms might appear:
On the workflow site, new tasks cannot be created for a SAP workflow application and existing tasks cannot be approved.
This event appears in the event log:
Event ID: 3016 Description: Business Data Connectivity Service endpoint validation failed. TaskParent end point BDC method input parameter should be nested and should have an identifier defined.
One or more of the following might be the cause:
The Business Data Connectivity service application is not installed or is not started.
A required field in the workflow entity of the BDC model was not found, or the Updater method in the BDC model specifies the ParentID field that is not the identifier for a workflow entity.
On the Central Administration Home page, click Application Management.
On the Application Management page, in the Service Applications section, click Manage service applications.
On the Service Applications page, find the Business Data Connectivity Service Application, and in the Status column, verify that the service proxy status is Started.
|This procedure is supported with BDC models that are provided with Duet Enterprise only. Do not use this procedure to import a custom BDC model. For more information, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/p/?LinkId=200925).|
Follow the procedure for importing the BDC models that are provided for all solutions that are provided with Duet Enterprise. For more information, see Import models (http://go.microsoft.com/fwlink/p/?LinkId=203586). For more information about how to import a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/p/?LinkId=200925). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/p/?LinkID=203587).
Use Microsoft SharePoint Designer 2010 to create a new external content type and import the new BDC model. For more information, see Creating SharePoint Server 2010 External Content Type Associations Using SharePoint Designer 2010 (http://go.microsoft.com/fwlink/p/?LinkId=203862).