[JavaJunkee]

Has anyone tested Server 2008 64-bit yet?

I've built out some Server 2008 64-bit servers, to test the new BES 5.0 High Availability function. I'm having trouble getting MAPI32.DLL to install.

I'm using ExchangeMapiCdo.exe, version 6.5.8069.0. The install runs without error and I can locate CDO.DLL. But MAPI32.DLL is no where to be found. I then took the ExchangeMapiCdo.exe file and applied it to Server 2003 and it installed both CDO.DLL and MAPI32.DLL as expected.

Keeping this breif for now and will provide further info if needed.

Let me know if any of you have had similar issues.

[sweater]

Originally Posted by JavaJunkee

Has anyone tested Server 2008 64-bit yet?

I've built out some Server 2008 64-bit servers, to test the new BES 5.0 High Availability function. I'm having trouble getting MAPI32.DLL to install.

I'm using ExchangeMapiCdo.exe, version 6.5.8069.0. The install runs without error and I can locate CDO.DLL. But MAPI32.DLL is no where to be found. I then took the ExchangeMapiCdo.exe file and applied it to Server 2003 and it installed both CDO.DLL and MAPI32.DLL as expected.

Keeping this breif for now and will provide further info if needed.

Let me know if any of you have had similar issues.

IIRC, BES running on Server 2008 64bit was just fine. I used the following to satisfy the prereq's:

Collaboration Data Objects, version 1.2.1

In fact, I used that package when installing BES 5.0 on any server (2k3, 2k8, 32 or 64bit).

Hope that helps...

[JavaJunkee]

Thx for the reply.

That version is slightly older. Tried it anyway and received an error stating, "Collaboration Data Objects 1.2.1 cannot be installed unless Microsoft Office Outlook 2007 is also installed."

My research has found installing CDO.DLL/MAPI32.DLL to Server 2008, to be an issue. See link below.

" This Just In: MAPI and Windows Server 2008 Now Get Along "

[JavaJunkee]

I found the below, which explains the issue a bit more clear. If I understand this correctly, CDO.DLL and 'EXMAPI.DLL' no longer reside within C:\Windows\system32\. I'm going to trudge ahead and install BES 5.0 and see what happens.

Exchange Messaging Outlook June 5 2008

Microsoft released an update for the MAPI/CDO download package that works on Windows Server 2008 and Vista.

Exchange's MAPI has always replaced mapi32.dll with its own version and Windows Server 2008 and Vista mark mapi32.dll as a system file so that any attempt to replace it would be blocked or undone. Microsoft fixed this by moving the MAPI binaries out of the system32 folder and into Program Files\ExchangeMAPI. They also renamed Exchange's mapi32.dll binary to ExMAPI32.dll.

If you have an earlier version of this package installed, you need to uninstall it first; you can't do an in-place upgrade. MAPI and CDO are 32 bit only. You can install it on a x64 machine but it only works with 32 bit applications.

[rsenio]

I'm testing BES right now on Win 2008 64-bit Hyper-V guest OS, works great. I used this http://www.microsoft.com/downloads/d...2-0a110307611e

[JavaJunkee]

@rsenio

Thank you for the reply, that's the same package that I used. The issue was it took me a bit of research to find that:

1. The location of CDO.DLL and EXMAPI32.DLL (previously MAPI32.DLL), has been changed from %SYSTEMROOT%\system32 to C:\Program Files (x86)\ExchangeMapi\.

2. The MAPI32.DLL file has been renamed to EXMAPI32.DLL.

It wasn't clear to me on the MS site, that this change had been made.

My BES 5.0 test environment, on ESX 3.5 update 3, is working like a charm.

I've also set up the new High Availibility for BES and database mirroring:

BES - Server 2008 64-bit (2 total)

Primary
Standby

MS SQL Server 2005 - Server 2008 64-bit (3 total)

Principal
Mirror
Witness

[Bigkahunatuna]

I have a similar setup Windows 2008 x64 SP2, BES 5 and Exchange 2007 SP2, only issue I'm having is appointments created in Blackberry are not being pushed down to the Exchange, but the inverse is not a problem. Everything I have researched indicates that CDO is the culprit.

The article written by Stephen Griffin I found misleading. Is he suggesting that we move the MAPI32.DLL out of c:\windows\system32 and c:\windows\syswow64 into c:\program files (x86)\exchangemapi? I've attempted this and moving mapi32.dll out of syswow64 will cause Blackberry MailStore to fail on start-up.

Any recommendations to help me solve this issue?