Mailbox sync problems (0x8004011d)

[Brian_Spooner]

Our EV 6.0 SP1 server no longer seems to be able to syncrhonize mailboxes. It logs 2270 and 3277 events for every mailbox when it tries to sync:

Event Type:Error
Event Source:Enterprise Vault
Event Category:Archive Task
Event ID:3277
Date:2/8/2006
Time:9:11:19 AM
User:N/A
Computer:BCCKVS0101
Description:
The MAPI error MAPI_E_FAILONEPROVIDER (0x8004011D) has occurred whilst synchronizing the properties of mailbox /o=Collier County Gov./ou=ITDOMAIN/cn=Recipients/cn=ramseym.

The mailbox will not be synchronized until the next scheduled run.

.\AgentExchSynch.cpp (CAgentExchSynch::SynchronizeMailboxEntry) built Nov 17 18:39:08 2005



Anyone ran across this before? Any ideas? We've deleted all the vaultmbx Outlook profiles, mapi files on EV server are fine, reset service account password, etc...

Any help is greatly appreciated. Thanks!

-Brian Spooner

[TonySterling]

You might want to verify the system mailbox ev is using is ok. try opening it on the ev server. Another thing is verify the permission for the VSA on exchange, make sure a GPO has not changed it.

[Brian_Spooner]

Also, the vault service account is NOT a member of Domain Admins and has been granted Exchange Full Administrator rights at the Admin. Group level in Exchange System Manager. I verified that it has send as & receive as rights on the information stores as well.

[Brian_Spooner]

I am able to open the vault system mailbox "vaultmbx" in Outlook from the EV server without any problems.

[Jason_Szeto]

Hey Brian,

It's been a while. Anyway, usually those mapi errors are related to Outlook or the mapi files. I don't remember what version of Outlook was installed on your server. Since SP1 discontinued support for Outlook 2000, do you have Outlook 2003 installed on your EV server?

I'm curious to see what happens if you try to enable a mailbox, if you get errors with that too.

[Brian_Spooner]

Hi Jason,

Yeah, it's been awhile. I just checked and the EV server has Outlook 2003 installed. Version 11.5608.5606. I believe that's the original Outlook 2003 without any service packs. Is it worth upgrading it? Would it support Outlook 2003 SP2? We were just getting ready to upgrade the Exchange Servers to SP2 in the next week or so also.

I DO get an error when trying to enable a mailbox. "An error occured enabling the mailbox. Error: the server is not operational"

What do you think?

[Jason_Szeto]

I would try upgrading to Outlook 2003 SP2 and see if that fixes it. SP2 is supported. Here's the announcement.

http://seer.support.veritas.com/docs/281568.htm

Here's what I would try as well. Do a dtrace of the MMC, try to enable the mailbox again and see what error is reported in the trace.

[Jason_Szeto]

Oh one more thing you might want to try is look in SQL in the EnterpriseVaultDirectory database and check all your tasks and see what it has listed for your System mailboxes. If they are using the Exchange alias names, try using the SMTP email address of the system mailbox instead. The correct format is SMTP:email@symantec.com.

[Brian_Spooner]

I just found out that when I tried enabling the mailbox earlier, we were having a problem with one of the DCs in this site. Apparently Symantec AV Corp. 10.0.1.1000 can cause problems on some 2003 servers: http://service1.symantec.com/SUPPORT/ent-security.nsf/pfdocs/2005082910334448?Open&dtype=corp

Anyway, after this DC was rebooted, I attempted to enable the mailbox again and it worked. I'm beginning to wonder if that's what is causing problems with the mailbox sync as well. However, I tried a manual sync again and still get the errors.

I'll upgrade Outlook 2003 to SP2 on the EV server as well and see if this helps.

[Brian_Spooner]

Which table would that be in? I checked 'Task' but did not see a reference to a system mailbox.

[Jason_Szeto]

I'm doing this from memory but I think these are the tables.

JournalTaskEntry
RetrievalTaskEntry
ArchivingTaskEntry