Welcome to Part 14 of the 20 part series looking at the BES logs (Part 13) ... the BlackBerry Phone / SMS / PIN logs.

If you're still running BES 4.0.x or older you've got no idea about these ... you need to look at upgrading anyway!

The PhoneCall/PIN/SMS logs (named below) are all a function of the BlackBerry Synchronization Service.

• PhoneCallLog_20090601.CSV
• PINLog_20090601.CSV
• SMSLog_20090601.CSV

By default logging for phone calls are enabled, however PIN...

Welcome to Part 13 of the 20 part series looking at the BES logs (Part 12) ... the BlackBerry Synchronization Service (SYNC) log.

The SYNC log isn't much more useful on its own than the DISP log ... At least the majority of the log is in plain writing ... nonetheless I rarely bother opening it up.

The most value from the SYNC comes from using one of the BlackBerry Resource Kit (BRK) Tools, as the BRK will provide you with usable output

I honestly can't...

Welcome to Part 12 of the 20 part series looking at the BES logs. (Part 11).

This will be the only time I provide you with an entire log file within a post ... because this one is just so clean.

The BlackBerry Router Service logs to the ROUT log, and under normal circumstances it should be the smallest of all of your logs that the BES generates.

Before I provide a clean log with nothing special in it, I'll provide some snips from a log with problems....

Continuing on the discussion of the POLC log started yesterday ... Welcome to part 11 of this 20 part series looking at the BES logs.

As promised, here is the other major part of the POLC log ... Software Deployment / Application Push. Keep in mind, that as a part of a Software Configuration is the Application Control Policy (APC). The APC (Yes, APC and not ACP) sets permissions on a given application that is deployed and either provides or revokes that application the ability to...

Welcome to Part 10 of the 20 part series looking at the BES logs. (Part 9).

My favorite log to tail is the BlackBerry Policy Service (POLC) log. To tail the log, use tail.exe from the Windows Server 2003 Resource Kit.

The POLC log is the place to go for looking at anything related to IT Policy, Application Control Policy and Software Configuration (Deployment).

Here's what you'll see when pushing an IT Policy:

[40000] (07/01 12:11:57.484):{0x166C}...