TimeZoneNotFoundException: The time zone ID 'America/Chicago' was not found on the local computer.

[nssidhu]

I am using .NET RC1 Blazor WebAssembly Hosted App.
In my published app to Azure AppService(windows) which is deployed as self-contained i am running into timezone error.
The app works fine when running on my local dev box

In my Server Controller, i am trying to find the Timezone of business location as shown below.

var timezoneLocation = TimeZoneInfo.FindSystemTimeZoneById(LocalTimeAtOrgLocation);

but i get the following error.

Error Occured in  OrganizationController.GetActiveTokenAtOrgLocationTerminal System.TimeZoneNotFoundException: The time zone ID 'America/Chicago' was not found on the local computer.
   at System.TimeZoneInfo.FindSystemTimeZoneById(String id)
   at XXXXXV6New.Server.Controllers.OrganizationController.GetActiveTokenAtOrgLocationTerminal(Nullable`1 OrgLocationTerminalID) in C:\Users\admin\source\repos\XXXXXXXV6New\Server\Controllers\OrganizationController.cs:line 2995

[pranavkm]

Is this error being thrown by .NET Core or WebAssembly?

[dotnet-issue-labeler]

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

[nssidhu]

This happens on the server(in the controller).Nothing to do with wash, other that it a Blazor wasm hosted project. Sent from Yahoo Mail for iPhone On Friday, October 8, 2021, 8:14 AM, Pranav K ***@***.***> wrote: Is this error being thrown by .NET Core or WebAssembly? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[nssidhu]

Here is the GitHub repo
https://github.com/nssidhu/BlazorAppTimezone

[danmoseley]

@nssidhu is that a private repo? the link gives 404.

I think all we need is the snippet of code, the value you're passing to the API, and any details of your configuration (sounds like .NET 6.0 RC1 on Windows?)

[nssidhu]

It is very simple to reproduce, Just create a Blazor wasm hosted sample app.
Add two lines.

Can't be any simpler than this.
The error only occurs on the published version(Publish it on Azure WebApp)

[HttpGet]
       public IEnumerable<WeatherForecast> Get()
       {
           var timezoneLocation = TimeZoneInfo.FindSystemTimeZoneById("America/Chicago");

           var timeAtLcoation = TimeZoneInfo.ConvertTimeFromUtc(DateTime.UtcNow, timezoneLocation);

           return Enumerable.Range(1, 5).Select(index => new WeatherForecast
           {
               Date = DateTime.Now.AddDays(index),
               TemperatureC = Random.Shared.Next(-20, 55),
               Summary = Summaries[Random.Shared.Next(Summaries.Length)]
           })
           .ToArray();
       }

[nssidhu]

I have changed the visibility to public

[nssidhu]

@nssidhu is that a private repo? the link gives 404.

I think all we need is the snippet of code, the value you're passing to the API, and any details of your configuration (sounds like .NET 6.0 RC1 on Windows?)

Yes it is using .NET 6 RC1.

C:\Users\admin>dotnet --info
.NET SDK (reflecting any global.json):
Version: 6.0.100-rc.1.21463.6
Commit: e627d556a1

Runtime Environment:
OS Name: Windows
OS Version: 10.0.19042
OS Platform: Windows
RID: win10-x64
Base Path: C:\Program Files\dotnet\sdk\6.0.100-rc.1.21463.6\

Host (useful for support):
Version: 6.0.0-rc.1.21451.13
Commit: d7619cd

.NET SDKs installed:
5.0.400 [C:\Program Files\dotnet\sdk]
6.0.100-rc.1.21463.6 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 6.0.0-rc.1.21452.15 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.0-rc.1.21451.13 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 5.0.9 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.0-rc.1.21451.3 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I am using .NET RC1 Blazor WebAssembly Hosted App.
In my published app to Azure AppService(windows) which is deployed as self-contained i am running into timezone error.
The app works fine when running on my local dev box

In my Server Controller, i am trying to find the Timezone of business location as shown below.

var timezoneLocation = TimeZoneInfo.FindSystemTimeZoneById(LocalTimeAtOrgLocation);

but i get the following error.

Error Occured in  OrganizationController.GetActiveTokenAtOrgLocationTerminal System.TimeZoneNotFoundException: The time zone ID 'America/Chicago' was not found on the local computer.
   at System.TimeZoneInfo.FindSystemTimeZoneById(String id)
   at XXXXXV6New.Server.Controllers.OrganizationController.GetActiveTokenAtOrgLocationTerminal(Nullable`1 OrgLocationTerminalID) in C:\Users\admin\source\repos\XXXXXXXV6New\Server\Controllers\OrganizationController.cs:line 2995

Author:	nssidhu
Assignees:	-
Labels:	arch-wasm, area-System.Globalization, untriaged
Milestone:	-

[danmoseley]

Ah - I missed that it was Blazor. @lewing I know we do special time zone things on Blazor..?

[nssidhu]

Again, I am talking about Blazor server side error and not client(wasm), I just happen to use Blazor wasm hosted project.
Re-iterating because it is very easy to get confused, The error happens in the hosted server project and not the client(wasm).
Also i made the repo public so it should be accessible.

[svick]

According to this SO question, Azure AppService uses the NLS globalization mode. That would explain this issue since support for IANA time zone IDs does not work in the NLS mode:

runtime/src/libraries/System.Private.CoreLib/src/System/TimeZoneInfo.FullGlobalizationData.cs

Lines 10 to 16 in 3de6207

	private static unsafe bool TryConvertIanaIdToWindowsId(string ianaId, bool allocate, out string? windowsId)
	{
	if (GlobalizationMode.Invariant || GlobalizationMode.UseNls || ianaId is null)
	{
	windowsId = null;
	return false;
	}

An answer to that question suggest using app local ICU to disable the NLS mode.

[danmoseley]

@tarekgh I wonder whether we should suggest to AppService that they move to ICU default, at least perhaps for 6.0+.

[danmoseley]

great find @svick BTW thank you.

[ghost]

Tagging subscribers to this area: @dotnet/area-system-runtime
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I am using .NET RC1 Blazor WebAssembly Hosted App.
In my published app to Azure AppService(windows) which is deployed as self-contained i am running into timezone error.
The app works fine when running on my local dev box

In my Server Controller, i am trying to find the Timezone of business location as shown below.

var timezoneLocation = TimeZoneInfo.FindSystemTimeZoneById(LocalTimeAtOrgLocation);

but i get the following error.

Error Occured in  OrganizationController.GetActiveTokenAtOrgLocationTerminal System.TimeZoneNotFoundException: The time zone ID 'America/Chicago' was not found on the local computer.
   at System.TimeZoneInfo.FindSystemTimeZoneById(String id)
   at XXXXXV6New.Server.Controllers.OrganizationController.GetActiveTokenAtOrgLocationTerminal(Nullable`1 OrgLocationTerminalID) in C:\Users\admin\source\repos\XXXXXXXV6New\Server\Controllers\OrganizationController.cs:line 2995

Author:	nssidhu
Assignees:	-
Labels:	arch-wasm, area-System.Runtime
Milestone:	-

[tarekgh]

I am not clear here what OS used to run the WASM server? Does WASM server is running with Azure AppService? Answers may help here.

Some Windows Servers OS's doesn't have ICU versions (or has old ICU versions which .NET doesn't support). If running on such environment, the workaround is to use ICU app-local feature. Add something like the following to the csproj:

  <ItemGroup>
        <RuntimeHostConfigurationOption Include="System.Globalization.AppLocalIcu" Value="68.2.0.6" />
        <PackageReference Include="Microsoft.ICU.ICU4C.Runtime" Version="68.2.0.6" />
  </ItemGroup>

If the users have no control and Azure AppService is controlling using NLS or ICU, then the solution must come from Azure AppService to allow using ICU. @lewing may know better how the WASM server run using Azure AppService. We'll need to understand too why Azure AppServer decided to force NLS mode too. @danmoseley can you connect us with somebody from Azure side?

[nssidhu]

The error is occurring in is .NET 6 server side. It has nothing to do with wasm.
I am deploying the App into Azure App Service(windows) as self contained.
FYI: The error does not occur in development on my local pc, occurs only on the published version.

I tried those settings in the separate isolated repo and it seems to work.
but the same setting in my existing project, tend to get time correct but loose the time zone info.

I am now trying to snap shot debug azure deployed app to see what is happening on the server side, will update

Found out that TimeZoneInfo.ConvertTimeFromUtc returns datetime without timezone info, its Quite weird since we are working with timezone it should return DateTimeoffset instead of DateTime.

I am not sure why that works correctly on my local pc.

[tarekgh]

FYI: The error does not occur in development on my local pc, occurs only on the published version.

Are you running the published version on the same machine you are developing on? This was my question about what OS the server code is running on.

I tried those settings in the separate isolated repo and it seems to work.
but the same setting in my existing project, tend to get time correct but loose the time zone info.

Were you running exact same type of project in the isolated repo? and you were running it on the exact same environment?

I am now trying to snap shot debug azure deployed app to see what is happening on the server side, will update

Thanks, that will help. Please ensure getting the OS version running the server.

Found out that TimeZoneInfo.ConvertTimeFromUtc returns datetime without timezone info, its Quite weird since we are working with timezone it should return DateTimeoffset instead of DateTime.

TimeZoneInfo.ConvertTimeFromUtc takes the time zone object which the time to. So, you already have all information you need there. Also, you can just use the following API if you need to get DateTimeOffset.

public static DateTimeOffset ConvertTime (DateTimeOffset dateTimeOffset, TimeZoneInfo destinationTimeZone);

I am not sure why that works correctly on my local pc.

It is possible the server is running on OS doesn't support ICU which cause the .NET to fallback to NLS.

[nssidhu]

I am finding that I cannot use snapshot debugger on Azure App service with visual Studio 2022, it only supports 2017 & 2019.
will try some different method to capture runtime values.

Details about OS and dotnet version are mentioned up in the chain.

Will post more details once i have them.

[nssidhu]

Some more findings

Here is the code which is running into problem when deployed on to Azure App Service(Windows) as self contained.

 var LocalTimeAtOrgLocation = orgLocationTerminal?.OrgLocationID_FKNavigation.TimeZone_Blazor;
  telemetryClient.TrackException(new Exception("TimeZone : " + LocalTimeAtOrgLocation));  
      This is the Output// 	TimeZone : America/Chicago
  TimeZoneInfo timezoneID = TimeZoneInfo.FindSystemTimeZoneById(LocalTimeAtOrgLocation); 


  telemetryClient.TrackException(new Exception("TimeZone ID : " + timezoneID.Id));   
      This is the Output // TimeZone ID : America/Chicago
  telemetryClient.TrackException(new Exception("TimeZone Display Name  : " + timezoneID.DisplayName));  
      This is output //TimeZone Display Name : (UTC-06:00) Central Time (US & Canada)
 
 telemetryClient.TrackException(new Exception("TimeZone Standard Name  : " + timezoneID.StandardName));  
     This is output//TimeZone Standard Name : Central Standard Time	

  DateTimeOffset timeAtLcoation = TimeZoneInfo.ConvertTimeFromUtc(DateTime.UtcNow, timezoneID);

  telemetryClient.TrackException(new Exception("Time at Location Before Offset : " + timeAtLcoation.ToString("MM/dd/yyyy HH:mm:ss tt zzz")));  
        **_This is output //Time at Location Before Offset : 10/09/2021 20:28:29 PM +00:00
        This is also the issue, it display correct time but no Timezone info (looks like it is GMT)_**

 timeAtLcoation = timeAtLcoation.ToOffset(timezoneID.BaseUtcOffset);
  Attempt to add timezone.
 telemetryClient.TrackException(new Exception("Time at Location after Offset : " + timeAtLcoation.ToString("MM/dd/yyyy HH:mm:ss tt zzz")));  
       It does adds time zone, but it messes up the actual time //Time at Location after Offset : 10/09/2021 14:28:29 PM -06:00

[nssidhu]

works after deploying on the new instance of Azure app service.
Looks like Azure App service should have option to clean install(i.e. delete everything including temp files)

[tarekgh]

@nssidhu thanks for your tries and investigation. Just to know, what extra thing you did to make it work when you have a clean reinstall on Azure app service? did you reference the ICU package in your project?

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

I am using .NET RC1 Blazor WebAssembly Hosted App.
In my published app to Azure AppService(windows) which is deployed as self-contained i am running into timezone error.
The app works fine when running on my local dev box

In my Server Controller, i am trying to find the Timezone of business location as shown below.

var timezoneLocation = TimeZoneInfo.FindSystemTimeZoneById(LocalTimeAtOrgLocation);

but i get the following error.

Error Occured in  OrganizationController.GetActiveTokenAtOrgLocationTerminal System.TimeZoneNotFoundException: The time zone ID 'America/Chicago' was not found on the local computer.
   at System.TimeZoneInfo.FindSystemTimeZoneById(String id)
   at XXXXXV6New.Server.Controllers.OrganizationController.GetActiveTokenAtOrgLocationTerminal(Nullable`1 OrgLocationTerminalID) in C:\Users\admin\source\repos\XXXXXXXV6New\Server\Controllers\OrganizationController.cs:line 2995

Author:	nssidhu
Assignees:	-
Labels:	arch-wasm, area-System.Runtime
Milestone:	7.0.0

[tarekgh]

@lewing could you please have a look? when running WASM server app from VS or when deploying it to local folder, everything works fine as expected. When deploying the app to Azure app service it doesn't work. Looking at the deployment log (from the video) it shows first the app get trimmed then mono-aot-cross.exe and emcc will run which is most likely is what causing the issue here. does mono-aot-cross.exe and emcc can handle ICU native libraries which is part of the app? Is there any option to publish the app as non-aot to Azure app service?

[nssidhu]

@tarekgh I suspect something wrong in the routing framework when deployed on Azure app service. I updated my code to have swagger and i cannot even open swagger on the deployed version.

Somehow i am getting feeling that Blazor wasm is very unstable platform. thing works fine when running locally and behaves totally different when deployed to Azure App Service.

I did open another issue on GitHub for the same source code citing why my API calls are not going through on the deployed vversion.

[tarekgh]

@nssidhu I have pinged @lewing who may help with the WASM apps deployment to Azure service.

[lewing]

This still doesn't look wasm related. @pranavkm any thoughts? or suggestions on who to talk to on the app service side?

[sebastienros]

I am having a similar issue with GitHub actions running my unit tests on Windows.
I am loading a time zone by id using an IANA string. It works locally with .NET 6 on Windows 11, but running the test using "windows-latest" in GitHub action returns this:

  Failed Fluid.Tests.MiscFiltersTests.DateNumberIsParsedInLocalTimeZone [< 1 ms]
  Error Message:
   System.TypeInitializationException : The type initializer for 'Fluid.Tests.MiscFiltersTests' threw an exception.
---- System.TimeZoneNotFoundException : The time zone ID 'America/Los_Angeles' was not found on the local computer.
  Stack Trace:
     at Fluid.Tests.MiscFiltersTests.DateNumberIsParsedInLocalTimeZone() in D:\a\fluid\fluid\Fluid.Tests\MiscFiltersTests.cs:line 474
--- End of stack trace from previous location ---
----- Inner Stack Trace -----
   at System.TimeZoneInfo.FindSystemTimeZoneById(String id)
   at Fluid.Tests.MiscFiltersTests..cctor() in D:\a\fluid\fluid\Fluid.Tests\MiscFiltersTests.cs:line 14

Failed!  - Failed:    12, Passed:   881, Skipped:     0, Total:   893, Duration: 622 ms - Fluid.Tests.dll (net6.0)

The code is just

private static readonly TimeZoneInfo Pacific = TimeZoneInfo.FindSystemTimeZoneById("America/Los_Angeles");

You can see in the trace that it's effectively running in .NET 6 so I don't expect it to fail.

I have the same tests for net5.0 but using the TimeZoneConverter library, and this works fine. My goal is to remove this dependency when targeting net6.0.

System information:

Local machine:

Microsoft Windows 10.0.22000
.NET 6.0.0-rtm.21522.10
.... UseNls:                 False ....
.... Invariant:              False ....

GitHub agent:

Microsoft Windows 10.0.17763
.NET 6.0.0-rtm.21522.10
.... UseNls:                 True ....
.... Invariant:              False ....

I don't I should rely on the feature if it can break when running a not so recent OS version.

I confirm that adding the ICU package fixes the issue, though it's not ideal.

[safern]

but running the test using "windows-latest" in GitHub action returns this:

The "Windows-latest" VM in GitHub actions is: OS Version: 10.0.17763 Build 2300 which doesn't yet have icu.dll which we depend on to run using ICU, so since we couldn't find it we fall back to NLS, as you can see in your latest output, UseNls = true. In order to run using ICU on Windows you need to be on 1903 or later.

I confirm that adding the ICU package fixes the issue, though it's not ideal.

Well it is ideal if you want to control the version of ICU you depend on and you don't want to rely on OS environments and want to control that stability.

I see that github actions has a windows-2022 agent available already, which is: OS Version: 10.0.20348 Build 350, so maybe you could use that tag for now?

[safern]

@tarekgh I suspect something wrong in the routing framework when deployed on Azure app service. I updated my code to have swagger and i cannot even open swagger on the deployed version.

@nssidhu by any chance could you share a .zip with the published app layout that is running on Azure App Services?

[sebastienros]

so maybe you could use that tag for now?

I don't really care about mitigating the CI issues. Now that I know that it can "randomly" not work on some customers' machines I don't think I want to use the feature. That's not something that a library can enforce.

[safern]

Yeah I totally get that and makes sense. That was the intent of the app local feature. The downside is that an app switch needs to be set. I don't know if from a library it could be set early enough before globalization is enabled.

Maybe you can instead of stripping the feature out limit it to non windows and windows equals or later than 1903?

[tarekgh]

I don't really care about mitigating the CI issues. Now that I know that it can "randomly" not work on some customers' machines I don't think I want to use the feature. That's not something that a library can enforce.

It is up to you to decide to use the feature or not, but I wouldn't suggest not using it. Instead, you can have a fallback mechanism when the API returns false to you. The app author/user is in control. If the NLS mode is used, it is expected to have some limitations. That is why the APIs pattern is returning bool and the callers can decide the fallback they decide to go with. I am expecting in the near future very few users will be using NLS mode. We are already discouraging users from enabling it and using ICU app-local feature when ICU is not available. If you use the feature, you'll be covering most of the users.

Now to focus on the original issue that @nssidhu has, @pranavkm is going to look at the deployment of the app to Azure app service and will get back to us.

[pranavkm]

@nssidhu looks like Azure App Services will url decode all incoming routes. In your case, this results in the app selecting the fallback route because there isn't a route that matches api/WeatherForecast/GetTimeZonetime/{a}/{b}. Changing the route parameter to a catch-all parameter should resolve this issue and make it so that it works locally and on App Services:

- [Route("GetTimeZonetime/{TimeZone}")]
+ [Route("GetTimeZonetime/{**TimeZone}")]
[HttpGet]
public IActionResult GetTimeZonetime(string TimeZone)

[nssidhu]

@tarekhgh I am vacationing and won’t get chance until Nov 28th. Also on the other thread someone replied that the problem is because App Sevice auto decode url and then since it does not match with anything it falls back to index.html. That kind of make sense, but I also ran into issue that even swagger is not working. Will give a try after I come back from vacation. Sent from Yahoo Mail for iPhone On Friday, November 19, 2021, 12:13 PM, Santiago Fernandez Madero ***@***.***> wrote: @tarekgh I suspect something wrong in the routing framework when deployed on Azure app service. I updated my code to have swagger and i cannot even open swagger on the deployed version. @nssidhu by any chance could you share a .zip with the published app layout that is running on Azure App Services? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android.

[nssidhu]

@tarekgh

The issue was due to Routing. Azure App Service runs IIS as a Web Server. When Developing locally Kestrel is the default web server.

The problem was occurring because on Azure App Service, which run IIS, automatically decodes the encoded url and than it cannot find the route, after auto decoding the route becomes GetTimeZone/America/chicago, which does not exists.

The solution was to update the server controller methods signature to use asterisk(*) and it works, but this is somewhat dangerous option. The proper way should be to pass the timezone in post instead of get request.

Original which was running into problem
```
[Route("GetTimeZonetime/{TimeZone}")]
[HttpGet]
public IActionResult GetTimeZonetime(string TimeZone)
{
............................
}

Update method which does not run into error. _Note * (asterisk in front of TimeZone)_

[Route("GetTimeZonetime/{*TimeZone}")]
[HttpGet]
public IActionResult GetTimeZonetime(string TimeZone)
{
............................
}

App is deployed at 
https://blazorapptimezoneserver20211115142701.azurewebsites.net
Source code at
https://github.com/nssidhu/BlazorAppTimezone

[tarekgh]

@nssidhu thanks for the update. Your confirmation match what @pranavkm mentioned. By that I am closing this issue. Please let's know if you still have any issues here.