web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Service | Customer Service, Contact Center, Fie...
Suggested Answer

SLA Set as Default error Exception occured in SLAInstance management custom action : system.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]

(0) ShareShare
ReportReport
Posted on by 5

Exception occured in SLAInstance management custom action : System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Invalid time zone code, expected 1 result, got 0 (Fault Detail is equal to Exception details: ErrorCode: 0x80040203 Message: Invalid time zone code, expected 1 result, got 0 TimeStamp: 2021-03-28T12:26:36.1229746Z -- Exception details: ErrorCode: 0x80040203 Message: Invalid time zone code, expected 1 result, got 0 TimeStamp: 2021-03-28T12:26:36.1229746Z -- ).

Exception Message: Exception occured in SLAInstance management custom action : System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Invalid time zone code, expected 1 result, got 0 (Fault Detail is equal to Exception details: ErrorCode: 0x80040203
Message: Invalid time zone code, expected 1 result, got 0
TimeStamp: 2021-03-28T12:30:47.5587200Z
--
Exception details:
ErrorCode: 0x80040203
Message: Invalid time zone code, expected 1 result, got 0
TimeStamp: 2021-03-28T12:30:47.5587200Z
--
).

ErrorCode: -2147220891
HexErrorCode: 0x80040265

ErrorDetails:
OperationStatus: 0
SubErrorCode: -2146233088

TraceText:
[Microsoft.Dynamics.Service.Plugins: Microsoft.Dynamics.Service.Plugins.PostOperationIncidentUpdateEntitlement]
[a468c44e-c204-e711-80ca-02155dc812c3: Post-operation update entitlement for incident]
Entered Microsoft.Dynamics.Service.Plugins.PreOperationIncidentUpdate.Execute(), Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247
Exiting Microsoft.Dynamics.Service.Plugins.PreOperationIncidentUpdate.Execute(), Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247
Entered Microsoft.Dynamics.Service.Plugins.PreOperationIncidentUpdateEntitlement.Execute(), Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247
Exiting Microsoft.Dynamics.Service.Plugins.PreOperationIncidentUpdateEntitlement.Execute(), Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247
Entered Microsoft.Dynamics.Service.Plugins.PostOperationIncidentUpdateEntitlement.Execute(), Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247
FlowBasedSLA: SLAPluginHelper - This is new sla and slainvokedid is also new sla, calling custom action. with slaid : 2b588b21-678f-eb11-b1ac-000d3a47bbd6 and slainvokedid : 00000000-0000-0000-0000-000000000000, Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247
Exception: System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Exception occured in SLAInstance management custom action : System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Invalid time zone code, expected 1 result, got 0 (Fault Detail is equal to Exception details:
ErrorCode: 0x80040203
Message: Invalid time zone code, expected 1 result, got 0
TimeStamp: 2021-03-28T12:30:47.5587200Z
--
Exception details:
ErrorCode: 0x80040203
Message: Invalid time zone code, expected 1 result, got 0
TimeStamp: 2021-03-28T12:30:47.5587200Z
--
). (Fault Detail is equal to Exception details:
ErrorCode: 0x80040265
Message: Exception occured in SLAInstance management custom action : System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Invalid time zone code, expected 1 result, got 0 (Fault Detail is equal to Exception details:
ErrorCode: 0x80040203
Message: Invalid time zone code, expected 1 result, got 0
TimeStamp: 2021-03-28T12:30:47.5587200Z
--
Exception details:
ErrorCode: 0x80040203
Message: Invalid time zone code, expected 1 result, got 0
TimeStamp: 2021-03-28T12:30:47.5587200Z
--
).
TimeStamp: 2021-03-28T12:30:47.5743595Z
--
Exception details:
ErrorCode: 0x80040265
Message: Exception occured in SLAInstance management custom action : System.ServiceModel.FaultException`1[Microsoft.Xrm.Sdk.OrganizationServiceFault]: Invalid time zone code, expected 1 result, got 0 (Fault Detail is equal to Exception details:
ErrorCode: 0x80040203
Message: Invalid time zone code, expected 1 result, got 0
TimeStamp: 2021-03-28T12:30:47.55...)., Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247
Exiting Microsoft.Dynamics.Service.Plugins.PostOperationIncidentUpdateEntitlement.Execute(), Correlation Id: d9bb07e1-7be5-40c1-9594-c8a0ca098281, Initiating User: 518df70a-2466-eb11-b0b0-000d3aa8e247

PII Removed. Length: 7148

I have the same question (0)
  • Community Member Profile Picture
    on at

    Hi Ana,

    Did this error come out of nowhere? Have you done any customization?

    Maybe you could try restarting it or changing your browser or using privacy mode to test again.

    Regards,

    Leah Ju

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

  • Ana Soares Profile Picture
    5 on at

    Thank you everyone the problem is already solved,

  • Community Member Profile Picture
    on at

    Hi Ana,

    Glad your problem was solved, and can you share the solution if possible.

    Regards,

    Leah Ju

  • Suggested answer
    Man G Profile Picture
    5 on at

    Hi Ana, please share the solution

    Update: I managed to find the culprit in my case: it had to do with the settings of the SLA Items in the SLA - in the 'General' section for 'Business Hours' I had mistakenly selected the Holiday Schedule instead of the Customer Service Schedule I had created previously. This led to the above error and the flows not being able to trigger. 

  • Community Member Profile Picture
    on at

    Hi Man,

    Thank you for sharing!

    Regards,

    Leah

  • Suggested answer
    Axel Girgensohn Profile Picture
    5 on at

    Hi

    I came across your comment. I had the same error that came up when assigning the case. In my case it was the connection in the dataverse steps of the SLA actions. Changing to the system user (a custom user that is set up for all flows in general in that environment) all worked.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > Service | Customer Service, Contact Center, Field Service, Guides

#1
Tom_Gioielli Profile Picture

Tom_Gioielli 73 Super User 2025 Season 2

#2
Daniyal Khaleel Profile Picture

Daniyal Khaleel 42 Most Valuable Professional

#3
Scott Jackson UK Profile Picture

Scott Jackson UK 22

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans