cancel
Showing results for 
Search instead for 
Did you mean: 

Troubleshooting 3310 Errors

Maverik
Level 6

The Event ID 3310 is very generic and has many different causes reasons for occurring. this can make it extremerly difficult to troubleshoot however having spent some time on it I thought I would put together my steps.

Firstly the error looks like this in the EV event log.

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).

Firstly this technote may help.

http://support.veritas.com/docs/284814

Secondly, here is a high level overview of possible causes.

1: Poor network performance.

2: Load on Exchange/Enterprise Vault servers.

3: Active Directory issues, particularly surrounding Global Catalogue and lookup issues.

4: MAPI issues

and probably more ;)

So how seriously should you take this event.  It really depends on how often it occurs, the impact and how concerned you are by it.  As the Event indicates it cannot process anything at the moment so it will pause for X. If this continually occurs then it can be quite serious as all your processing threads can be pasued and then will not be archiving anything. If happens once a year dont worry too much.

First thing to do would be to capture in a dtrace and see what occurs on that processing thread, prior to the 3310.  Is there a MAPI error for example? There is also a link to confguring a trigger dtrace, so if the event only occurs at 2300, set up a trigger as per the technote.  Usually the 3310 error will occur for the Archiving Task, but I have seen this for the Retreival Task.

http://support.veritas.com/docs/276120         

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

A wireshark trace can be useful. Can you filter by MAPI and see for example a request but no reply from the EV Server IP address and the Exchange Server?

If you are archiving multiple Exchange servers does this only occur against one or them all? Could be resources?

Is there any pattern in the timing of the events? For example does this occur when arhciign and backing up Exchange Server? Back to resources here ;)

Alll of the above are questions you need to answer to try and get to the bottom of this issue.  The dtrace is the best place to start followed by the other questions.

When in doubt log a case with support, they are there to help. ;)