not connectivity issues
I am having issue of another sort with running Outlook 2007 in the Parallels 5 environment. Similar issue showed up in another part of the forum, but doesn't directly address an issue with 2007, but I feel are related. Let me give detail on this:
User has three Macs: Desktop at home, desktop at the office and a laptop. All three are running Snow Leopard OS. All three run Parallels 5.0. All three run Windows XP Professional. All three run Office 2007.
The issue is with Outlook 2007 and more specifically the Calendar with Daylight Savings Time. Items created in Outlook within the DST affected zones have invitees show up an hour later in their Outlook. The same thing applies to the users Blackberry. After applying DST patches to all XP OS on all machines and Outlook DST patches to Outlook, it pushes the dates, but they are still one hour off to all receiving attendees and also the Blackberry.
To further show what troubleshooting step I took, I made sure the OS for all machines had the adjust for daylight savings time check box marked. I also looked to Outlook Web Access and saw that those appointments show one hour off.
My logic shows that Exchange is reflecting the correct time for DST. OWA shows the correct time for DST. The Outlooks on all machine, while showing the times he set the appointments for correctly as they were set in Outlook, is not interpreting the data on the Exchange Server correctly. So the last thing to troubleshoot was Parallels, to which I found this:
Parallels 5 and DST structure
Nov 25, 2009, 11:34 PM
#1
Douglas Weber
Join: Nov 2009
Posts: 2
Parallels 5 and DST structure
--------------------------------------------------------------------------------
Using XP in Parallels 5 on Snow Leopard, the structure returned giving the DST information seems to be bad. We have an application that depends on this data and it is reporting that that data is not properly formatted. I do not know the API being called right now but will post it next week when I can get to the code. I have reverted to Parallels 4 and the problem goes away, so it is definitely a Parallels 5 issue. Is this a known issue and is a fix in the works?
Nov 30, 2009, 12:48 PM
#2
Douglas Weber
Join: Nov 2009
Posts: 2
Continuation of the DST issue
The following windows code is used to get the DST info:
TIME_ZONE_INFORMATION timeWarp;
DWORD tz_result = GetTimeZoneInformation(&timeWarp);
Our code splits this structure and sends the fields individually. The other side of this transaction reports
Month = 0
Day = 1
seconds = 7200
as not being valid for DST info
It looks promising, but is this a resolution? Am I supposed to make a change to a registry entry, or is this just pointing to an issue that exists?
What are your insights? So you have a better picture, Ive created new test appointments in Outlook 2007. OWA shows it an hour off and so does the Blackberry (within the DST affected dates). If I invite attendees, they show it an hour off also.