Russian Time Zones in MS CRM 2011

(2) Share

Report

Posted on by Community Member

Hello!

Since Friday we've been experiencing a problem with our MS CRM 2011 Rollup 18 on-premise installation. Whenever we create a record (e.g. new Opportunity), its CreatedOn becomes current datetime + 1 hour. This also applies to other system dates, like ModifiedOn, records in Audit etc. We've been able to narrow the problem down to the TimeZoneRuleBase table, where we found some incorrect time zone rules. In particular they state that fields with date value set between 7th August 2015 to 26 October 2015 should have an additional offset.

We also have found a bugfix for MS CRM 2013 here: https://support.microsoft.com/en-us/kb/2963850 :

Daylight Saving Time changes for Russian Time Zones.
With the windows DST patch for Russia and UR 18 installed, fields with date value set between 7th August 2015 to 26 October 2015 have an incorrect time offset.

However, we cannot find a solution for MS CRM 2011. We tried several options, e.g. fixing the timezone table ourselves, but no luck so far. It usually results in all kinds of unexpected behaviour. I'm aslo afraid that a manual hotfix can complicate our future upgrade to 13/15 versions of CRM.

So, what should we do now? Is there any possibility that MS will release a patch for CRM 2011? It's really frustrating that MS updated CRM 13 but not 11, which is still supported...

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Community Member on at

Like (0)

Report

We faced the same problem. Manual fix of timezone tables doesn't lead to correct datetime values. It seems that such behavior is hardcoded.

There is no information about expected UR19 release date and no special patch.

Is it a new type of sanctions against Russia?..

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

In CRM 2013 were fixed rules for RTZ in TimeZoneRuleBase

In CRM 2013 org base find out your TimeZoneRuleId in Timezonedefenitionbase by Userinterfacename info

then

copy from TimeZoneRuleBase

Create new rule for CRM 2011 in SQL

We are testing now in crm 2011 Moscow +3 RTZ

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Tried this for 2011. Doesn't help.

Was this reply helpful? Yes No
Community Member on at

Like (1)

Report

For Moscow +3 RTZ

CRM 2013

select * from TimeZoneRuleBase where TimeZoneRuleId = '5F8807C7-D29B-4D1D-A960-F0CE0E67C568'

for 2011

insert into TimeZoneRuleBase .....

Was this reply helpful? Yes No
Wayne Walton 13,730 on at

Like (0)

Report

I would open a support ticket with Microsoft. It's possible they have a hotfix for 2011 but haven't made it public. Some issues like this require going through them, as those fixes get listed as "rapid release" instead of "general release".

Was this reply helpful? Yes No
Vladislav Osmanov 55 on at

Like (0)

Report

Solution from Alexander Valyushkin works for us. But after inserting new time zone rule you have to restart CRM AppPool and site.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Solution works, date fields in CRM show correct values (and utc dates in DB are also correct). But unfortunately Filtered Views still return wrong local time.

Was this reply helpful? Yes No
Vladislav Osmanov 55 on at

Like (0)

Report
Filtered Views use this function to convert UTC time:

dbo.fn_UTCToTzSpecificLocalTime([entity].[field_name], us.TimeZoneBias, us.TimeZoneDaylightBias, us.TimeZoneDaylightYear, us.TimeZoneDaylightMonth, us.TimeZoneDaylightDay, us.TimeZoneDaylightHour, us.TimeZoneDaylightMinute, us.TimeZoneDaylightSecond, 0, us.TimeZoneDaylightDayOfWeek, us.TimeZoneStandardBias, us.TimeZoneStandardYear, us.TimeZoneStandardMonth, us.TimeZoneStandardDay, us.TimeZoneStandardHour, us.TimeZoneStandardMinute, us.TimeZoneStandardSecond, 0, us.TimeZoneStandardDayOfWeek), [entity].[field_name]

`us` is alias for UserSettings view.

For RTZ 2 all users must have -180 in TimeZoneBias and 145 in TimeZoneCode. But it's not enough, I assume that right value for TimeZoneDaylightBias must be 0 not -60.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Can anybody provide query result (we still work on CRM 2011 and, so, can't execute query on CRM 2013)?

Was this reply helpful? Yes No
Vladislav Osmanov 55 on at

Like (0)

Report
INSERT INTO TimeZoneRuleBase( StandardDay, ModifiedOn, StandardMinute, StandardBias, StandardYear, DaylightMonth, StandardDayOfWeek, DaylightSecond, Bias, TimeZoneRuleVersionNumber, DaylightBias, StandardMonth, EffectiveDateTime, DaylightHour, StandardHour, CreatedOn, DaylightYear, StandardSecond, DaylightMinute, TimeZoneDefinitionId, DaylightDayOfWeek, TimeZoneRuleId, DaylightDay) VALUES( 0, getutcdate(), 0, 0, 0, 0, 0, 0, -180, 18, -60, 0, CONVERT(DATETIME, '2015-01-01', 111), 0, 0, getutcdate(), 0, 0, 0, 'F6A0CC2F-7EC6-4F34-9CCC-9C2029D23EBF', 0, '5F8807C7-D29B-4D1D-A960-F0CE0E67C568', 0)

Recycle CRM App Pool and restart website.

To fix time in filtered views I have used this script:

UPDATE UserSettingsBase SET TimeZoneBias = -180, TimeZoneDaylightBias = 0 WHERE TimeZoneCode = 145

Was this reply helpful? Yes No