Article ID: 822176 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
The purpose of this article is to provide steps to help you to troubleshoot issues with Exchange 2003 Always-up-to-date Notifications. This article lists the following steps:
Always-up-to-date Notifications is a new feature in Exchange 2003 that permits an always up-to-date user experience with Pocket PC. This feature is only available on devices that have Microsoft Windows Mobile 2003 operating system. By default, Always-up-to-date Notifications are installed with Exchange 2003. When an event is generated in a user’s Exchange account, a notification is sent to the user’s device. The device performs synchronization in the background so that the most current information is available when the user next checks the device.
When a message arrives in the user’s mailbox, there is an event registration item in this folder (referred to as a binding) that is registered with the Exchange OLE Database Provider (ExOLEDB) and the Exchange Store Event .dll file (OmaSink.dll). The binding will trigger an event with the store event sink (OmaSink). The store event sink creates a new message in the Simple Mail Transfer Protocol (SMTP) Pickup directory. The message is then processed by the Outlook Mobile Access Categorizer. The Outlook Mobile Access Categorizer modifies the message body and adds the user’s device address as the recipient. Exchange 2003 can then send the SMTP message to the appropriate carrier by using the standard routing mechanism. The carrier creates and sends a Short Messaging Service message to the device.
Use the following procedures to troubleshoot Always-up-to-date Notifications that are not working correctly.
Increase Logging to Maximum for MSExchangeActiveSyncNotify
Turn On Message Tracking for This Server
View the Event Log to Verify That the Message Was Processed
back to top
Verify That the Message Was Processed by the Outlook Mobile Access Categorizer
back to top
Verify That the Message Left the Corporate Messaging Organization or the Exchange 2003 Messaging Organization
back to top
Article ID: 822176 - Last Review: January 17, 2015 - Revision: 3.4