Welcome to Part 4 of at least a 20 part series looking at the BES logs. (Part 3)

In this post we'll look at the Management Connector Log (CMNG). This is one of the few logs I almost never go in ... and I'm betting the only reason most of you have gone in it is pure curiosity.

Like the Backup Connector (CBCK) log, it gets data fed from the BlackBerry Synchronization Service. Be prepared to see the same thing for every user in this log ... it's a good thing
...

Welcome to Part 3 of at least a 20 part series looking at the BES logs. (Part 2)

In this post we'll look at the Backup Connector Log (CBCK). As one of the most straightforward logs in BES it is actually easy to read.

The CBCK log is data generated from the Automatic Wireless Backup function of BES. By default this functionality is enabled for all users, and is what allows you to wipe and reactivate a device without losing a whole slew of customizations ... unless you...

Welcome to Part 2 of at least a 20 part series looking at the BES logs. (Part 1)

Each day I'll talk about a specific type of log file and hopefully we'll all learn something.

The ALRT log is fed data through the BlackBerry Alert service. The BlackBerry Alert service also feeds data to the Windows Application log. You'll notice a duplication of data in the ALRT log and Windows Application log.

For those of us that do event log scraping or have triggers...

I really wanted to title this series: BES Logs ... do I really care?

... but if anyone knows me, you know I love the logs and just couldn't say a bad thing about them. Why, you ask? Are you ready for the answer ... The logs don't lie. Users lie ... administrators lie ... but the logs tell us like it is.

Over the next 20 days, each day I'm going to talk about one specific BES Log file along with:

• What function it serves
• What service(s) feed it information
• A

...