inforCRM Web Client TimeZone stuck on Chetumal

Several users are noticing their Web Client timezone is (UTC-05:00) Chetumal. It is my understanding it uses the PC's timezone for this. None of the PC's are set to Chetumal.

Thoughts? Anyone else notice this?

8.1 3b is the version we are one. Experienced in Chrome and IE.

Find more posts tagged with

Comments

Legacy Contributor

Hi,

Which time zone is your user in? Is only the name wrong or also the utc stuff?

I had seen this in 8.1 with german time zone, but in my case only the name was wrong and the utc was correct.

Legacy Contributor

One user is experiencing this in the wrong time zone with the wrong UTC time.

Legacy Contributor

Hi,

Well, the time zone from the client is taken if it is possible to do so. If not, it uses the server time zone.

You mentioned that you see this in two browsers. Does it work, if the user tries to login from a computer where it works for other users?

Legacy Contributor

First thing we checked was users Time Zone. It is set correctly for him. Also checked the time zone for the server and it is correct for its location. I have tried it in multiple browsers and each one shows Chetumal. If I set the time zone to the correct one in the web client, when I log back in it has returned to showing Chetumal.

Legacy Contributor

Every time you re-login it will try to grab the new time zone from the client.

There is a javascript called timezone.js which calculates the time zone.

You can put some altering in and see what it gets from the client. In my case, the hour calculation was wrong and this was why it got the wrong time zone.

tiffanykai-king

I noticed this issue in our test environment after activating Windows login. I came up with a quick and dirty workaround -- I haven't used it in production, but it seems to work.

This only applies to Windows login, since the authentication page is different from Forms login.

Essentially, I removed the reference to timezone.js from WinAuthLoad.aspx. Then I copied the time zone initialization C# code from the Page_Load of Login.master, and pasted it into Button1_Click in WinAuthLoad.aspx.cs. This seems to eliminate the problem, and initialize the user's time zone correctly.

Again, just a quick and dirty workaround -- I can post the code if anyone wants to try it.

tiffanykai-king

Did some additional testing on this and it doesn't work as advertised. (But it works great if you want to force everyone to use the server's timezone!) Looks like a fix is needed to the JS file.

Copyright © 2025 Infor. All rights reserved.