We have installed MBS-2009 CTP2 for development and have an issue with then RTC on Terminal Server. The SQL-Database, 3-Tier server and RTC clients are installed on different machines and work fine, accept for the RTC clients on terminal server. The message I receive is as follows:
"The time zone with ID 'West-Europ (standaardtijd)' was not recognized on the server. Update your computer's time zone defenitions.
I've checked and the timezones on all local machines, servers en terminal server is "GMT +1:00 Amsterdam, Berlin...
Has anyone, any suggestion were or what to look for.
Thanks for your reply
It sounds like the information in your client's system registry may not be correct. Could you please provide (1) the OS version (2) the OS intallation language, and (3) a screenshot of one or two of the subkeys under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones (for example HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\W. Europe Standard Time)?
My local machines are running Windows XP3 and the remote sessions on Terminal server are running on a Windows 2003 R2 Enterprise SP2 machine.
The registry setting on my local machine were it's working are:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\W. Europe Standard Time]"Display"="(GMT+01:00) Amsterdam, Berlijn, Bern, Rome, Stockholm, Wenen""Dlt"="West-Europa (zomertijd)""Std"="West-Europa (standaardtijd)""MapID"="2,3""Index"=dword:0000006e"TZI"=hex:c4,ff,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,0a,00,00,00,05,00,03,00,00,\ 00,00,00,00,00,00,00,03,00,00,00,05,00,02,00,00,00,00,00,00,00
The registry setting on my Terminal server is:
Windows Registry Editor Version 5.00[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones\W. Europe Standard Time]"Display"="(GMT+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna""Dlt"="W. Europe Daylight Time""Std"="W. Europe Standard Time""MapID"="2,3""Index"=dword:0000006e"TZI"=hex:c4,ff,ff,ff,00,00,00,00,c4,ff,ff,ff,00,00,0a,00,00,00,05,00,03,00,00,\ 00,00,00,00,00,00,00,03,00,00,00,05,00,02,00,00,00,00,00,00,00
The setting are more or less the same,except for the language difference. My local machines run a dutch windows xp and my Terminal server runs a English version. The windows Servers where my SQL database and navison Server-Tier are installeled both run on the same Windows 2003 version (English).
Because of security settings on Terminal server I can not look into the registry settings of a user, but I can see in the regular windows timezone screen that it's the same there. The registry setting shown above (windwos 2003) are copied with the administrator account.
Does this give you any clue?
Do you have access to SP1? I have been told that the timezone messages were removed from that version.
Hi Michel van den Heijkant,
i think your problem wil fixed if you check Server time zone then RTC's time4 zone. i think your server has another time zone and your client computer has another time zone. you must have same time zone. so this have message give you.
In 2009 SP1, it is no longer required that client and server be in the same time zone. I believe Michel is encountering this problem using 2009 SP1 CTP2. Is that correct?
I'm investigating the issue.
Could you please execute the attached exe from a command prompt and post the output? The source is also included. The code won't make any changes to your system.
I've added a document with the printscreen of the results.
It looks about the same, with a minor difference on Terminal server, when logged on as a user or as an administrator.
thanks for your help. What i've done is, change the timezone to something different, and then changing it back.
With this, the correct timezone setting is configured and the RTC client now works on Terminal server.
Only problem at this moment is that the timezone isn't saved after leaving the RDP session, but we will figure this out ourselves.
Probably a registry setting thats distributed with Group Policies.
Again thanks for your help.
That's good to hear. The time zone set for the RDP user wasn't valid because the ID should never translated (the DisplayName wasn't correct either). I hope you will be able to figure this one out!
I just had the same problem with a client and found that Microsoft has actually released a hotfix for this. More information available here: