Base solution for your next web application
Open Closed

Localization has stopped to work and started again by itself #9602


User avatar
0
Leonardo.Willrich created

Hi.

I am using ASP.NET CORE MVC & jQuery .NET Core 3.1 v9.0.1 and I got an issue with Localization.

I have the application hosted on AWS running under IIS version 8.5. This morning, for a while, all menus and labels were in brackets instead of showing the written name as per in the Localization file.

In the log I could only see that the localization was not found, for example:

WARN 2020-09-07 20:57:00,122 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'Materials' in localization source 'iAPIS'! WARN 2020-09-07 20:57:00,127 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'VisitObservationQuestionTemplates' in localization source 'iAPIS'! WARN 2020-09-07 20:57:00,132 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'TaskGroups' in localization source 'iAPIS'! WARN 2020-09-07 20:57:00,137 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'TaskTypes' in localization source 'iAPIS'! WARN 2020-09-07 20:57:00,142 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'VisitTemplates' in localization source 'iAPIS'! WARN 2020-09-07 20:57:00,147 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'VisitStatus' in localization source 'iAPIS'! WARN 2020-09-07 20:57:00,156 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'WorkerCrews' in localization source 'iAPIS'! WARN 2020-09-07 20:57:00,161 [52 ] naries.DictionaryBasedLocalizationSource - Can not find 'WorkerVehicles' in localization source 'iAPIS'!

It has affected all users and tenants.

And then, after 10 minutes, doing absolutely nothing, it has restored by itself.

Any idea about what happened?


3 Answer(s)
  • User Avatar
    0
    zony created
    Support Team

    Hi Leonardo.Willrich, Has this problem occurred before?

  • User Avatar
    0
    Leonardo.Willrich created

    Hi zony,

    We have migrated this version and hosted it for tests around one week ago. That was the first time on this environment that it happened.

    Have you seen it before or are there other topics related to this issue?

  • User Avatar
    0
    ismcagdas created
    Support Team

    Hi,

    This might happen when the localization XML file can not be accessed on the server. This might be a temporary issue.