BlackBerry® Enterprise Service 10

[jhanff]

CDOCalendar:rocessWindowsTimezoneInfo- No Index value present

I have this error in the event log every 10 minutes.

What does it mean?

[bbinmyhart]

Means nothing.

[kerseyr]

Check this out..

http://coreygilmore.com/blog/2009/06/01/bes-5-0-fix-for-processwindowstimezoneinfo-warning/

Not going to steal the glory.... I found it with google :-)

Respect to Cory!!

[kerseyr · Accepted solution]

And the official line...

http://www.blackberry.com/btsc/microsites/search.do?cmd=displayKC&docType=kc&externalId=KB18396&slic...

[Delta]

If you're using W2K8 - 64bit, there are now 4 keys that need to be added:

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Research In Motion\BlackBerry Enterprise Server\Time Zone Identification\Mauritius Standard Time]
"StdKeyName"="Mauritius Standard Time"
"Index"=dword:8000004f

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Research In Motion\BlackBerry Enterprise Server\Time Zone Identification\Kamchatka Standard Time]
"StdKeyName"="Kamchatka Standard Time"
"Index"=dword:80000052

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Research In Motion\BlackBerry Enterprise Server\Time Zone Identification\Paraguay Standard Time]
"StdKeyName"="Paraguay Standard Time"
"Index"=dword:80000051

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432node\Research In Motion\BlackBerry Enterprise Server\Time Zone Identification\UTC]
"StdKeyName"="UTC"
"Index"=dword:80000050

and you'll have to keep adding them from this list as new ones are created:

http://support.microsoft.com/kb/973627

[y0gurt]

OK, This has been a problem for us so I spent some time on it and thought I'd share. Our problem is still not resolved but hope this helps get to a solution. If you have any suggestions or see errors below please let us know. We would like to close this one.

We have a Windows 2008 64-bit server with BES 5.0 MR2 and errors keep filling up our log (with my name attached...)

 

Below are the settings/registry keys in question. This is from an export of the BES registry and merged with the Microsoft Time Zone Index Values put into an Excel spreadsheet.

Findings:

Ten of the Time Zone Identification formats in MS kb973627 do not match the "StdKeyName" registry keys in BES, but the HEX Index number keys do (highlighted in red).

Two additional zones are missing (Mexico Standard Time 2 and Mexico Standard Time) so six total need to be added on 09/02/09 if you are running BES 5.0 MR2 on a Windows 2008 64-bit server.

Settings/registry keys in question

Index (hex): F
Name of Time Zone U.S. Mountain Standard Time
(Hex) Index=dword: 0000000f
StdKeyName:  US Mountain Standard Time
Time Zone Identification:US Mountain Standard Time
 
Index (hex):  28
Name of Time Zone U.S. Eastern Standard Time
(Hex) Index=dword: 00000028
StdKeyName:  US Eastern Standard Time
Time Zone Identification:US Eastern Standard Time
 
Index (hex):  2D
Name of Time Zone S.A. Pacific Standard Time
(Hex) Index=dword: 0000002d
StdKeyName:  SA Pacific Standard Time
Time Zone Identification:SA Pacific Standard Time
 
Index (hex):  38
Name of Time Zone Pacific S.A. Standard Time
(Hex) Index=dword: 00000038
StdKeyName:  Pacific SA Standard Time
Time Zone Identification: Pacific SA Standard Time
 
Index (hex):  46
Name of Time Zone S.A. Eastern Standard Time
(Hex) Index=dword: 00000046
StdKeyName:  SA Eastern Standard Time
Time Zone Identification: SA Eastern Standard Time
 
Index (hex):  AF
Name of Time Zone Transitional Islamic State of Afghanistan Standard Time
(Hex) Index=dword: 000000af
StdKeyName:  Afghanistan Standard Time
Time Zone Identification: Afghanistan Standard Time
 
Index (hex):  CD
Name of Time Zone S.E. Asia Standard Time
(Hex) Index=dword: 000000cd
StdKeyName:  SE Asia Standard Time
Time Zone Identification: SE Asia Standard Time
 
Index (hex):  F5
Name of Time Zone A.U.S. Central Standard Time
(Hex) Index=dword: 000000f5
StdKeyName:  AUS Central Standard Time
Time Zone Identification: AUS Central Standard Time
 
Index (hex):  FF
Name of Time Zone A.U.S. Eastern Standard Time
(Hex) Index=dword: 000000ff
StdKeyName:  AUS Eastern Standard Time
Time Zone Identification: AUS Eastern Standard Time

Index (hex):: D
Name of Time Zone: Mexico Standard Time 2
(Hex) Index=dword: - missing
StdKeyName::  - missing
Time Zone Identification: - missing 
 
Index (hex): 1E
Name of Time Zone: Mexico Standard Time
(Hex) Index=dword: - missing
StdKeyName::  - missing
Time Zone Identification: - missing 

On a lighter note, the funniest thing I found was that the Timezone for Brussels, Copenhagen, Madrid and Paris is called the "Romance Standard Time" and the index number is 69....I almost fell off my chair laughing.... I know... get my head out of the gutter... Who thinks this stuff up?

Anyways, hope it helps.

[knottyrope]

---

y0gurt wrote:

On a lighter note, the funniest thing I found was that the Timezone for Brussels, Copenhagen, Madrid and Paris is called the "Romance Standard Time" and the index number is 69....I almost fell off my chair laughing.... I know... get my head out of the gutter... Who thinks this stuff up?

Anyways, hope it helps.

---

That is too funny thanks for sharing it.

[y0gurt]

Update - Applied the fixes listed above today on the production system and it resolved the problem.

[y0gurt]

Scratch that - problem is back...

[bulletooth]

Has this issue been solved? I have followed the instructions in BTSC KB18396 and still have this error.

My understanding is that there are other time zones that need to be entered but want to verify which ones. RIM's documentation fails to acknowledge other time zones.