Quantcast
Channel: Microsoft Dynamics 365 Community
Viewing all articles
Browse latest Browse all 64797

Australian Data Centre Bug Workaround – “Invalid Argument” in Workflow/Business Process Flow Editor

$
0
0

Recently it’s been reported by my colleague and a fellow Australian CRM MVP, Guy Riddle, that there is a bug on Australian CRM Online on Workflow/Business Process Flow editor that showing “Invalid Argument” error screen:

AustralianBPFWFError

And on the Workflow editor it will produce an error log similar to:


Unhandled Exception: System.ServiceModel.FaultException`1[[Microsoft.Xrm.Sdk.OrganizationServiceFault, Microsoft.Xrm.Sdk, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]]: A validation error occurred. The languageCode = 3081 not a provisioned or enabled LCID.Detail:

<OrganizationServiceFault xmlns:i="<a href="http://www.w3.org/2001/XMLSchema-instance" target="_blank">http://www.w3.org/2001/XMLSchema-instance</a>" xmlns="<a href="http://schemas.microsoft.com/xrm/2011/Contracts" target="_blank">http://schemas.microsoft.com/xrm/2011/Contracts</a>">

  <ErrorCode>-2147220989</ErrorCode>

  <ErrorDetails xmlns:d2p1="<a href="http://schemas.datacontract.org/2004/07/System.Collections.Generic" target="_blank">http://schemas.datacontract.org/2004/07/System.Collections.Generic</a>" />

  <Message>A validation error occurred. The languageCode = 3081 not a provisioned or enabled LCID.</Message>

  <Timestamp>2015-05-21T23:35:31.0011596Z</Timestamp>

  <InnerFault>

    <ErrorCode>-2147220970</ErrorCode>

    <ErrorDetails xmlns:d3p1="<a href="http://schemas.datacontract.org/2004/07/System.Collections.Generic" target="_blank">http://schemas.datacontract.org/2004/07/System.Collections.Generic</a>" />

    <Message>System.ArgumentException: A validation error occurred. The languageCode = 3081 not a provisioned or enabled LCID.</Message>

    <Timestamp>2015-05-21T23:35:31.0011596Z</Timestamp>

    <InnerFault i:nil="true" />

    <TraceText i:nil="true" />

  </InnerFault>

  <TraceText i:nil="true" /></OrganizationServiceFault>

One of the workaround that my colleague found is to set the format to English (US). To change this, navigate to Options> Formats> Change “Current Format” to English (United States)

Options

US_Format

Now you should be able to work on Workflow/Business Process Flow editor again.

HTH!


Viewing all articles
Browse latest Browse all 64797

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>