Solved! Go to Solution.
Windows Registry Editor Version 5.00 [HKEY_USERS\S-1-5-21-1242909238-215958010-794563710-203157\Software\Microsoft\Exchange\Exchange Provider] "Closest GC"=dword:00000001
3310 Error is a little blighter of an error as it can cover so many different issues and is a very generic error as you can see from the error description. If you are constantly seeing this error every 10 minutes then we need to investigate and what I would need to see is the output of a DTRACE of the archivetask process whilst the error is generated.
Usually 3310 is an indication of a loss of MAPI resource and can be solved sometimes simply by restarting the archiving task but this is not always the case. If a restart does not work then follow the MAPI troubleshooting guide that you can find in the articles section of this website. If after restarting, MAPI troubleshooting you still get the error every 10 minutes then post the DTRACE,
If you only see this error every now and again then you can safely ignore it
OK so if you woud like to futher troubleshoot then I would recommend setting up a dtrace of the archivetask process and putting in a trigger on 3310. There are technotes out there explaining how to do this if you do not already. Then you can post the log data and we will see where we can go from there.
2445406 13:48:22.062  (ArchiveTask) <5880> EV~E Event ID: 3310 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: Exchange Mailbox Archiving Task for SEXCVIVV02 |2445407 13:48:22.062  (ArchiveTask) <7040> EV:M AgentMessageDispenser: 3 of 10 Agent threads is pausing|
We could be getting into the realms of putting on a network sniffer.
Is the exchange server SEXCVIVV02 sat close to the ev server from a network perspective.
We rely on the exchange server as a default referring us to a good gc. WHat you can do is implement a key called closest gc which will change the gc referral to use outlook installed on the ev server. It maybe that you have intermittent GC problems from you exchange server.
As a first stop implement this key on the ev server (just google it for info) and restart your tasks. Monitor for the 3310 error. If you still get it then we can move onto the next step.