| | DisplayName | Description | ID | Target | Parent Monitor | Category | Enabled | Instance Name | Counter Name | Frequency | Alert Generate | Alert Severity | Alert Priority | Alert Auto Resolve | Monitor Type | Remotable | Accessibility | RunAs |
|---|
 | Workflow: Cannot resolve account to activate SAP workflow | Summary
When an SAP Workflow is configured, a specified user account (service account) is used for all workflow transactions between SharePoint Server 2010 and the SAP environment. The SAP system uses this account to send workflow tasks to the computer running SharePoint Server. This user account will also be added as a member of the SAP Workflow Trusted Users group on the workflow site.
Symptoms
The following symptoms might appear:
Activation of the Duet Enterprise workflow feature failed.
This event appears in the event log:
Event ID: 3010 Description: Cannot add the configured service account user to the group <SAP Workflow Trusted Users>.
Cause
The service account that was specified for the SAP workflow cannot be resolved on the Web application where the SAP workflow is being activated.
Resolution
Specify the service account for workflowFollow the instructions in Configure SAP Workflows (http://go.microsoft.com/fwlink/?LinkId=205816) to specify the user service account that will be used for all workflow transactions between SharePoint Server and the SAP system. | Microsoft.SharePoint.DuetE.CannotAddCurrentUserToTrustedGroup | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Role sync: User profiles could not be updated with list of deleted SAP users | Summary
Microsoft Business Connectivity Services provides a connector for communication between SharePoint Server and the SAP environment. The Duet Enterprise Profile Synchronization timer job uses the Business Data Connectivity service to retrieve the list of deleted SAP users from the SAP system and subsequently update the User Profile store by clearing the SAP Roles property for the deleted SAP users. Business Connectivity Services could not retrieve the list of deleted SAP users.
Symptoms
The following symptoms might appear:
The Duet Enterprise Profile Synchronization timer job fails.
This event appears in the event log:
Event ID: 5007 Description: Could not retrieve deleted users information from backend. The exception message is <message>.
Cause
One or more of the following might be the cause:
Transient connectivity problems that are caused by high server load on the SAP system.
The process account for the SharePoint 2010 Timer (SPTimerV4) service does not have Execute permissions on the BDC UserRoles model.
Resolution
Grant permissions on the BDC UserRoles model
1.Verify that you have the following administrative credentials:
You must be a member of the Farm Administrators group.
2.Follow the instructions in Manage user access to BDC models (http://go.microsoft.com/fwlink/?LinkID=201163) to grant the process account for the SharePoint 2010 Timer service Execute permissions on the BDC UserRoles model.
Synchronize user profile information
1.Follow the instructions in Perform nonrecurring profile synchronization (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkID=201163) to synchronize user profile information between Active Directory Domain Services (AD DS) and SharePoint Server 2010.
Configure the following:
a. Verify that you have the following administrative credentials:
You must be a member of the Farm Administrators group or administrator of the User Profile Service Application.
b. On the User Profile Service Application page, in the Synchronization section, click Start Profile Synchronization.
c. On the Start Profile Synchronization page, select whether you want to perform an incremental or full synchronization, and then click OK. | Microsoft.SharePoint.DuetE.DeletedUsersInfoRetrievalFailed | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.RoleSyncServerMonitor | AvailabilityHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Role sync: Roles in SAP and User Profile Store are not synchronized | Summary
Duet Enterprise users and their roles are synchronized with the SAP system and stored in the User Profile Service’s profile store. A function of the synchronization process is to retrieve the list of deleted SAP roles from the SAP system and update the User Profile store by clearing the SAP Roles property for the deleted SAP users. The Duet Enterprise Profile Synchronization timer job initiates the synchronization of the users in the SharePoint User Profile Store to mapped roles in the SAP system. The Timer Service service account running Duet Enterprise Profile Synchronization must have full control permissions to the User Profile Service application.
Symptoms
This event appears in the event log:
Event ID: 5008 Description: SAP Roles of users deleted from backend could not be updated.
Cause
One or more of the following might be the cause:
A network connectivity issue or transient SAP back-end errors occurred.
The User Profile Service application is not running.
The timer job account does not have full control permissions to the User Profile Service application.
For more information about how to provide managed accounts permissions to a service application administrator for a specific User Profile Service application, see Assign administration of a User Profile service application (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=204625).
The DeletedIDEnumerator method in the BDC model that is associated with role synchronization, and that retrieves the deleted users from backend, failed. The SharePoint administrator might not have sufficient permission on the BDC model to execute this method.
Resolution
Verify network connectivity and SAP back-end connectivityPing the servers in the remote farm to ensure that they are available. Ask the administrator of the remote farm to ping the servers in your farm.
Note:
Contact the SAP administrator and verify that there are no connectivity issues on the SAP system.
Start the User Profile service
1.Confirm that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
2.On the SharePoint Central Administration Web site, click System Settings.
3.On the System Settings page, in the Servers section, click Manage services on server.
4.Click Start in the Action column for the User Profile Service.
5.Click OK to start the service.
Verify the service account
1.Verify that the user account that is performing this procedure is a member of the Administrators group on the local computer.
2.Click Start, point to Administrative Tools, and then click Services.
3.In the Services snap-in, right-click the Windows SharePoint Services Timer V4 service, and then click Properties.
4.In the Service Properties dialog box, on the Log On tab, type the password for the account, confirm the password, and then click OK.
5.Right-click the service, and then click Start.
Verify access to the User Profile Service Application
1.On the Central Administration Home page, in the Application Management section, click Manage service applications.
2.On the Manage Service Applications page, click the row that contains the User Profile Service Application that was deployed for Duet Enterprise.
The User Profile Service Application for your installation of Duet Enterprise is specified in the Duet EnterpriseDuetConfig.config file.
3.In the Sharing group of the Ribbon, click Permissions.
4.In the Connection Permissions dialog box, do one of the following:
If the timer job account appears in the middle pane, click the user account.
If the timer job account does not appear in the middle pane, type the user account in the top pane, and then click Add.
5.In the bottom pane, verify that the Full Control check box is selected.
6.Click OK.
For more information, see Restrict or enable access to a service application (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkID=202009). | Microsoft.SharePoint.DuetE.DeletedUsersRolesNotUpdated | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.RoleSyncServerMonitor | AvailabilityHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Role sync: Updated SAP user profiles could not be retrieved | Summary
Duet Enterprise Profile Synchronization uses Microsoft Business Connectivity Services for communication between Microsoft SharePoint Server 2010 and the SAP environment. The Duet Enterprise Profile Synchronization timer job retrieves the list of updated SAP roles from the SAP system and updates the SAP Roles property in the User Profile store for all SAP users. Business Connectivity Services could not communicate with the SAP system and retrieve the list of updated SAP roles.
Symptoms
The following symptoms might appear:
The Duet Enterprise Profile Synchronization timer job fails.
This event appears in the event log:
Event ID: 5003 Description: Could not retrieve roles from backend. The exception message is <message>.
Cause
One or more of the following might be the cause:
Transient connectivity problems that are caused by high server load on the SAP system.
The process account for the SharePoint 2010 Timer (SPTimerV4) service does not have Execute permissions on the BDC UserRoles model.
Resolution
Grant permissions on the BDC UserRoles model
1.Verify that you have the following administrative credentials:
You must be a member of the Farm Administrators group.
2.Follow the instructions in Manage user access to BDC models (http://go.microsoft.com/fwlink/?LinkId=204089) to grant the process account for the SharePoint 2010 Timer service Execute permissions on the BDC UserRoles model.
Verify the SharePoint 2010 Timer service accountYou must provide the SAP administrator with the user account that is assigned to the SharePoint 2010 Timer service, also known as the SPTimerV4 service. The SAP administrator must ensure that this account is mapped to an SAP user who is granted sufficient permissions on the SAP system to query the UserRoles assignments query. To learn how to get the user account for the SharePoint 2010 Timer service, see Synchronize profiles and roles (http://go.microsoft.com/fwlink/?LinkId=205815).
Synchronize user profile information1.Follow the instructions in Perform nonrecurring profile synchronization (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkID=201163) to synchronize user profile information between AD DS and SharePoint Server 2010.
Configure the following:
a. Verify that you have the following administrative credentials:
You must be a member of the Farm Administrators group or administrator of the User Profile Service Application.
b. On the User Profile Service Application page, in the Synchronization section, click Start Profile Synchronization.
c. On the Start Profile Synchronization page, select whether you want to perform an incremental or full synchronization, and then click OK. | Microsoft.SharePoint.DuetE.RoleSync.RolesRetrievalFailed | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.RoleSyncServerMonitor | AvailabilityHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Role Sync: Service context for the User Profile Service application not found | Summary
When a Farm Administrator runs the Duet Enterprise Profile Synchronization Timer job, the job determines if the associated User Profile Service application is accessible. This is important for execution. The Timer Job could not find the service context for the User Profile Service application. The SharePoint Timer Service service account running Duet Enterprise Profile Synchronization must have Full Control permissions to the User Profile Service application.
Symptoms
The following symptoms might appear:
The Duet Enterprise Profile Synchronization timer job fails.
This event appears in the event log:
Event ID: 5001 Description: User Profile Service Context corresponding to the <User Profile Service application> could not be found. The exception message is <message>.
Cause
One or more of the following might be the cause:
The User Profile Service application has not been created.
The User Profile Service is not running.
The Timer Job account does not have Full Control permissions to the User Profile Service application.
For more information about how to provide managed accounts permissions to a service application administrator for a specific User Profile service application, see Assign administration of a User Profile service application (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkID=204625).
Resolution
Start the User Profile service
1.Confirm that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
2.On the SharePoint Central Administration Web site, click System Settings.
3.On the System Settings page, in the Servers section, click Manage services on server.
4.Click Start in the Action column for the User Profile Service.
5.Click OK to start the service.
Create a User Profile Service applicationTo learn how to create a User Profile Service application, see Create, edit, or delete a User Profile service application (http://go.microsoft.com/fwlink/?LinkId=207520).
Verify access to the User Profile Service Application
1.On the Central Administration Home page, in the Application Management section, click Manage service applications.
2.On the Manage Service Applications page, click the row that contains the User Profile Service Application.
3.In the Sharing group of the ribbon, click Permissions.
4.In the Connection Permissions dialog box, do one of the following:
If the Timer Job account appears in the middle pane, click the user account.
If the Timer Job account does not appear in the middle pane, type the user account in the top pane, and then click Add.
5.In the bottom pane, verify that the Full Control check box is selected.
6.Click OK.
For more information, see Restrict or enable access to a service application (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkID=202009). | Microsoft.SharePoint.DuetE.RoleSync.UPAServiceContextNotFound | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.RoleSyncServerMonitor | AvailabilityHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Role sync: SharePoint and SAP profile stores could not be synchronized | Summary
The Duet Enterprise Profile Synchronization Timer Job synchronizes user profiles in the SharePoint User Profile Store with SAP Roles over a Business Data Connectivity service connector. This synchronization process stores the SAP roles for each Duet Enterprise user in the SharePoint User Profile Store. The BDC models provided with Duet Enterprise for Microsoft SharePoint and SAP contain the connectivity information and authentication properties for the SAP system. The SAP roles could not be synchronized with the user profiles in SharePoint Server.
Symptoms
This event appears in the event log:
Event ID: 5010 Description: The Role Sync basic validation failed. The exception message is <message>.
Cause
Run DuetConfig with the /CheckConfiguration option to learn about the cause of the error and the recommended resolution.
Resolution
Run DuetConfig
1.Log in to a front-end Web server as a member of the Farm Administrators group.
Tip:
You only have to perform this procedure on one front-end Web server.
2.Open a command prompt as administrator:
Click Start, click All Programs, and then click Accessories.
Right-click Command Prompt and then click Run as administrator.
3.In the Command Prompt window, go to the folder that contains the DuetConfig.exe file. By default, this is the C:\program files\Duet Enterprise\1.0\ folder.
4.Type DuetConfig/CheckConfiguration out checkconfig.xml and then press ENTER.
5.At the command prompt type notepad checkconfig.xml to open the .xml file in Notepad.
You can also choose to open the test.xml file directly in a browser (C:\Program Files\Duet Enterprise\1.0\test.xml).
6.Follow the recommendations in the report to resolve the problem. | Microsoft.SharePoint.DuetE.RoleSync.ValidationFailed | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.RoleSyncServerMonitor | AvailabilityHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Role sync: User profiles not synchronized with updated SAP user roles | Summary
A SharePoint farm administrator synchronizes user profiles in the SharePoint User Profile Store with SAP Roles over a Business Data Connectivity service connector. This synchronization process stores the SAP user accounts and the SAP roles to which they are mapped in the SharePoint User Profile Store. An error during synchronization prevented the update of the user profiles. The SAP Roles of SAP users in the User Profile Store were not updated with the current SAP Roles from the SAP profile store.
Symptoms
The following symptoms might appear:
User profiles of SharePoint users that have mapped SAP user accounts are not updated with changes to the SAP user roles.
This event appears in the event log:
Event ID: 5005 Description: Few profiles couldn't be updated. See the logs for details about the profiles. The exception message is \%1.
Cause
One or more of the following might be the cause:
The User Profile Service application is not running.
The Timer Job account does not have Full Control permissions to the User Profile Service application. For more information about how to provide managed accounts permissions to a service application administrator for a specific User Profile service application, see Assign administration of a User Profile service application (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkID=204625).
Resolution
Start the User Profile service
1.Confirm that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.
2.On the SharePoint Central Administration Web site, click System Settings.
3.On the System Settings page, in the Servers section, click Manage services on server.
4.Click Start the Action column for the User Profile Service.
5.Click OK to start the service.
Verify the service account
1.Verify that the user account that is performing this procedure is a member of the Administrators group on the local computer.
2.Click Start, point to Administrative Tools, and then click Services.
3.In the Services snap-in, right-click the Windows SharePoint Services Timer V4 service, and then click Properties.
4.In the Service Properties dialog box, on the Log On tab, type the password for the account, confirm the password, and then click OK.
5.Right-click the service, and then click Start.
Verify access to the User Profile Service Application1.On the Central Administration Home page, in the Application Management section, click Manage service applications.
2.On the Manage Service Applications page, click the row that contains the User Profile Service Application.
3.In the Sharing group of the ribbon, click Permissions.
4.In the Connection Permissions dialog box, do one of the following:
If the Timer Job account appears in the middle pane, click the user account.
If the Timer Job account does not appear in the middle pane, type the user account in the top pane, and then click Add.
5.In the bottom pane, verify that the Full Control check box is selected.
6.Click OK.
For more information, see Restrict or enable access to a service application (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkID=202009). | Microsoft.SharePoint.DuetE.RoleSyncProfileNotUpdated | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.RoleSyncServerMonitor | AvailabilityHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - BDC metadata not found | Summary
The Duet Enterprise SharePoint Add-on and Duet Enterprise SAP Add-ons utilize the Microsoft Business Connectivity Services to enable communication between SharePoint Server 2010 and the SAP environment. The BDC model that is associated with the SAP workflow contains metadata that the SAP workflow requires to connect to SharePoint solutions. The SAP workflow cannot find a metadata element in the associated BDC model that it requires to run.
Symptoms
The following symptoms might appear:
A new SAP workflow task type cannot be configured.
Configuring a new SAP workflow registers a new site to display related tasks, reports, and data.
This event appears in the event log:
Event ID: 3021 Description: Business Data Connectivity Service metadata element(s) specified in task parent endpoint could not be found.
Cause
The metadata in the BDC model that is required by an SAP workflow was not found in the BDC Metadata Store.
Resolution
Import BDC modelsFollow the procedure for importing the BDC models that are provided for all of the solutions that are provided with Duet Enterprise. For more information, see Import models (http://go.microsoft.com/fwlink/?LinkId=203586). For more information about importing a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=200925). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/?LinkID=203587).
Create a new SAP workflowTo create a Workflow site and then specify the SAP Workflow task type for your Workflow site, follow the procedure in Create a Workflow site (http://go.microsoft.com/fwlink/?LinkId=203634). | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BDCArtifactNotFound | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - BDC metadata catalog is not available | Summary
The Duet Enterprise SharePoint Add-on and Duet Enterprise SAP Add-ons utilize the Microsoft Business Connectivity Services to enable communication between SharePoint Server 2010 and the SAP environment. The BDC model that is associated with the SAP workflow contains metadata that the SAP workflow requires to connect to SharePoint solutions. The BDC Metadata Store contains the metadata about the SAP system. The BDC Metadata Store is currently unavailable.
Symptoms
This event appears in the event log:
Event ID: 3011 Description: Business Data Connectivity Service could not be found. Business Data Connectivity Service might be disabled or incorrectly configured.
Cause
The application server is not accessible or the Business Data Connectivity service application is disabled or incorrectly configured.
Resolution
Verify that the Business Data Connectivity service application is provisioned correctly
1.On the Central Administration Home page, click Application Management.
2.On the Application Management page, in the Service Applications section, click Manage service applications.
3.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.
Verify that the application server is available
1.On the Central Administration Home page, in the System Settings section, click Manage servers in this farm.
2.On the Servers in Farm page, verify that the status of the server on which the Business Data Connectivity service runs is No Action Required. | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BdcCatalogNotFound | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - BDC update method parameters do not match Workflow entity fields | Summary
The Duet Enterprise SharePoint Add-on and Duet Enterprise SAP Add-ons utilize the Microsoft Business Connectivity Services to enable communication between SharePoint Server 2010 and the SAP environment. The BDC model that is associated with the 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. An entity describes a collection of data fields.
The Updater method in a BDC model for a SAP workflow must have the following six fields in this specific order: Action, CorrelationId, Comments, ParentId, Outcome, ReassignedTo. The Business Data Connectivity service calls the method in your BDC model when a user updates an SAP workflow. The Updater method must have one input parameter and one return parameter. The input parameter must specify the five mandatory fields in the workflow entity. This event occurs when a field that the Updater method requires is not found.
Symptoms
This event appears in the event log:
Event ID: 3012 Description: Business Data Connectivity Service endpoint validation failed. TaskParent end point bdc method should have one input and one return parameter. The input parameter must have at least 5 mandatory fields.
Cause
A required field in the Updater method of the BDC model was not found.
Resolution
Import BDC modelsFollow the procedure for importing the BDC models that are provided for all of the solutions that are provided with Duet Enterprise. For more information, see Import models (http://go.microsoft.com/fwlink/?LinkId=203586). For more information about how to import a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=200925). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/?LinkID=203587).
Create a new external content type for custom workflow applicationsUse 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/?LinkID=203862). | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BdcEndPointParameterCountMismatch | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - BDC Workflow identifier is not valid | Summary
The value of the ParentID field identifies the workflow entity in a BDC model that is associated with a SAP workflow. 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. This error occurs when the fourth parameter of the Updater method is not defined as identifier.
Symptoms
The following symptoms might appear:
On the workflow site, new tasks cannot be created for an SAP workflow application and existing tasks cannot be approved.
This event appears in the event log:
Event ID: 3013 Description: Business Data Connectivity Service endpoint validation failed. TaskParent end point bdc method input parameter parentId should be defined as an identifier.
Cause
The Updater method in the BDC model specifies the ParentID field that is not the identifier for workflow entity.
Resolution
Import BDC models
Follow the procedure for importing the BDC models that are provided for all of the solutions that are provided with Duet Enterprise. For more information, see Import models (http://go.microsoft.com/fwlink/?LinkId=203586). For more information about how to import a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=200925). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/?LinkID=203587).
Create a new external content type for custom workflow applicationsUse 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/?LinkId=203862). | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BdcEndPointParameterInvalidIdentifier | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - BDC field in Workflow entity not found | Summary
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. This entity must define an Updater type method to update the status of a task from SharePoint Server to the SAP system. The UpdateWorkflow method must define the following parameters in this specific order: Action, CorrelationId, Comments, ParentId, Outcome, ReassignedTo. One of the required fields in the Workflow entity was not found.
Symptoms
The following symptoms might appear:
On the workflow site, new tasks cannot be created for an SAP workflow application and existing tasks cannot be approved.
This event appears in the event log:
Event ID: 3014 Description: Business Data Connectivity Service endpoint validation failed. Could not find parameter. Please refer to the signature of Update workflow method in Business Data Connectivity Service model.
Cause
A required field in the UpdateWorkflow method in the BDC model was not found or is not in the correct order.
Resolution
Import BDC modelsFollow 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/?LinkId=203586). For more information about importing a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=200925). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/?LinkID=203587).
Create a new external content type for custom workflow applications
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/?LinkID=203862). | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BdcEndPointParameterNotFound | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - BDC incorrect data type in update method | Summary
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. This entity must define an Updater type method to update the status of the task from SharePoint Server to the SAP system. The parameters in the UpdateWorkflow method must be of a String data type.
Symptoms
The following symptoms might appear:
On the workflow site, new tasks cannot be created for an SAP workflow application and existing tasks cannot be approved.
This event appears in the event log:
Event ID: 3015 Description: Business Data Connectivity Service endpoint parameter with name: <parameter> should be a string data type.
Cause
A parameter in the UpdateWorkflow method is not a String data type.
Resolution
Import BDC modelsFollow 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/?LinkId=203586). For more information about how to import a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=200925). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/?LinkID=203587).
Create a new external content type for custom workflow applications
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/?LinkID=203862). | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BdcEndPointParameterTypeError | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - BDC validation of Workflow entity failed | Summary
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.
Symptoms
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.
Cause
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.
Resolution
Verify that the Business Data Connectivity service application is provisioned correctly
1.On the Central Administration Home page, click Application Management.
2.On the Application Management page, in the Service Applications section, click Manage service applications.
3.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.
Import BDC models
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/?LinkId=203586). For more information about how to import a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=200925). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/?LinkID=203587).
Create a new external content type for custom workflow applications
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/?LinkId=203862). | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BdcEndPointParameterValidationFailed | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow:Business Data Connectivity Service - BDC is disabled | Summary
The Duet Enterprise SharePoint Add-on and Duet Enterprise SAP Add-ons utilize the Microsoft Business Connectivity Services to enable communication between SharePoint Server 2010 and the SAP environment. Microsoft Business Connectivity Services could not be found on this farm.
Symptoms
The following symptoms might appear:
On the workflow site, new tasks cannot be created for an SAP workflow application and existing tasks cannot be approved.
This event appears in the event log:
Event ID: 3017 Description: Business Data Connectivity Service could not be found on this farm. Business Data Connectivity Service might be disabled or incorrectly configured.
Cause
The Business Data Connectivity service application is not installed or is not started.
Resolution
Verify that the Business Data Connectivity service application is provisioned correctly1.On the Central Administration Home page, click Application Management.
2.On the Application Management page, in the Service Applications section, click Manage service applications.
3.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.
Verify that the application server is available
1.On the Central Administration Home page, in the System Settings section, click Manage servers in this farm.
2.On the Servers in Farm page, verify that the status of the server on which the Business Data Connectivity service runs is No Action Required. | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.BdcServiceNotFound | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: SAP workflow task URL is incorrect for root site | Summary
When an SAP workflow is created or updated, the URL of the SAP workflow site that is passed to SharePoint Server is not a valid SAP workflow rootsite. The SAP workflow site has been deleted or the Duet Enterprise workflow feature is not active on the specified site.
Symptoms
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: 3018 Description: No task workspace for task type <TaskName> and language <LCID> is currently active.
Cause
The URL of the SAP workflow site that is passed to SharePoint Server is not a valid SAP workflow rootsite.
Resolution
Activate the Duet Enterprise workflow feature
1.Verify that you have the following administrative credentials:
You must be a member of the site collection administrators group on the site collection that you are configuring.
2.On the top level of the site collection, on the Site Actions menu, click Site Settings.
3.On the Site Settings page, in the Site Collection Administration section, click Site collection features.
4.On the Features page, click Activate next to the Duet Enterprise Workflow feature. The Status column displays “Active” to indicate that the feature is now active. | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.CannotFindTaskWeb | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Root site URI for SAP workflow task is not valid | Summary
When an SAP workflow is created or updated, the URL of the SAP workflow feature root site is passed to the API to identify the SAP workflow. The root site that is passed to the API must be a root site for the workflow site that is configured as a SAP workflow task type.
Symptoms
The following symptoms might appear:
On the workflow site, new tasks cannot be created for an SAP workflow application and existing tasks cannot be approved.
This event appears in the event log:
Event ID: 3019 Description: The root site URL is not valid.
Cause
The Duet Enterprise workflow feature is not activated on the SAP workflow site that is passed to SharePoint Server.
Resolution
Activate the Duet Enterprise workflow feature
1.Verify that you have the following administrative credentials:
You must be a member of the site collection administrators group on the site collection that you are configuring.
2.On the top level of the site collection, on the Site Actions menu, click Site Settings.
3.On the Site Settings page, in the Site Collection Administration section, click Site collection features.
4.On the Features page, click Activate next to the Duet Enterprise Workflow feature.
The Status column displays “Active” to indicate that the feature is now active. | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.InvalidRootSite | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: SAP workflow feature not activated | Summary
The site template that is used to create a Duet Enterprise Workflow site must be a workflow site that is registered as an SAP workflow. This error occurs when a user tries to create a Duet Enterprise Workflow site and selects a site template that is not a valid workflow site for an SAP Workflow. This error also occurs in a custom workflow application when the URL of the SAP workflow that is passed to the API is not a valid SAP workflow site.
Symptoms
The following symptoms might appear:
On the Duet Enterprise Workflow Site page, a new Duet Enterprise Workflow site cannot be created.
This event appears in the event log:
Event ID: 3020 Description: The site at URL: '<URL>' is not a valid task workspace.
Cause
The site template that is used to create a Duet Enterprise Workflow site is not a valid Workflow site for an SAP Workflow.
Resolution
Use the SAP Workflow Site templateWhen the user creates a workflow site, on the Duet Enterprise Workflow Site page, select a site template that is registered as an SAP workflow.
Modify the custom workflow applicationUse Microsoft SharePoint Designer 2010 to modify the custom workflow application to reference only workflow sites that are registered as an SAP workflow site. | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.InvalidTaskWeb | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
| Workflow: Business Data Connectivity Service - LobSystem in BDC model not found | Summary
The Duet Enterprise SharePoint Add-on and Duet Enterprise SAP Add-ons utilize the Microsoft Business Connectivity Services to enable communication between SharePoint Server 2010 and the SAP environment. The BDC model that is associated with the SAP workflow contains metadata that the SAP workflow requires to connect to SharePoint solutions. The LobSystem object is the top-level container in the BDC model for metadata that describes the SAP system. In XML terms, the LobSystem is the root node that contains all other metadata objects in an application definition. The metadata for the LobSystem that is specified in the BDC model was not found.
Symptoms
This event appears in the event log:
Event ID: 3023 Description: The LOB system could not be found. Please check the Business Data Connectivity Service configuration on the SharePoint server to validate.
Cause
The metadata for the LobSystem object that is specified in the BDC model was not found.
Resolution
Import BDC models
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/?LinkId=205308). For more information about how to import a BDC model, see Manage BDC models (SharePoint Server 2010) (http://go.microsoft.com/fwlink/?LinkId=203862). For information about how to use Windows PowerShell to import a BDC model, see Import-SPBusinessDataCatalogModel (http://go.microsoft.com/fwlink/?LinkID=203587).
Create a new external content type for custom workflow applications
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/?LinkId=203862). | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor.LobsystemNotFound | Microsoft.SharePoint.DuetE.ServerSeed | Microsoft.SharePoint.DuetE.Workflow.WorkflowServerMonitor | ConfigurationHealth | True | | | 0 | False | | | False | Microsoft.Windows.SingleEventLogTimer2StateMonitorType | True | Public | |
Home