07-04-2008 01:09 AM
Hi all,
We recently setup a new exchange server along side our old one. I then setup a new archive task on our EV server to start looking at this new server. Also created the registry key "SynchInMigrationMode" on the EV server so that it was able to start vaulting these mailbox's that have been migrated.
Now however, we have switched the old server off, and vaulting has stopped working on the new server. The messages are going into the EV queue on our EV server but just keeps rising. I have tried restarting all tasks but still no joy.
We are able to open from the vault.
Any help would be appreciated.
Thanks
Ben
Solved! Go to Solution.
07-04-2008 03:40 AM
Yeah we had these:
Event Type: Error
Event Source: Enterprise Vault
Event Category: Archive Task
Event ID: 3310
Date: 04/07/2008
Time: 09:20:21
User: N/A
Computer: EVSERVER
Description:
There was a problem accessing a network service or resource. The dispenser will re-queue the current item and sleep for 10 minute(s).
Task: Mailbox Archiving Task for EXCHANGESERVER
For more information, see Help and Support Center at http://evevent.veritas.com/rosetta/showevent.asp
We have now resolved this problem. We removed all tasks relating to the old exchange server, and removed the old exchange server as the target.
Deleted the task for the new server and deleted all the queues.
Recreated the task for the new server and its now running.
Thanks for looking :)
Ben
07-04-2008 02:06 AM
Ben
Are there any Eventlog entries?
Have you removed the Tasks for the old Server?
Cheers
Michel
07-04-2008 03:40 AM
Yeah we had these:
Event Type: Error
Event Source: Enterprise Vault
Event Category: Archive Task
Event ID: 3310
Date: 04/07/2008
Time: 09:20:21
User: N/A
Computer: EVSERVER
Description:
There was a problem accessing a network service or resource. The dispenser will re-queue the current item and sleep for 10 minute(s).
Task: Mailbox Archiving Task for EXCHANGESERVER
For more information, see Help and Support Center at http://evevent.veritas.com/rosetta/showevent.asp
We have now resolved this problem. We removed all tasks relating to the old exchange server, and removed the old exchange server as the target.
Deleted the task for the new server and deleted all the queues.
Recreated the task for the new server and its now running.
Thanks for looking :)
Ben
07-04-2008 04:30 AM
Thanks for posting the Solution! :)
Could you mark the thread as answered?
/Michel
07-04-2008 11:52 AM
Hi,
Just for the record that's a bit of a drastic approach to take. There are many reasons why you may get this error, so I certainly don't recommend everyone taking this solution everytime they see this error.