[millardus]

Hi all

I've noticed in the past 10 weeks that my Primary BES server has experienced "Agent" problems on 4 seperate occasions. Because of the failover manager (FOM) we have been protected on 3 occasions, but on 1 occasion the Failover was set to manual, and on this occasion we had an outage (longer than it should have been due to poor Alert monitoring on our part).

Can anyone lend some insight into the parts of the BES logging (or pother areas) which would help to diagnose what may have caused the BES Agents to fail, and then prevented them from starting again? If this is a minefield of possibilities then apologies for the open question, but if there are obvious culprits I'd appreciate greatly if you could suggest what they may be. we had such an event yesterday so logs are fresh and available for my inspection.

Tom

[millardus]

Managed to siphen through the Magt logs, and there are numerous "dump" events being recorded yesterday (in all 5 Agent logs). I can see that on Monday, there were 3 restarts of the BES Agents, and they were, in turn, successful. However, yesterday, after 10 attempts, the Agents failed to initialise. Is it possible that an invididual user can impact an entire BES environment because of data they have or an action they are performing?

There are also error events referring to the CDO, which I believe is a Calendering "object".

Any clues?

[cyclmpc]

Agent issues that I experienced were directly tied to MAPI/CDO issues. You should check your specs for your environment to see that you are up to date across the board.

If you feel a specific user needs to be monitored, you can assign that user a static agent to monitor them.

[millardus]

Cheers cyclmps,

That is in fact exactly what the support team from my reseller suggested, an which my team have implemented.
Good to see it may well be the root of the issue (Our MAPI\CDO version was Nov 2009).

[cyclmpc]

Great news. GL, moving foward.