BES Logs ... What's in them? Part 9 of 20 (MNGR log)
Posted 07-02-2009 at 05:00 AM by hdawg
Tags bb manager, bes log, bes manager, blackberry console, blackberry logs, blackberry mgr, blackberry mngr log, blackberry server logs, mdat log
Welcome to Part 9 of the 20 part series looking at the BES logs. (Part 8).
The BlackBerry Manager (MNGR) is another one of the few logs that I think never really gets looked through ... honestly, I think it is because some days an MNGR log files doesn't even exist!
... and the days it does exist, there usually isn't much in there to be concerned with ... see below:
[30000] (06/01 09:40:12.609):{0x1268} [ENV] Current Process logged on as: DOMAIN\besadmin, Start Time: Jun 08 2009 09:40:12, Uptime (seconds): 0
...<snip>SNIP...</snip>
[30000] (06/01 09:40:12.687):{0xD28} BlackBerry Manager Version 4.1.6.20 starting...
[30000] (06/01 09:40:12.828):{0xD28} Mailstore Connector initialized.
[30000] (06/01 09:40:13.297):{0xD28} [ENV] [DB] Connection String = Server=SQL01;Database=BESMgmt;Trusted_Connection=Yes
[30000] (06/01 09:40:13.297):{0xD28} [ENV] [DB] DBMS Name = Microsoft SQL Server; DBMS Version = 08.00.0760; Provider Name = sqloledb.dll; Provider Friendly Name = Microsoft OLE DB Provider for SQL Server; OLE DB Version = 02.70; Provider Version = 08.10.3959
[35019] (06/01 09:40:13.297):{0xD28} [ENV] [DB] Database Schema Version: 4.1.6 <4.1.2.2008.05.07>
[30000] (06/01 09:40:13.609):{0xD28} Access BBMgrAppResources using rim_db_admin_security
[30000] (06/01 09:40:16.172):{0x151C} [DIAG] EVENT=Register_thread, THREADID=0x151C, THREADNAME="Unnamed"
[30000] (06/01 09:40:16.953):{0xD28} BlackBerry Manager has successfully started
[30000] (06/01 09:40:17.187):{0x5E0} [DIAG] EVENT=Register_thread, THREADID=0x5E0, THREADNAME="Unnamed"
[30000] (06/01 09:40:19.078):{0xBF4} [DIAG] EVENT=Register_thread, THREADID=0xBF4, THREADNAME="Unnamed"
[30000] (06/01 09:40:19.078):{0x1C3C} [DIAG] EVENT=Register_thread, THREADID=0x1C3C, THREADNAME="Unnamed"
[30000] (06/01 09:43:06.596):{0xD28} User id=133 (Test User1) successfully queued for HARD deletion.
[30000] (06/01 09:43:15.612):{0xD28} User id=45 (Test User2) successfully queued for HARD deletion.
Do I even need to explain what this is? ... here I go. So, the BlackBerry Manager was launched connected to Exchange, and SQL using Windows Authentication, with a user priveledge of the role rim_db_admin_security. The user (DOMAIN\besadmin) then successfully deletes Test User1 and Test User2 from the BES ... that's it!
If a day passes and the BlackBerry Manager isn't launched on the BES there will be no MNGR log. The MNGR log serves as a good way to audit activity of what happens on the BES. Nothing to fancy, nothing too complicated ... and generally nothing to useful. The same information retrieved from these logs can be pulled from the BRK tool AdminHistory.exe.
If you've got any questions about other specific entries in the MNGR log feel free to post a question / comment in response to this post, or in the forum.
Tomorrow in Part 10 we venture to a log that I absolutely love. If you've got a question about policy or application deployment, your answer is to be found in this ... the BlackBerry Policy Service (POLC) log.
The BlackBerry Manager (MNGR) is another one of the few logs that I think never really gets looked through ... honestly, I think it is because some days an MNGR log files doesn't even exist!
... and the days it does exist, there usually isn't much in there to be concerned with ... see below:
[30000] (06/01 09:40:12.609):{0x1268} [ENV] Current Process logged on as: DOMAIN\besadmin, Start Time: Jun 08 2009 09:40:12, Uptime (seconds): 0
...<snip>SNIP...</snip>
[30000] (06/01 09:40:12.687):{0xD28} BlackBerry Manager Version 4.1.6.20 starting...
[30000] (06/01 09:40:12.828):{0xD28} Mailstore Connector initialized.
[30000] (06/01 09:40:13.297):{0xD28} [ENV] [DB] Connection String = Server=SQL01;Database=BESMgmt;Trusted_Connection=Yes
[30000] (06/01 09:40:13.297):{0xD28} [ENV] [DB] DBMS Name = Microsoft SQL Server; DBMS Version = 08.00.0760; Provider Name = sqloledb.dll; Provider Friendly Name = Microsoft OLE DB Provider for SQL Server; OLE DB Version = 02.70; Provider Version = 08.10.3959
[35019] (06/01 09:40:13.297):{0xD28} [ENV] [DB] Database Schema Version: 4.1.6 <4.1.2.2008.05.07>
[30000] (06/01 09:40:13.609):{0xD28} Access BBMgrAppResources using rim_db_admin_security
[30000] (06/01 09:40:16.172):{0x151C} [DIAG] EVENT=Register_thread, THREADID=0x151C, THREADNAME="Unnamed"
[30000] (06/01 09:40:16.953):{0xD28} BlackBerry Manager has successfully started
[30000] (06/01 09:40:17.187):{0x5E0} [DIAG] EVENT=Register_thread, THREADID=0x5E0, THREADNAME="Unnamed"
[30000] (06/01 09:40:19.078):{0xBF4} [DIAG] EVENT=Register_thread, THREADID=0xBF4, THREADNAME="Unnamed"
[30000] (06/01 09:40:19.078):{0x1C3C} [DIAG] EVENT=Register_thread, THREADID=0x1C3C, THREADNAME="Unnamed"
[30000] (06/01 09:43:06.596):{0xD28} User id=133 (Test User1) successfully queued for HARD deletion.
[30000] (06/01 09:43:15.612):{0xD28} User id=45 (Test User2) successfully queued for HARD deletion.
Do I even need to explain what this is? ... here I go. So, the BlackBerry Manager was launched connected to Exchange, and SQL using Windows Authentication, with a user priveledge of the role rim_db_admin_security. The user (DOMAIN\besadmin) then successfully deletes Test User1 and Test User2 from the BES ... that's it!
If a day passes and the BlackBerry Manager isn't launched on the BES there will be no MNGR log. The MNGR log serves as a good way to audit activity of what happens on the BES. Nothing to fancy, nothing too complicated ... and generally nothing to useful. The same information retrieved from these logs can be pulled from the BRK tool AdminHistory.exe.
If you've got any questions about other specific entries in the MNGR log feel free to post a question / comment in response to this post, or in the forum.
Tomorrow in Part 10 we venture to a log that I absolutely love. If you've got a question about policy or application deployment, your answer is to be found in this ... the BlackBerry Policy Service (POLC) log.
Total Comments 0
