[mlynch@o-n.com]

I've been having a problem where users enter an appointment in their BB and when it shows up in their Outlook it's an hour later. At firest I thought it might be a DST thing, but I installed all the proper patches last year and had no issues until now. Then I remember that I had updated my Exchange server a couple weeks ago to solve an issue with it. I have an Exchange 2000 server on a Windows 2000 machine. My BES is 4.1 on a Windows 2000 machine. My CDO.DLL is the same version on the BES and Exchange. But the MAPI32.DLL is different on the two machines. Could this be the issue? Any other ideas?

[ashworth]

The only think i can think of is that Wndows server 2000 does not have the DST patch. You might need to use tzedit from MS to update the DST date and times on the BES or what ever box is windows 2000.

[hdawg]

Originally Posted by mlynch@o-n.com

I've been having a problem where users enter an appointment in their BB and when it shows up in their Outlook it's an hour later. At firest I thought it might be a DST thing, but I installed all the proper patches last year and had no issues until now. Then I remember that I had updated my Exchange server a couple weeks ago to solve an issue with it. I have an Exchange 2000 server on a Windows 2000 machine. My BES is 4.1 on a Windows 2000 machine. My CDO.DLL is the same version on the BES and Exchange. But the MAPI32.DLL is different on the two machines. Could this be the issue? Any other ideas?

Besides the fact that you need to upgrade, this is DST related; plain and simple.

CDO.dll is the one that handles the specifics of calendaring; not MAPI32.dll.

[mlynch@o-n.com]

Well, I am mystified, then. I performed all the DST 2007 updates last year and have had no problems until two weeks ago. So if you're saying that this can only be a DST issue, then something had to disable the DST patch. Do you think the Exchange Server patch I installed did this?

[ashworth]

I dont think the issue is with Exchange or the BES's cdo.dll or mapi32.dll (asuming they are the proper versions).

I think the issue is with Windows 2000 server. There is no DST Patch for Windows 2000 server. You have to patch the server yourself with a reg hack or tzedit.

See the following link to check to make sure your windows 2000 server has the proper DST times:

How to configure daylight saving time for Microsoft Windows operating systems

[mlynch@o-n.com]

Thanks for your reply! Unfortunately, the time on both of those servers changed appropriately with the new DST, and is correct now. I had applied the registry hacks last year. I'm mystified as to what this could be.

[ashworth]

ok so then lets look at the mapi and cdo versions.

The value of '(Default)' will be the path of the registered CDO.dll in
"HKEY_CLASSES_ROOT\CLSID\{3FA7DEB3-6438-101B-ACC1-00AA00423326}\InprocServer32"

Then check the version of that cdo.dll.

[mlynch@o-n.com]

I'm assuming this is on the BES, not the Exchange server?

[ashworth]

Yah or both. The more information the better

[mlynch@o-n.com]

This is what I have:

BES 4.1 server (Windows 2000 Server SP 4):

cdo.dll v 6.0.66.0.0 Exchsrvr\BIN
mapi32.dll v 6.0.6487.1 Exchsrvr\BIN
mapi32.dll v 6.0.6487.1 WINNT\system32

Exchange 2000 SP4 (Windows 2000 Server SP 4):

cdo.dll v 6.0.6603.0 Exchsrvr\BIN
mapi32.dll v 6.0.6603.0 Exchsrvr\BIN
mapi32.dll v 6.0.6603.0 WINNT\system32

[mlynch@o-n.com]

Here's something I found on the BB KB, which seems to address my issue, but doesn't say whether I can/should update the MAPI32.dll:

Doc ID : KB02937
To verify that you are using the correct cdo.dll file version, check the version of the mapi32.dll file on the BlackBerry Enterprise Server, then use the table below to check the corresponding version of the cdo.dll file.

Note: For instructions on how to locate the cdo.dll file, and to verify that it is registered, see KB04912.

Microsoft Exchange Administration Tool version
cdo.dll version
mapi32.dll version

Microsoft Exchange 5.5 Administrator
5.5.2657.55
5.5.2653.12

Microsoft Exchange 2000 System Manager
6.0.6487.2
6.0.6487.1

6.0.6603.0
6.0.6603.0

Microsoft Exchange 2003 System Manager
6.5.6980.3
6.5.6944.0

6.5.7226.0
6.5.7226.0

6.5.7651.61
6.5.7638.1

[mlynch@o-n.com]

Found this, too, which seems to directly address the problem. I have applied the same Exchange patch to the BES as I did to the Exchange server, but the mapi32.dll on the BES i s still older. Can I simply copy and paste the mapi32.dll from the Exchange server?

Exchange Administrator or Exchange System Manager

This requirement will be based on the version of Microsoft Exchange that you are using in your environment. The BlackBerry Enterprise Server software version should always be at an equal or later version of Exchange Administrator (Microsoft Exchange 5.5) or Exchange System Manager (Microsoft Exchange 2000 and Microsoft Exchange 2003). To verify this, complete the following steps:

On the BlackBerry Enterprise Server, search for the following three files:
CDO.dll
EMSMDB32.dll
MAPI32.dll
Record the locations and versions of the files found in step 1.
Repeat this process on the Microsoft Exchange Server (if there are multiple Microsoft Exchange Servers in the environment, repeat the process for all instances).
If the file versions that exist on the BlackBerry Enterprise Server are not equal to, or later than, those on the Microsoft Exchange Server, you must upgrade the software on the BlackBerry Enterprise Server.

[mlynch@o-n.com]

The good news: I figured out that there are 3 different Exchange SP3 rollups, that are identified as SP4, and I had installed an earlier version on the BES. So I downloaded and installed the correct one and the mapi32 and cdo are all in alignment now.

The bad news: I still am getting the one hour offset in Outlook.

[mlynch@o-n.com]

So the saga continues. I contacted RIM support and we ran through everything and it all checked out as far as the BES server and it's configuration and patching. They ended up telling me that the patch I appled to my Exchange server, KB870540, which gives me the CDO and MAPI32 versions I mentioned previously (6.0.6603.0), somehow do not "contain" the DST patch. I tried to tell them that when I look in my registry, I see the DynamicDST key under Timezones which is the concrete indicator that the DST patch was applied and still exists.
Can anyone solve this conflict? IS it that even though the DST patch is applied, the CDO version somehow ignores it?

[kapasaca]

Originally Posted by mlynch@o-n.com

This is what I have:

BES 4.1 server (Windows 2000 Server SP 4):

cdo.dll v 6.0.66.0.0 Exchsrvr\BIN
mapi32.dll v 6.0.6487.1 Exchsrvr\BIN
mapi32.dll v 6.0.6487.1 WINNT\system32

Exchange 2000 SP4 (Windows 2000 Server SP 4):

cdo.dll v 6.0.6603.0 Exchsrvr\BIN
mapi32.dll v 6.0.6603.0 Exchsrvr\BIN
mapi32.dll v 6.0.6603.0 WINNT\system32

cdo.dll must be equally new or newer on the BBserver.
In your case you need to copy the cdo.dll v 6.0.6603.0 to the BBserver and register it. start run --> regsvr32 "location of the cdo.dll"

this might not fix it, but at least it will be in order.

[Aerospace_Cadet]

There has been more then one DST patch supplied by Microsoft. The latest one I do believe was put out in March of 08 which included the changes in DST for New Zealand.

[knottyrope]

Originally Posted by Aerospace_Cadet

There has been more then one DST patch supplied by Microsoft. The latest one I do believe was put out in March of 08 which included the changes in DST for New Zealand.

You are right, and it messed up my BES on w2k.

I used the Tzedit to fix it.
BES was looking at server time.

But after the date for the time change it would equal out. Was too lazy to change it last fall.

Now all is well I hope for this fall.