Only 1 out of 2 Exchange instance is archiving mail

[Paultje]

Hi, we have a Microsoft Exchange cluster (MS clustering, 2 nodes only) where we introduced EV on last year. We only had 1 Exchange (81) instance at that time. Archiving was no problem, all activated mailboxes were archived, no matter on which node it's running. Due to performance issues we made a new Exchange instance (82) on the passive node. So now we have 2 active nodes with each 1 active Exchange Instance. EV was also implemented on the new node and arcviving is no problem.

But now it seems that the archive isn't working on the first node. I cannot even enable new mailboxes on the 81. When I stop/start/restart the task for the 81 it takes more that 2 minutes to respond.

I checked the rights of the rights of the EV-account, which seems to be in order, there are no names changed on the 81. Both Exchange instances have their own mailbox, which is almost identical.

This could be a problem, (article 278530), I asked our DBA specialist to assist me, but he couldn't find the tables as mentioned in the article. We have version 7.5 SP2

I'm also not able to run the task in Report mode.

Message Edited by Paultje on 02-10-2009 06:09 AM

[TonySterling]

Have you tried creating a new system mbx on the 81 node?

[Paultje]

I removed the mailbox and made a new 1, but there's no change, used a different mailbox name. Any other suggestion?

http://www.senternovem.nl/english/

Message Edited by Paultje on 02-11-2009 01:55 AM

[GertjanA]

Hello Paultje,

Can you open the systemmailbox on the non-working server using Outlook?

If yes, are the accounts on this server in the provisioning task?

Did the provisioning task run without problems? (c:\program files\enterprise vault\reports has report)

Did you add the exchangeserver in EV?

Did you sync the mailboxes?

Gertjan

[Paultje]

Hoi GertjanA,

Thanks for the reply, I still have no clue what's going on. My respond to your advices:

Can you open the systemmailbox on the non-working server using Outlook?

With the admin-account of EV I can open all systemmailboxes (for EV on each Exchange Server) 

If yes, are the accounts on this server in the provisioning task?

The accounts which I want to enable are in the provisioning task

Did the provisioning task run without problems? (c:\program files\enterprise vault\reports has report)

In the report I see 10 skipped system mailboxes.

Did you add the exchangeserver in EV?

This exchangeserver was from the beginning added to EV, but we added the second instance of this exchange cluster and from that moment this problem seems te be started. Just found out when i wanted to add new mailboxes.

Did you sync the mailboxes?

Yes twice every day the mailboxes are synced.

[GertjanA]

hmm. Does the Vault Service Account has the correct rights to the 2nd instance?

Make sure it is not in the Domain Admin group, and make sure it has the appropriate rights.

Nothing else pops to mind.

Groet,

Gertjan

[Paultje]

When I try to enable a mailbox on 81, I will get the next message after a while:

An error occured enabling the mailbox "name".

Error: Timed out whilst waiting for the mapi profile mutex [0xc00408da]

I checked the rights, but it seems to be as it should be.

Any1 with other ideas/suggestions?

Paul

[Chris_Harrison]

Hi Paultje,

Some quick suggestions:

1. Run Deployment scanner against the exchange instance that is not working, to doublecheck all permissions are ok.

2. Create a new (EV) system mailbox on the Exchange instance and update the archiving task's system mailbox entry (through the VAC) to ensure the new mailbox is being used. Make sure the VSA has the appropriate rights to log onto the mailbox you've just created.

3.  Make sure that in the ArchivingRetrievaTask table (Directory database)the entry for the Exchange instance in the SystemMailbox column is correct.

4. Setup a dtrace of Archivetask and then try a report mode run of the task. What errors do you get?

[Paultje · Accepted solution]

Hi Chris,

The deployment scanner gave no problems, everything was OK. After this I created for the third time a new system mailbox, changed the archiving task to the new bax (again) and synchronized that task.

I did this just 30 minutes ago and I already can enable new mailboxes and run the report mode for this Exchange instance. FINALLY, it works, also the others are still working, enabling mailboxes and run reports.

Let's hope this weekend the archiving task will run without problems.