Article ID: 319711 - Last Review: August 18, 2005 - Revision: 5.3 Calendar, Contacts, or Tasks folders show one or more unresolved items after synchronizationThis article was previously published under Q319711 On This PageSYMPTOMS After you synchronize data to your Pocket PC 2002 or later
device by using ActiveSync 3.5 or later, the Calendar folder, the Contacts
folder, or the Tasks folder may report that there is one or more unresolved
items. Even though ActiveSync may display an "Attention Required" message for
that particular object type, additional items of that group are synchronized
successfully. CAUSE This behavior may be caused by a damaged item in the
related object store on the Pocket PC 2002-based device. RESOLUTION If you are using ActiveSync 3.5 and later, you can use
either the Wcesmgr.log file or the Outstore.log file to troubleshoot this
behavior. Both log files are stored in the system Temp folder. Use the Search
functionality to locate these log files, and use Notepad to open the files and
to view the contents. You can use the Wcesmgr.log file to get information about the Synchronization Service Provider(SSP)-type that is not synchronizing, and you can use the Outstore.log file, in conjunction with Wcesmgr.log, to determine the item that is causing the synchronization error. Use information from both log files to determine the corrupted item that is not synchronizing. After you find the item, create a copy of that item (it may be either an appointment, a contact, or a task), and then delete the copy of the item that is corrupted. See the "More Information" section in this article for more information about how to use Wcesmgr.log and Outstore.log to determine the individual items that are not synchronizing. MORE INFORMATIONHow to Troubleshoot Using Outstore.log and Wcesmgr.logWhen an error with an SSP that uses the Pocket Outlook Object Model (POOM) occurs, data similar to the following text is logged in Wcesmgr.log:
2001-09-25 11:25:22 000003B0 - One Contact item [Vol: 0, Oid: 0x0500185E] flagged, SyncType: REMOTE_CHG NOTE: This data is an example of the data that is logged if a contact
is not synchronized.2001-09-25 11:25:22 000003B0 - ERROR returned in function CReplEntry::ProcessPacketData. hr: 0x80070057 2001-09-25 11:25:22 000003B0 - ERROR: failed to write an Contact object [0, 0x2000E71]. Code: 0x80070057 2001-09-25 11:25:22 000003B0 - WARNING: Processing NACK: FromDevice: 0, [SSPId: 0x10003, Oid: 0x02000E71, Hr: 0x80070057, Flags: 0x00000000] Note the following information:
- Time/Date Stamp [2001-09-25 11:25:22] Look for a corresponding entry in the Outstore.log file, for
example: - Process ID [000003B0]
2001-09-25 11:25:22 000003B0 - Error on contact: The following contact cannot be synchronized with Microsoft Outlook on your desktop computer. Ensure Outlook is running. If Outlook is running, try restarting your desktop computer. If the problem persists, contact your network administrator. Jeff Smith (555) 555-1234
NOTE: Microsoft recommends that you use Notepad with the WordWrap
functionality turned on to view the Outstore.log file. This entry from Outstore.log matches the information in Wcesmgr.log (Time/Date Stamp data and Process ID data) and provides the information from the contact that is not synchronizing. In this example, the contact "Jeff Smith, (555) 555-1234" is not synchronizing. To resolve this issue, re-create the Jeff Smith contact, and then delete the corrupted Jeff Smith contact. How to Locate Outstore.log and Wcesmgr.logTo locate either the Outstore.log file or the Wcesmgr.log file, complete one of the following procedures.Microsoft Windows 98, Microsoft Windows 98 Second Edition, and Microsoft Windows Millennium Edition (Me)
Microsoft Windows 2000 and Microsoft Windows XP
| Article Translations
|

Back to the top
