[ChrisSnape]

Hi People,

First post on here after running out of available info searching the web.

I have got a Windows Server 2003 SP2 running Exchange Enterprise 2003 SP2.

I have recently started to use BESX Version 5.0.3.41 on the same Server.

I have been through the trauma of setting up the BESAdmin account and have gor about a dozen Blackberries all working now via them picking up the users through active directory etc. etc.

BUT... Two things are still annoying me:

1. One BB user keeps putting Event ID 1639 into the servers Application Event log. Every 10 minutes. Is this to do with the Blackberry or the Mailbox? I figure it has nothing to do with the overall setup else every BB user would get it.

2. I get MAPI errors when using Backup Exec 2010 (on another server - agent installed on Exchange/BESX server) when using our overnight backup.

All I want to know is if I have BESX and Exchange on the same box do I need to worry about the MAPI/CDO install or will this be sorted out because they live on the same server? I have had a a look in 'Add/Remove Programs' but cannot see the seperate install of the MAPI/CDO thing but guess that is only required when BESX is on a seperate server. So can I rule this whole MAPI/CDO install thing out?

If so what is my next check? Is my first issue related to my second?

Thanks in advance for the help.

Regards,
Chris Snape

[freakinvibe]

Has been solved here:

Event ID 1639 MsExchangeCDO warning every ten minu... - BlackBerry Support Community Forums

[rambo47]

Is #2 related to this: Enterprise Support - Symantec Corp. - Backup Exec 2010 revision 2896 Hotfix 348284

[ChrisSnape]

Originally Posted by freakinvibe

Has been solved here:

Thanks for the tip but it says 2007/2010 only for exchange.

Originally Posted by rambo47

Is #2 related to this:

Cheers but I haven't got any more hotfixes via liveupdate to download and I updated the agents afterwards.


The event ID is only coming up for one user, could it be something in that specific mailbox/blackberry setup? They are all using the same default IT policy though.

[rambo47]

I've seen these isolated "hiccups" with individual users and sometimes the only cure is to completely wipe that user's account off the BES system and then recreate it from scratch. That means re-activating the handset and restoring previous emails to the device. Beware the number of emails that can be restored and the limit on how far back the restore can go. 2 weeks?

[knottyrope]

are both backup exec and BES using the same exact CDO version?

I am running similar to you and dont have those errors, but I am on BES 4.1.7 not BES 5

[ChrisSnape]

Originally Posted by knottyrope

are both backup exec and BES using the same exact CDO version?

I am running similar to you and dont have those errors, but I am on BES 4.1.7 not BES 5

I didn't realise that BackupExec used CDO too? How do I check it again? Would it be worth just upgrading them anyway so I can tick it off?

Looking at the Microsoft Link microsoft.com/download/en/details.aspx?displaylang=en&id=1004 I can see there are two to download - is one for the Exchange server and one for the non-exchange server (Backup Exec server)?

PS. We did upgrade our Backup exec version on the same weekend we installed BESX.

[ChrisSnape]

Ok, been searching around for possible solutions for the BackupExec issue...

Does it matter that my Exchange/BESX server is currently logged in as Domain Administrator instead of BesAdmin? Everything to do with BESX seems to be working ok regardless. (I guess it is the reason I get an error when I click on the Edit MAPI profile while logged on as Administrator - right? I know not to mess with that though)

Secondly - do I need to change the credentials on the Backup Exec server to use BesAdmin instead of Administrator? Or is that a red herring?

Also, when searching for cdo.dll and mapi32.dll on the BESX/Exchange server and the BackupExec server I couldn't find them?

Sorry for yammering on but I figure more info the better.

[knottyrope]

Since you have not proven CDO versions are the same

search all files and folder including hidden ones for CDO.DLL

you will find them, then look at properties of the CDO file version.

[ChrisSnape]

Ok, thanks for the advice so far.

Exchange server has CDO.dll - 6.5.7654.12

I cannot find CDO.dll on the Backup Exec Server at all. Checked everywhere.
Could that be the issue? Do I need to install v1.2.1 from Microsofts link?

[knottyrope]

is the backup server separate from the mail/BES server?

if yes, then you need to install ESM on it

[ChrisSnape]

Yes, the Backup Exec server is separate.

Are you saying that my other server needs Exchange System Manager installing!?

Never had to do that before I installed BESX - Backup Exec server used to backup Exchange server fine, no issues. It is only since the installation of BESX (and the upgrade of Exchange to Enterprise and the Upgrade of Backup Exec to 2010) that it has started the MAPI issues.

[ChrisSnape]

Ok, I took your advice and installed ESM onto the Backup Exec server and patched it with SP2. The version is the same in ESM now but the CDO.dll is slightly different:

Exchange/BESX: 6.5.7654.12
Backup Exec: 6.5.7638.2

Not sure how to get them to match. Checked Windows Update on the Backup Exec, nothing to download. Tried the MAPI download but it says wrong version of Exchange but TBH I don't want to mess with the Exchanger Server CDO.dll, just the Backup Exec one to match.

Shall I leave them like this and see what happens with Reference to the MAPI error in Backup Exec?

[knottyrope]

windows update wont do it. you have to run microsoft update.

[ChrisSnape]

Ok, got it. Both on same version now - 6.5.7654.12

It failed last night but they were the different versions still. Trying some backups to disk today so I can do more tests in one day.

Fingers crossed.

[jmckey]

Curious to know if that resolved it. Ping us on twitter (@backupexec) if you are still having issues backing up Exchange.

[ChrisSnape]

To close this thread:

I managed to resolve the issue in the end. It wasn't BESX's fault but Backup Exec. Since upgrading it to 2010 there are issues when backing up Exchange when using Advanced Open File Option. As it was one backup it was selected. I split the backup job so it did all Exchange and SQL backups first WITHOUT AOFO selected and then a secodn job for all the files etc. WITH AOFO selected. This resulted in successful backups.

Not sure if this would have been the case without the previous MAPI changes but just glad I got there. Thanks all for your assistance.

[knottyrope]

AOFO and databases dont work well. I too have separate jobs for them.

Thanks for coming back with more info to share with us.