07-22-2009, 04:23 PM
|
 |
Proprietor
|
|
Join Date: Nov 2008
Posts: 2,238
|
|
KB17896 - Increased log size seen in the messaging agent logs caused by invalid ...
KB17896 - Increased log size seen in the messaging agent logs caused by invalid log entry
Environment
- BlackBerry® Enterprise Server version 4.1 SP5 - 4.1 SP6 MR4
- SDR186469
Overview
After upgrading to BlackBerry Enterprise Server version 4.1.5 or 4.1.6, the messaging agent logs may increase in size and generate a large amount of Invalid log entry log lines. This is because the logging for these events was placed at a lower level and not at level 15 as expected.
Example log lines:
[50000] (MM/DD HH:MM:SS.MS):Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- compared to date %s, User: , ArgCount:3, Args:arg[1](char*)=TestUser1@domain.com arg[2](char*)=SimilarExclDates arg[3](char*)=
[50000] (MM/DD HH:MM:SS.MS): Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s-Add Date:%s to parent Ox%x, User: , ArgCount:3, Args:arg[1](char*)=TestUser2@domain.com arg[2](char*)=MAPIRecurrenceBlobtoRIMEvent arg[3](char*)=
[50000] (MM/DD HH:MM:SS.MS):{0x1C24} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- Compare Exception Date:%s Ox%x No %d with appt start date:%s, User: , ArgCount:3, Args:arg[1](char*)=user@domain.com arg[2](char*)=SpecifyExceptionsToSend arg[3](char*)=
[50000] (MM/DD HH:MM:SS.MS):{0x1C24} Invalid log entry - Level:15, EventId:0(0x00000000), Format:{%s}-%s- Compare Exclusion Date:%s Ox%x No %d with appt start date:%s, User: , ArgCount:3, Args:arg[1](char*)=user@domain.com arg[2](char*)=SpecifyExceptionsToSend arg[3](char*)=
Cause
The log lines are generated because of a corrupted calendar appointment. During the processing of the BlackBerry smartphone user's calendar the agent reads each calendar appointment and reports these log lines if a calendar contains invalid or corrupted data that the BlackBerry Enterprise Server is unable to process correctly.
Resolution
To resolve the issue the corrupted calendar appointment would need to be deleted and recreated. To determine what calendar appointment is corrupted follow these steps.
- Backup the BlackBerry smartphone user's calendar mentioned in the log line.
- Disable wireless calendar synchronization.
- Attempt to move all calendar appointments to a calendar sub-folder. If the appointment is corrupted enough it will not move successfully.
If specific Messaging Application Programming Interface (MAPI) attributes are corrupted it may require additional testing of the appointments to determine which one causes the issue. In this case restoring the .pst file to a test activated user would allow you to delete or move only partial appointments in attempt to find the one which is corrupt. Older reoccurring appointments are the most likely to cause this issue.
Additional Information
Level 1 and level 5 messages are always logged regardless of the log level setting.
__________________
http://blog.port3101.org/hdawg/
The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.
|
Linear Mode
