04-08-2011 10:34 PM
Hello,
Just recently I am getting a pile of EventID 2850's on one of the EV servers. I have looked up this issue, there was a Hotfix for EV8 SP3, and this was supposed to be resolved with SP4
http://www.ev-assist.com/uploads/news/files/Enterprise_Vault_8_0_SP4.htm
We are running EV8 SP5, and that should have addressed this issue:
Whilst post processing a message an error occurred in CArchivingAgent::PostProcessArchivedItem() whilst calling CExchangeShortcutAccessor::BuildFromSessionAndLocation().
Error returned from BuildFromSessionAndLocation(): 0x80004005
Any ideas at this point?
Solved! Go to Solution.
04-11-2011 03:27 PM
After a failover and reboot of the offending node, the Saveset errors have disappeared (cleared). In turn the EventID 2850's have also stopped happening.
04-08-2011 10:45 PM
you could try setting the pending shortcut timeout to 0.
in the Mailbox policy, advanced tab, pending shortcut timeout. set it to 0, apply policy (run provisioning, sync mailboxes) then run task in report mode.
04-08-2011 10:52 PM
Why would this all of a sudden start happening though? Also, on the same server I am getting SaveSet errors stating there are over 1 million savesets that haven't been backed up. We are using a Centera on the backend, and replication seems to be fine with the Centera.
04-08-2011 11:05 PM
is your vault store set to remove safety copies after backup or immediate after archive?
are you backing up EV or does your centera replication act as your backup?
if your backup method doesnt set the archive bit then you need to use a trigger file. you can check what your vault store is set to use by going to it's properties then backup tab.
04-09-2011 08:57 AM
Centera replication acts as our backup mechanism.
Safety copies are removed after backup, and in our case replication..
04-09-2011 09:06 AM
you have SaveSet errors stating there are over 1 million savesets that haven't been backed up and you use centera replication. sounds like you need to be using the trigger file. have you checked that yet?
04-11-2011 03:27 PM
After a failover and reboot of the offending node, the Saveset errors have disappeared (cleared). In turn the EventID 2850's have also stopped happening.