unexpected error create a case

(0) Share

Report

Posted on by PersianBoy

hi when i want to create or edit a case this error happen

the error code is <ErrorCode>-2147220891</ErrorCode>

can you help me to fix it

error when create a case

All responses (7)

Answers (1)

Sort by

cloflyMao 25,210 on at

Like (1)

Report
Copy link

Link copied!

Hi Partner,

Please disable possible plugins or workflows on case entity,

it seems that some data on fields didn't meet requirement(missing or not valid) in related plugins or workflows.

Also, make sure you current user had all necessary privileges.

You could Download Log File or Show technical details for more details about your error, then share it if possible.

Regards,

Clofly
PersianBoy 20 on at

Like (0)

Report
Copy link

Link copied!

ty for your answer

Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=8.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: Operation is not valid due to the current state of the object.Detail:

<OrganizationServiceFault xmlns:i="www.w3.org/.../XMLSchema-instance" xmlns="schemas.microsoft.com/.../Contracts">

<ActivityId>97940a65-c2d1-4850-9cfb-decdd5b18a6f</ActivityId>

<ErrorCode>-2147220891</ErrorCode>

<ErrorDetails xmlns:d2p1="schemas.datacontract.org/.../System.Collections.Generic">

<KeyValuePairOfstringanyType>

<d2p1:key>OperationStatus</d2p1:key>

<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">0</d2p1:value>

</KeyValuePairOfstringanyType>

<KeyValuePairOfstringanyType>

<d2p1:key>SubErrorCode</d2p1:key>

<d2p1:value xmlns:d4p1="www.w3.org/.../XMLSchema" i:type="d4p1:string">-2146233088</d2p1:value>

</KeyValuePairOfstringanyType>

</ErrorDetails>

<Message>Operation is not valid due to the current state of the object.</Message>

<Timestamp>2019-12-31T06:33:05.8299282Z</Timestamp>

<ExceptionSource i:nil="true" />

<InnerFault i:nil="true" />

<OriginalException i:nil="true" />

<TraceText>

[Microsoft.Crm.Service.ObjectModel: Microsoft.Crm.Service.ObjectModel.CasePostCreatePlugin]

[ffde44b1-a685-4948-85b8-e4091bc2a98b: CasePostCreatePlugin]

[Microsoft.Crm.ObjectModel: Microsoft.Crm.Extensibility.InternalOperationPlugin]

[46f6cf4c-14ae-4f1e-98a1-eae99a37e95c: ExecuteWorkflowWithInputArguments]

Starting sync workflow 'SLA MobinTech', Id: eea2467d-bdcb-e911-80f2-005056bd1d96

Sync workflow 'SLA MobinTech' terminated with error 'Operation is not valid due to the current state of the object.'

</TraceText>

</OrganizationServiceFault>
Verified answer

ba365guy 2,950 on at

Like (0)

Report
Copy link

Link copied!

Based on the error log, the workflow "SLA MobinTech" is causing the error.

Please deactivate this workflow for a moment and check if you still face the error.

Please check the workflow process sessions to find more details on this error.
cloflyMao 25,210 on at

Like (0)

Report
Copy link

Link copied!

Hi Partner,

1. Please open workflow 'SLA MobinTech' Process Sessions to check detail about failed reason.

2. Disable the workflow to test whether the issue would still appear.

3. Is there any plug-in running when you create or update a case?(or any other workflow that is related to SLA, SLAItem or SLAKPIInstance)

Regards,

Clofly
AJ-22040756-0 Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Hi Partner

Based on the Traces shared, this seems to be an issue with the workflow "SLA MobinTech",

1. Please check the Workflow process session for this workflow referencing the article https://docs.microsoft.com/en-us/dynamics365/customerengagement/on-premises/customize/monitor-manage-processes

2. Try disabling the Workflow and check if you are able to create or edit a case

Hope this helps.

Best regards,

Akash

Please mark as verified if the answer is helpful. Welcome to join hot discussions in Dynamics 365 Forums.
Suggested answer

RajuB Microsoft Employee on at

Like (0)

Report
Copy link

Link copied!

Based on the given above recommendations you can try those options by disabling the WF related to SLA and reproduce the issue. if its working as expected after the pointed WF disabled then issue get isolated and you can validate the problematic WF to check what is causing the issue.

you can open a case with Microsoft support channel if still need any assistance.

Happy New year!
Suggested answer

ashish12 3,079 on at

Like (1)

Report
Copy link

Link copied!

Hi,

I am not sure whether your issue is resolved or not.

If not, as everyone mentioned. Watch your real-time, background workflows and actions. Try after disabling custom wf created for case.

You can check how many WFs are running on case creation or update go to Settings > System Jobs.

Thanks