Sp-dev-docs: After change regional settings, pages with SPFx webparts gives unexpected error has occurred.

[VesaJuvonen]

_From @geogikk92 on November 17, 2017 7:29_

• [ ] Question
• [x] Bug
• [ ] Enhancement

After change regional settings in SharePoint 2016 On-Premise server to Bulgarian, Macedonian оr other Locale

I have following error:

Error from log file is:

Message : System.FormatException: String was not recognized as a valid DateTime. at
System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCachedThirdPartyComponentProvider.GetUpdateTimeFromAppCatalog(SPWebweb) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCachedThirdPartyComponentProvider.GetDistributedUpdateTime(Guid tenantId, SPWeb web) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCachedThirdPartyComponentProvider.EnsureCacheIsValid(SPWeb web, Guid tenantId) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCachedThirdPartyComponentProvider.GetNotFoundComponents(SPClientSideComponentQueryResultCollection requests, SPWeb web) at Microsoft.SharePoint.ClientSideCom...

Thanks for your contribution! Sharing is caring.

_Copied from original issue: SharePoint/sp-dev-fx-webparts#367_

[VesaJuvonen]

_From @waldekmastykarz on November 20, 2017 11:33_

Did you customize the list's Add form and put a SharePoint Framework client-side web part on it?

[VesaJuvonen]

_From @geogikk92 on November 20, 2017 11:47_

Yes! I replace my default add listItem form with customized SharePoint Framework client-side web part.

My WebPart working with Locale(English(USA)), but others locale(Bulgarian, Macedonia and other) doesnt working, give above error in stacktrace.

[VesaJuvonen]

_From @waldekmastykarz on November 20, 2017 11:57_

@VesaJuvonen do you have more information about if SPFx web parts are not meant to be used on list form pages and the behavior is by design or if this is a potential bug in SPFx that needs further investigation?

[VesaJuvonen]

_From @geogikk92 on November 20, 2017 12:5_

I have SPFx web parts In site classic pages and error is the same.

[VesaJuvonen]

_From @waldekmastykarz on November 20, 2017 12:9_

Which version of the SharePoint Framework Yeoman generator did you use to scaffold the project?

[VesaJuvonen]

_From @geogikk92 on November 20, 2017 12:15_

The version of the SharePoint Framework Yeoman is:

.yo.rc.json file contains:

{
"@microsoft/generator-sharepoint": {
"version": "1.3.4",
"libraryName": "lirex-holidays",
"libraryId": "c715415a-9890-4a12-b72b-0dc8244f1bb3",
"environment": "onprem"
}
}

[VesaJuvonen]

_From @darekjpro on November 23, 2017 11:32_

Having the same issue.
Using the latest version of Yeoman (1.3.4). Solution targeted for SharePoint 2016 onwards.
SPFx web part added to classic web part page working fine with English-US regional settings. Changing site regional settings to English-UK causes the same error in ULS (_String was not recognized as a valid DateTime._)
Thanks.

[geogikk92]

Did you find anything on my question? This is a blocker for my project. Thank you! :)

[VesaJuvonen]

This was an issue on the server side which has been now fixed. Since this is, however, on-premises fix, it will be rolled out as part of the on-premises CUs. In this case, it will be most likely either in January CU or in Feb CU.

[geogikk92]

Today, after upload my solution in app catalog an same issue comes again.

Error from stack trace:

Category : General
Level : High
EventID : bihod
Message : GetComponentManifests Failure: System.FormatException: String was not recognized as a valid DateTime. at System.DateTimeParse.Parse(String s, DateTimeFormatInfo dtfi, DateTimeStyles styles) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCachedThirdPartyComponentProvider.GetUpdateTimeFromAppCatalog(SPWeb web) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCachedThirdPartyComponentProvider.GetDistri
butedUpdateTime(Guid tenantId, SPWeb web) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCached ThirdPartyComponentProvider.EnsureCacheIsValid(SPWeb web, Guid tenantId) at Microsoft.SharePoint.ClientSideComponent.SPClientSideCachedThirdPartyComponentProvider.GetNotFoundComponents(SPClientSideComponentQueryR
esultCollection requests, SPWeb web) at Mi...

[VesaJuvonen]

Hi @geogikk92, like mentioned in the last comment, this is a fix which will be part of the upcoming Cumulative Path for on-premises. To be able to get it fixed, there has to be a server-side fix to your on-premises environment. This means that the issue will be resolved after the patch (January CU or February CU) is available and installed in your environment.

[LucasOvejero]

Hi @VesaJuvonen, some notice from this fix-update?

[christopher-walker]

Just been looking for the status on this also:
https://support.microsoft.com/en-us/help/4011642/descriptionofthesecurityupdateforsharepointenterpriseserver2016january
Looks like it was fixed in the January 2018 CU:

The SharePoint Framework (SPFx) page crashes when the site’s regional setting is changed.

[andrewconnell]

Closing as fixed...

[msft-github-bot]

Issues that have been closed & had no follow-up activity for at least 7 days are automatically locked. Please refer to our wiki for more details, including how to remediate this action if you feel this was done prematurely or in error: Issue List: Our approach to locked issues