cancel
Showing results for 
Search instead for 
Did you mean: 

Added a second exchange server to the EV vault (user mailboxes and new journal mailbox). Now original exchange server is not archiving any more, but new one is ??

Matthew_Bennett
Level 4

Added a second exchange server to the EV vault (user mailboxes and new journal mailbox). Now original exchange server is not archiving any more, but new one is ??

Any one any ideas about this one. I have a call logged with Symantec support, which they are having to refer to next level of support, whihc was 2 days agao and I have not heard any thing since. This is getting critical due to our journal mailbox on the orginal server is over flowing and the space availbel is running out quick.

Windows 2003 , exchnage 2003 (both servers)  each email server cannot see the other due to the routing groups , hencing a journal mailbox on each server.

Help anyone ?

Matthew.
1 ACCEPTED SOLUTION

Accepted Solutions

TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
Also did you create brand new system mailbox for the new task on the new exchange server?

View solution in original post

7 REPLIES 7

MichelZ
Level 6
Partner Accredited Certified
This is weird.

The only thing I can think of right now is that you have "changed" the Archiving Task to the new Server, instead of creating a new one.

You should have 2 Archiving Tasks & 2 Journaling Tasks.
Is this correct?

Anything logged in the Eventlog?
Can you dtrace the server?
DTrace "Mailbox archiving issues (Exchange)" and "Mailbox provisioning issues (Exchange)"

Cheers
Michel

cloudficient - EV Migration, creators of EVComplete.

RahulG
Level 6
Employee
You should have a new mailbox archiving task as well as new journal archinving task .
you cannot use the same task for two servers . In case if you are using one task you might get this issue

Matthew_Bennett
Level 4
Yes there are 2 archiving task for each exchange server. and there is still the 1 exchnage provisioning task.

The orginal exchange servers private queue A1 has over 7000 items waiting in it and the its journal queues have no activity.
The server EV server and exchnage servers have been rebooted. tried re-syncing the journal task, which did not seem to work.
re-entered the VS account password in the directory properties.

in the event viewer there only seems info regarding the new exchnage server.
the orginals exchnage server journal task and target server has been re-created from scratch, but its has not solved it.

its like the EV has stopped aknowledging the orginal exchnage server.

Matthew.

Matthew_Bennett
Level 4


I have just found 2 event errors the night the problems happened



EVENT ID 2246   23:28.57
An error occurred opening the Journal mailbox /O=MDC/OU=MDCMAIL/CN=RECIPIENTS/CN=JOURNAL04. The Journal Task will shut down.

Task: Journal Task for EMAIL04

Error code: MAPI_E_FAILONEPROVIDER [0x8004011d]

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp

 

EVENT ID 2276  23:28:57

The dispenser will shut down due to an unrecoverable error.

Task: Journal Task for EMAIL04

For more information, see Help and Support Center at http://evevent.symantec.com/rosetta/showevent.asp

PJuster
Level 5
Employee Accredited

0x8004011d googled = http://support.microsoft.com/kb/289971

Are all system mailboxes or journal mailboxes not hidden from the GAL ?

Are the system mailboxes referenced by there SMTP address, incase of system mailboxes of similar names.

Have you run a dtrace of journaling or mailbox archiving issues while the error happens ? EV 7.o and above this can be done via the gui.

http://seer.entsupport.symantec.com/docs/276120.htm

HTH


TonySterling
Moderator
Moderator
Partner    VIP    Accredited Certified
Also did you create brand new system mailbox for the new task on the new exchange server?

Matthew_Bennett
Level 4
Problem has been sorted with help from Symantec Support.
recreated the user AD/exchnage connection account and assigned ito to the tasks for our original exchange server.
This fixed the problem.

Thanks got the advice.