AnsweredAssumed Answered

What does Workflow type 'Reusable' is not recognized in this environment mean?

Question asked by jennifer1973 on Mar 18, 2015

We received an error "Workflow type 'Reusable' is not recognized in this environment." and can't figure out what caused it.

 

Additional information:

 

We have created a reusable workflow and connected it to a sharepoint list. It runs after creation or modification of a listitem.

This morning an error occured. An e-mail was send containing the message "Click HERE to view the workflow status". Following the link results in this message:

Error

Cannot find history for workflow with
instanceId 5692e165-4f8a-4390-a99d-09896cad13d7. It may have been removed from
the database.

Troubleshoot
issues with Microsoft SharePoint Foundation.

Correlation ID:
ff5d52b2-9797-43af-99ca-a27391a77611

Date and Time: 3/18/2015 9:41:34
AM

 

Clicking on the status of the workflow in the list item shows this:

The following events have occurred in this workflow. 

Date Occurred   Event Type   Presence enabled for this columnUser ID   Description   Outcome  

3/18/2015 7:42 AM Comment  Failed to start workflow. Workflow type 'Reusable' is not recognized in this environment.

Parameter name: type Error

3/18/2015 7:42 AM Error No presence informationSystem Account An error has occurred in Afhandeling Evaluation.

 

The log shows this:

SqlError: 'Transaction (Process ID 161) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.'    Source: '.Net SqlClient Data Provider' Number: 1205 State: 51 Class: 13 Procedure: 'proc_RevertInProgressWorkItems' LineNumber: 38 Server: 'SQL-APPL1\SP' d415696e-9c9a-406e-860f-42aaab8c9902

03-18-2015 07:42:33.81 w3wp.exe (0x1FB0) 0x1534 SharePoint Foundation Database 5586 Critical Unknown SQL Exception 1205 occurred. Additional error information from SQL Server is included below.  Transaction (Process ID 161) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. d415696e-9c9a-406e-860f-42aaab8c9902

I don't quite understand how the transaction could be deadlocked on lock resources with another process. The concerning listitem was only created and not updated afterwards, so the workflow on the listitem was started once.

Please find attached the logfile

Attachments

Outcomes