Troubleshoot Exchange 2003 Always-Up-To-Date Notification (822176)

MORE INFORMATION

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

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand the Servers tree.
3. Right-click the server that contains the user's mailbox, and then click Properties.
4. Click the Diagnostics Logging tab.
5. Click MSExchangeActiveSyncNotify.
6. Drag OMA Push Cat and OMA Event Sink to Maximum.

back to top

Turn On Message Tracking for This Server

1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand the Servers tree.
3. Right-click the server where you want to enable message tracking, and then click Properties.
4. Click the General tab.
5. Click to select the Enable Message Tracking check box.
   
   This option logs information about the sender, about the time the message was sent or was received, about the message size and priority, and about the message recipients.
6. Click to select the Enable Subject Logging and Display check box.
   
   This option logs the subject of any message that is sent to, from, or through the server.
7. Send a message to the user to start logging information.

back to top

View the Event Log to Verify That the Message Was Processed

1. Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.
2. Open the Application log.
3. On the View menu, click Filter.
4. Click the Filter tab, and then type 11324 in the Event ID field.

This event indicates that the message was successfully processed by the Outlook Mobile Access Event Sink and that the message was placed in the SMTP Pickup directory.

back to top

Verify That the Message Was Processed by the Outlook Mobile Access Categorizer

1. Click Start, point to Programs, point to Administrative Tools, and then click Event Viewer.
2. Click to select the Application log.
3. On the View menu, click Filter.
4. Click the Filter tab, and then type 10310 in the Event ID field.

This event indicates that the message was processed by the Outlook Mobile Access Categorizer. Event 10310 provides the user's device address, the user's alias, and the MessageID.

back to top

Verify That the Message Left the Corporate Messaging Organization or the Exchange 2003 Messaging Organization

1. Note the MessageID from the Event 10310.
2. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
3. Expand the Tools container.
4. Double-click Message Tracker.
5. Type the MessageID with @OMA added to search for the message.
   
   For example, if the message ID that you obtained from event 10310 is 01C133474E27D04FABA48D02078CF41D01137B3B, type the following: 01C133474E27D04FABA48D02078CF41D01137B3B@OMA

back to top