Workflow throwing unexpected error after importing into CRM 2016

(0) Share

Report

Posted on by Community Member

We have a workflow which creates ID's for our reports. This works in our development environment but we moved it into out acceptance environment and now get an error.

Please see below for the error message.

Plugin Trace:

[OccurenceReportIDSequencer: OccurrenceReportIDSequencer.IDSequencer]
[Occurrence Report: ID Sequencer]

Error Message:

Unhandled Exception: Microsoft.Crm.CrmException: Unexpected exception from plug-in (Execute): OccurrenceReportIDSequencer.IDSequencer: System.Exception: Failed to update all new Occurrence Reports.
at Microsoft.Crm.Sandbox.SandboxCodeUnit.Execute(IExecutionContext context)
at Microsoft.Crm.Workflow.Services.ProxyCustomActivity.Execute(CodeActivityContext executionContext)

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Sort by

JFulfordMS 193 on at

Like (0)

Report
Copy link

Link copied!

We would need to see the code in order to assist. Also, have you tried using System Customization Comparer and/or Delta Plugins (XrmToolBox plugins) to see if there are schema differences between environments?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

Hi,

Thanks for the timely response. Please see below for the two workflows code.

I will give thoughts tools a try and get back to you. In the mean while any other suggestions?

Thanks in Advance!

Occurrence Report: Update Occurrence Report #

• Check workflow

OccurenceReportWorkFlowCheck (1.0.0.0);OccurrenceReportWorkFlowCheck.WorkflowCheck

Step: if Check Workflow;WorkflowStatus equals [o], then:

Start child workflow Occurrence Report ID Sequencer

Occurrence report: ID Sequencer

Timeout until 15 minutes then

No steps have been added

Timeout until 15 minutes then

No steps have been added

Timeout until 15 minutes then

No steps have been added

Timeout until 15 minutes then

• Start child workflow: Occurrence Report: ID Sequencer

• Stop workflow with status of: Succeeded

Was this reply helpful? Yes No
Suggested answer

Charles Abi Khirs 3,569 on at

Like (0)

Report
Copy link

Link copied!

Hello,

You might missed something during the deployment that is required by your workflow to be able to generate the Sequence Number of your reports.

Make sure that you deploy all the components on your acceptance environment. In addition, if you are using a configuration entity, make sure you import its data to the acceptance environment as well.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

I didn't deploy to the acceptance environment. Is there any way I can check if the workflow is missing any required components?

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report
Copy link

Link copied!

I compared our acceptance environment to our development environment. The only differences were attributes. I unistalled and reinstalled the workflow plugins and the processes from our development environment. However the problem persists. Am unhandled exception from the plugin. On top of this using the Plugin Registration tool I am unable to debug the workflow plugin. Any ideas? Thanks in advance!

Was this reply helpful? Yes No