W12 Up to Date Notification

Contents

Overview 1

Lesson 1: Managing Mobile Service Components 2

Lesson 2: Always Up-To-Date Notifications 14

Lesson 3: Beneath the GUI 17

Lesson 4: Troubleshooting 34

Review 51

Appendix A 52

Appendix B 56

Appendix C 64

Module 12: Up to Date Notifications

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places and events depicted herein are fictitious, and no association with any real company, organization, product, domain name, e-mail address, logo, person, place or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation. Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property. © 2005 Microsoft Corporation. All rights reserved. Microsoft, MS-DOS, Windows, Windows 2000, Active Directory, ActiveX, BackOffice, FrontPage, Hotmail, Jscript, MSN, NetMeeting, Outlook, PowerPoint, SQL Server, Visual Studio, and Windows Media are either registered trademarks or trademarks of Microsoft Corporation in the United States, and/or other countries. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Module 12: Up to Date Notifications 1

Overview

*****************************illegal for non-trainer use******************************

Microsoft® Exchange Server 2003 includes built-in mobile functionality, which allows users to access Exchange data by using mobile devices. Exchange Server 2003 offers two services for your mobile users: Microsoft® Exchange ActiveSync® and Microsoft® Outlook® Mobile Access.

After completing this module, you will be able to:

Manage mobile service components.

Understand what up-to-date notifications can do.

Know the inner working and how it interacts with other components.

Know how to troubleshoot up-to-date notifications and what tools you can use.

Introduction

Objectives

2 Module 12: Up to Date Notifications

Lesson 1: Managing Mobile Service Components


This lesson introduces you to the mobile service components of Exchange Server 2003. It explains how to administer and secure these mobile service components.

After completing this lesson, you will be able to:

Describe the mobile service components of Exchange Server 2003.

Explain the requirements for Exchange Server 2003 mobile service components.

Explain the utilities that are needed to administer mobile components.

Identify the Mobile Services object properties that you can modify by using Exchange System Manager.

Configure Exchange ActiveSync and up-to-date notifications.

Describe the considerations necessary for securing mobile components.

Introduction

Lesson objectives


What Are the Mobile Service Components of Exchange Server 2003?


Exchange Server 2003 allows users of wireless and small devices, such as mobile phones, personal digital assistants (PDAs), or smart phones (hybrid devices that combine the functionality of mobile phones and PDAs), access to Exchange data. Exchange ActiveSync and Outlook Mobile Access are two of the mobile service components that are built into Exchange Server 2003. These components enable mobile users to browse Exchange information, in addition to synchronizing calendar, contact, and inbox information.

Exchange ActiveSync is a service provided in Exchange Server 2003 that allows users to synchronize their Exchange information (inbox, subfolders, calendar, contacts, and tasks) with their ActiveSync-enabled mobile device (such as Pocket PC 2002, Smartphone 2002 and Microsoft® Windows Mobile™ 2003 devices).

The two types of client initiated remote synchronizations supported by Exchange ActiveSync are:

Manual user driven. Allows users of mobile devices to perform a manual synchronization.

Scheduled. Allows users of mobile devices to schedule synchronization.

In addition, Exchange supports server initiated synchronization though Exchange ActiveSync and up-to-date notifications. Up-to-date notifications allow synchronization of mobile devices to be automated by using an up-to-date notification. This option in the Mobile Services Properties dialog box sends a notification to the mobile device to initiate an automatic synchronization through Exchange ActiveSync.

What Is Exchange ActiveSync?

What are up-to-date notifications?


After a user completes the first successful synchronization from the Pocket PC, the device is automatically populated with the user’s mailbox folder tree, exposing all mailbox folders available for synchronization. Each folder can be selected for an up-to-date notification. After a folder is chosen for an up-to-date notification, an event is set on the folder, which looks for new e-mail to be delivered to the folder. When the new e-mail arrives, an event runs inside the Exchange server mailbox store and creates a Simple Mail Transfer Protocol (SMTP) notification. When the notification on the device is received (devices receive notifications, based on the network type, the notification could be as a Short Message Service–based message), the device will start an Exchange ActiveSync session, enabling the device to become up to date. All this occurs without waking the device.

The up-to-date notification feature is only supported on the Windows Mobile 2003 devices.

Outlook Mobile Access is a service provided in Exchange Server 2003 that allows your users to access their Exchange mailbox by using a browser enabled mobile device. Devices such as mobile phones and PDAs that use Extensible Hypertext Markup Language (XHTML), compact HTML (cHTML), or standard HTML browsers allow your users to connect to their inbox, calendar, contacts, tasks, and perform global address list (GAL) searches. In addition to mobile phones, Windows Mobile devices using Microsoft Pocket Internet Explorer and desktop personal computers using Microsoft® Internet Explorer 6.0 or later also support Outlook Mobile Access.

If your Exchange server has Device Update 2 installed (the default), Internet Explorer 6.0 will work but it will receive the following error message “The device type you are using is not supported. Press OK to continue.”

If you have previously used Microsoft Mobile Information Server 2001 Enterprise Edition or Microsoft Mobile Information Server 2002 Enterprise Edition to provide mobile access to your users, you need to be aware of the following compatibility issues with Exchange Server 2003 mobile components to determine the requirements for co-existence:

Mobile Information Server can communicate with Microsoft® Exchange 5.5 mailbox servers to provide Outlook Mobile Access (real-time browse access) and with Microsoft® Exchange 2000 mailbox servers to provide Exchange ActiveSync and Outlook Mobile Access support for browsing and new e-mail notifications.

Microsoft® Exchange Server 2003 mobile components can only communicate with Exchange Server 2003 mailbox servers to provide Exchange ActiveSync and Outlook Mobile Access.

Mobile Information Server can be installed in an ‘ActiveSync-only’ configuration. When installed in this manner, Mobile Information Server does not require an Active Directory® schema change or any complicated auxiliary forest topologies.

The recommended path for customers that want mobility on Exchange 2000 and want to ensure they will have a good migration path to Exchange 2003 is to install Mobile Information Server in the ‘ActiveSync only’ configuration for Exchange 2000. Then the same devices, PPC Phone and Smartphone, will work with Exchange 2003 when they migrate. Then they do not have to be concerned

How do up-to-date notifications work?

Note

What Is Outlook Mobile Access?

Note

Compatibility with Microsoft Mobile Information Server

Integrating Exchange 2003 with Mobile Information Server 2002


with a complex Active Directory schema change and auxiliary forest scenarios pertinent to Mobile Information Server. Of course, this means they will not get the browse and push features of Mobile Information Server. But past experience shows Exchange ActiveSync is usually the feature driving Mobile Information Server deployments.

In summary:

Mobile Information Server has not been tested against Exchange 2003 mailboxes. Using Mobile Information Server mobile browse or Mobile Information Server ActiveSync against Exchange 2003 mailboxes is not a supported scenario.

Coexistence: Mobile Information Server (browse, push and sync) used against Exchange 2000 mailboxes can co-exist in the same environment as Exchange 2003 Outlook Mobile Access and Exchange ActiveSync used against Exchange 2003 mailboxes. Exchange 2003 does not reuse the Active Directory attributes used by Mobile Information Server, and so they do not conflict. For exact details about what Active Directory attributes are used by Exchange 2003 Mobility, see the documentation that will be available by launch.

If a customer wants to use Mobile Information Server for some users and Exchange 2003 mobility for others, then using separate name spaces for each is best.

Mobile Information Server /Exchange 2000 users URL = mis.corp.com

Exchange 2003 users URL = oma.corp.com

In a mixed Exchange environment where you deploy a front-end and back-end topology, you must use Exchange Server 2003 for both the front-end and back-end servers to gain access to mailboxes through Outlook Mobile Access and Exchange ActiveSync.

For more information on Windows Mobile devices, see the Windows Mobile page on the Microsoft Web site at http://www.microsoft.com/windowsmobile.

Note


Utilities That You Can Use to Administer Mobile Components


You use utilities such as Exchange System Manager, Internet Information Services (IIS) Manager, and Active Directory Users and Computers to configure Exchange mobile components.

Exchange System Manager is used when configuring Mobile Services objects. These objects are a part of the global settings for the Exchange organization. These objects allow you to define how Exchange ActiveSync and Outlook Mobile Access are enabled for all users in your organization. You can also define the domain name for mobile carriers that are used by up-to-date notifications.

Exchange System Manager is also used to configure an SMTP connector that is used for up-to-date notifications. You define the SMTP connector to connect your corporate SMTP bridgehead server to your mobile carrier, such as Microsoft® MSN® Mobile or your mobile operator.

IIS Manager is used to configure settings such as the security of Outlook Mobile Access and the Exchange ActiveSync virtual directories. Configuring Outlook Mobile Access and Exchange ActiveSync is similar to how you configure options for Microsoft Office Outlook Web Access by using the IIS Manager.

Active Directory Users and Computers allows you to control mobile access on a user-by-user basis. By default, Exchange ActiveSync and Outlook Mobile Access are enabled on all user accounts, but Outlook Mobile Access is disabled globally by default for Exchange Server 2003.

Exchange System Manager

IIS Manager

Active Directory Users and Computers


How to Configure Mobile Services Object Properties Using Exchange System Manager


By default, Exchange Server 2003 global settings for Exchange ActiveSync allow all users to initiate synchronization and receive up-to-date notifications. Exchange ActiveSync can be configured on a Global and Per user basis with the on/off switch in Exchange System Manager and Active directory Users and Computers.

By Default up-to-date notifications is enabled for all users but is disabled globally by default through the Mobile Services object settings. Using Exchange System Manager, expand Global Settings, right-click Wireless Services, and then click Properties. Then on the General Tab of the Mobile Services Properties, in the Outlook Mobile Access pane, enable Outlook Mobile Access

To modify your global settings for Exchange ActiveSync and Outlook Mobile Access, use the Mobile Services object in Exchange System Manager.

The following table lists the object properties available for Exchange ActiveSync.

Object property Description Enable user-initiated synchronization

Users can use their mobile carrier connection to synchronize their Exchange information to their Exchange ActiveSync-enabled device and then access this information while offline.

Enable up-to-date notifications

Mobile devices will be able to receive notifications sent to the device that will initiate synchronization between a user’s device and their Exchange mailbox. (Note: Currently only Windows Mobile 2003 devices support the up-to-date notifications.)

Enable notifications to user-specified SMTP

Users can use any mobile carrier with the wireless synchronization feature of Exchange. Enable this feature

To configure Exchange ActiveSync


addresses if you have users who are using mobile devices to synchronize their Exchange information, and you do not want to specify the mobile carrier in Exchange.

The following table lists object properties available to access Exchange through Outlook Mobile Access.

Object property Description Enable Outlook Mobile Access

This feature allows users to use mobile devices such as a Windows Mobile powered device, an iMode device, or any XHTML–compatible mobile phone to access their e-mail, contacts, calendar, and tasks.

Enable unsupported devices

This feature provides mobile access to Exchange Server from devices that are not supported, such as Wireless Application Protocol (WAP) 1.0 mobile phones. These unsupported devices may have unexpected results when using Outlook Mobile Access.

To configure Outlook Mobile Access


How to Configure Exchange ActiveSync and Up-to-Date Notifications


The notifications can be sent from Exchange Server 2003 directly through a carrier/mobile operator to the Systems Management Server (SMS) address of the device, or through a Corporate Carrier Connector/aggregator configured by the Exchange administrator.

In addition to allowing sending to a user’s device, if the Administrator creates carriers in Exchange System Manager, the user can choose the second option. The user will just need to type their phone number and select their carrier from the list. This eases the pain of the user having to remember the full SMTP address of the device.

This option is allowed or disallowed in Exchange System Manager by an Exchange Administrator.

Administrators also have the option to disallow sending directly the user’s device. For example if the enterprise chooses to send via an aggregator or corporate provider such as MSN, administrators may force users to receive notifications through MSN only. If administrators make sending to MSN mandatory, then user must choose the second option for up-to-date notifications to work for them.

Note: Enterprises can choose to send through MSN while still allowing sending directly to the user’s SMTP device address. If the MSN link is down for some reason, they can instruct their users to choose the first option.

There are many benefits when an enterprise chooses to use a Corporate Carrier Connector to send notifications instead of sending the message directly to the SMS address of the device.


When an administrator configures an SMTP carrier to send notifications directly to the SMS address of the device, the notification goes through the SMTP gateway at the mobile operator and then to the operator’s SMS Center (SMS-C). Operator SMTP gateways are often associated with high message latencies and SMS delivery times sometimes are longer.

Mobile carrier objects are created to support up-to-date notifications by either using Exchange System Manager to create an SMTP mobile carrier object or through automated means, such as importing a LDAP Data Interchange Format (LDIF) file from a mobile operator such as MSN Mobile that has an agreement with Microsoft (known as an aggregator). MSN Mobile has mobile operator agreements with other mobile carriers (such as AT&T and T-Mobile). Mobile operator agreements will allow you to have a single point of contact for all your mobile carriers and that will allow you to route all your up-to-date notification traffic through a single carrier.

After the mobile carrier object is created in Active Directory, the list of mobile carriers are exposed on the Windows Mobile 2003 device when up-to-date notifications are configured, thereby allowing users to choose their specific mobile operator and configure up-to-date notifications for their specific device.

To specify the mobile carriers that users use for up-to-date notifications, you will need to create these mobile carriers for your users.

To allow your Exchange organization to route all messages through a single carrier, you must create an MSN Mobile carrier. The steps for creating the MSN Mobile carrier object, if you are using MSN Mobile as a mobile carrier, are as follows:

1. Log on to the MSN Mobile Web site by using a Microsoft Passport account and select the carriers you want to use through MSN Mobile. You will then be able to obtain credentials from MSN for secure notification delivery.

2. Configure Active Directory for using the MSN Mobile carrier by importing the necessary .Ldf file for the carrier updates.

3. Create an SMTP connector from your SMTP bridgehead server to MSN Mobile by using the credentials you received when you signed up.

To allow notifications to be sent directly to the mobile device, you must create an SMTP Mobile carrier. The steps for creating an SMTP Mobile carrier are as follows:

1. In Exchange System Manager, browse to Mobile Services and create a new Mobile Carrier object.

2. Enter the SMTP address for the mobile carrier.

3. Have your users select this mobile carrier from their device by using Exchange ActiveSync.

For additional information about creating an SMTP connector, see Module 9, “Managing Routing,” in Course 2400, Implementing and Managing Microsoft Exchange Server 2003.

The notifications can be sent from Exchange Server 2003 directly to the SMS address of the device, or through a corporate service provider configured by the Exchange administrator.

Why create Mobile carrier objects?

To create an MSN Mobile carrier for up-to-date notifications

To create an SMTP Mobile carrier for up-to-date notifications

Note

Adding Carriers


For notifications to be sent to the SMS address of the device, the Exchange administrator has to create an SMTP carrier in Exchange system manager.

A corporation can also choose an aggregator and send notifications to the devices through the aggregator. Currently MSN Internet Access is the only aggregator.

In order to set this up, the corporation will log in to a Web site using a Passport account and select the carriers they want to use through MSN. They will then be able to obtain credentials from MSN for secure notification delivery.

Next the MSN carrier will have to be created in Active Directory. A separate file, MSNCarrierConfigurator.zip will be provided. The Zip file will contain CreateMSNCarrier.cmd and CarrierConfig.LDF, which can be used to setup the MSN Carrier.

The administrator will then need to setup an SMTP connector for secure notification delivery to MSN using the credentials received when they signed up.

When an administrator configures an SMTP carrier to send notifications directly to the SMS address of the device, the notification goes through the SMTP gateway at the mobile operator and then to the operator’s SMS Center (SMS-C). Operator SMTP gateways are often associated with high message latencies and SMS delivery times sometimes exceed an hour. This negates the advantages of up-to-date notifications and thereby does not provide an up-to-date experience for the user.

There are also security concerns with forwarding messages to an SMTP gateway at the operator.

Choosing an aggregator allows an enterprise to connect via Transport Layer Security (TLS) (secure SMTP) to Microsoft Mobile Services. This enables an enterprise to connect to one or more of the operators Microsoft Mobile has created up-to-date notifications partnerships with. There are a number of associated benefits, some of which are:

QoS: message latency for up-to-date notifications via the aggregator is lower and more consistent by virtue of the fact that MS Mobile Services connects directly to the operator’s SMS-C (i.e. via SMPP 3.4 or another standard SMS protocol) rather than to a public SMTP gateway.

Ease of Management: there is only one connection from the enterprise to Microsoft Mobile Services to maintain and monitor regardless of the number of operators the enterprise users utilize.

Microsoft Mobile service maintains all the individual operator connections/relationships.

Security: the connection to Microsoft Mobile Services is secured via Transport Layer Security (TLS).

Cost Effective: Setting up a connection with Microsoft Mobile Services carries no incremental cost for the enterprise. In actuality, up-to-date notifications will likely be cheaper as a result of Microsoft Mobile Services partnerships with operators; part of which is geared toward making up-to-date notifications cost effective for end users (i.e. since it is a control message, billing is different than standard SMS).

Advantage of using an Aggregator for up-to-date notifications


How to Configure Devices for Synchronization


After a user account is configured to use Exchange ActiveSync, you must configure the mobile device to use Exchange ActiveSync and up-to-date notifications.

The steps for configuring a Windows Mobile 2003 device for Exchange ActiveSync are as follows:

1. On your device, open ActiveSync.

2. On the Server tab, on the Server Synchronization page, do the following:

3. Specify the Exchange 2003 server name.

4. If your Exchange Server 2003 is set to use SSL, select the This server uses secure connections (SSL) check box.

5. On the Server Synchronization Options page, specify a user name, password, and domain name.

6. Select Save your network password or you will be prompted every time a synchronization session with your Exchange Server is initiated.

7. Select the items that you want to synchronize.

8. Configure the synchronization settings for the items that you selected.

9. On the Server Synchronization Options page, configure the Device Address.

The Device Address button will appear only after a successful synchronization attempt has completed with an Exchange 2003 server.

To configure a Windows Mobile 2003 device for Exchange ActiveSync

Note


To use up-to-date notifications, you must have a Windows Mobile 2003 device with the Windows Mobile 2003 operating system. Additionally, the up-to-date feature for Exchange ActiveSync must appear on the device after the first successful synchronization with the Exchange 2003 server.

The steps for configuring a Windows Mobile 2003 device for up-to-date notifications are as follows:

On your device, open ActiveSync.

On the Mobile Schedule tab, on the Mobile Schedule page, under both the During peak times, sync and During off-peak times drop-down menus, select When new items arrive.

Synchronize your device with your Exchange 2003 server to save these settings.

For more information about configuring mobile devices for Exchange ActiveSync and up-to-date notifications, see the white paper What’s New in Exchange Server 2003, located on the Exchange Server 2003 Technical Library page of the Microsoft Web site at http://www.microsoft.com/exchange/library.

The following picture shows a screen shot of the interface where a user will specify how they want to receive notifications. If sending notifications to a user’s device address is allowed by the Exchange Administrator, users can choose the first option. The user will need to know their device SMTP address ([email protected])

To configure a Windows Mobile 2003 device for up-to-date notification

Note

Deciding how Notifications will be sent


Lesson 2: Always Up-To-Date Notifications


This lesson explains provides a general overview of up-to-date notifications and some known issues.

After completing this lesson, you will be able to:

Have a basic understanding of how up-to-date notifications works and be familiar with known issues.

Introduction

Lesson objectives


General Overview


Exchange ActiveSync can be configured on the device to sync with the server at intervals, syncing as frequently as every five minutes. This, however, does not provide up-to-date information on the device. The user can also possibly incur additional charges due to the frequent sync sessions.

Up-to-date notification is a new feature in Exchange Server 2003 that provides the user with the ability to automatically synchronize the mobile device with the server as new items are received on the server. Up-to-date notifications requires Pocket PC 2003 or a SmartPhone. Up-to-date notifications is a feature of Exchange ActiveSync that is installed with every Exchange 2003 server.

An event is generated in a user’s Exchange account when any of the selected options are updated. This event results in a Short Message Service notification being sent to the user’s device. The device synchronizes in the background. The user data is updated to the most current information with no intervention on their part.

The notification is sent as a Short Message Service control message to the device. It is different from a regular Short Message Service in that it does not appear as a Short Message Service message in the inbox. The Short Message Service router and Exchange ActiveSync on the device process the notification. The notification itself does not carry any sensitive data.

For a step-by-step walkthrough of Pocket PC Configuration see Module 12 Appendix A.

Overview


Known Issues


As with all of the Mobility Components, the known issues revolve around installing Microsoft® SharePoint™ Portal Services and Forms Based Authentication/Secure Sockets Layer (SSL). These are covered below:

As with other Exchange 2003 components, SharePoint Portal Services also stops Exchange ActiveSync from working. This Knowledge Base (KB) article will help:

823265 "Page Not Found" Error Message When You Browse Exchange Server 2003

Note: If you have SSL and Forms Based Authentication or are using the ExchangeVdir you need to exclude these from the SharePoint Portal Services managed paths, too.

Again like SharePoint Portal Services, this breaks Exchange Active Sync. This KB article will help:

817379 Cannot Access Exchange Server 2003 by Using Outlook Mobile Access When the Exchange Virtual Directory Requires SSL or Uses Forms-Based Authentication

OR

822177 "Unable to Connect to Your Mailbox on Server <ServerName>" Error Message and an Event ID 1805 Message Occur When You Try to Access Outlook Mobile Access

There is a Known issue with Internet Security Acceleration (ISA) server that may prevent device provisioning. This KB article will help: 304340 The ISA Server Response to Client Options Requests Is Limited to a Predefined Set.

SharePoint Portal Services

SSL and Forms Based Authentication

ISA


Lesson 3: Beneath the GUI


This lesson explains what happens under graphical user interface (GUI), and covers a number of subjects in-depth. These include:

Device Provisioning

Device Info XML / Notify Guids

Up-To-Date Notifications Message Flow Overview

Outlook Mobile Access SINK

Batching of Notifications

Some of the topics may not be covered by the instructor, but are there for your reference.

Introduction


Beneath the GUI: Device Provisioning


When a user with a device running Windows Mobile 2003 synchronizes for the first time with a server that supports up-to-date notifications (Exchange Server 2003), there is a bubble (prompt) on the device to set up up-to-date notifications. The client sends the OPTIONS command during the sync and if the response contains the NOTIFY command, a bubble is shown. If the user is disabled for push notifications, NOTIFY is not included in the response and therefore the bubble does not come up. If the device is cradled, the bubble is not triggered until the device is disconnected from the desktop.

If you choose No on the up-to-date notifications prompt, you can setup up-to-date notifications at a later stage by configuring the Schedule to “When new items arrive” and specifying the Device Address.

Note: If the user never sees the “blob” or “popup” above, it is most likely that the OPTIONS verb may be blocked by a firewall. Some Mobile Operators do not allow the OPTIONS verb without SSL. The device log will show whether or not there was a successful OPTIONS response from the server.

A successful response looks like this:


=-=-=-= Client Request =-=-=-= OPTIONS Microsoft-Server-ActiveSync?User=johndoe &DeviceId=11235408531900011403513&DeviceType=PocketPC Accept-Language: en-us MS-ASProtocolVersion: 2.0 -=-=-=- Start of Body -=-=-=- =-=-=-= Server Response =-=-=- HTTP/1.1 200 OK Date: Fri, 18 Apr 2003 00:37:24 GMT Server: Microsoft-IIS/6.0 Pragma: no-cache Content-Length: 0 Public: OPTIONS, POST Allow: OPTIONS, POST MS-Server-ActiveSync: 2.0.xxxx.0 MS-ASProtocolVersions: 1.0,2.0 MS-ASProtocolCommands: Sync,SendMail,SmartForward,SmartReply,GetAttachment,GetHierarchy,CreateCollection,DeleteCollection,MoveCollection,FolderSync,FolderCreate,FolderDelete,FolderUpdate,MoveItems,GetItemEstimate,MeetingResponse,Notify

When a user provisions the device, store event bindings are created in the mailbox on the folders that the user has specified for up-to-date notifications. Bindings can be created in all email folders, calendar and contacts. When the user provisions the device for the first time only Inbox, Calendar, and Contacts folders can be set up for up-to-date notifications. After the first sync, they will get their folder hierarchy, after which any mail folder can be selected for up-to-date notifications. When a binding is created, a WirelessOnSave hidden message is saved in the folder and the folder is monitored for new items.

Note: The journal, notes, sent items, tasks folders cannot be up-to-date enabled.

You can use MDBvu32 and look at the properties of the Inbox, Calendar or Contacts, you will see an associated message which is the WireLessOnSave Storeside EventSink

Additionally you can use regevent.vbs to view the binding too. The Bindings are the same for the Calendar and Contacts folders too.

Microsoft Windows [Version 5.2.3790] (C) Copyright 1985-2003 Microsoft Corp. C:\tools>cscript regevent.vbs enum file://./backofficestorage/homealone.local/mb x/wypfl9/inbox all Microsoft (R) Windows Script Host Version 5.6 Copyright (C) Microsoft Corporation 1996-2001. All rights reserved. DAV:contentclass, urn:content-class:storeeventreg http://schemas.microsoft.com/exchange/events/EventMethod, OnSave http://schemas.microsoft.com/exchange/events/SinkClass, Exchange.OmaEventSink.1 http://schemas.microsoft.com/exchange/events/MatchScope, EXACT http://schemas.microsoft.com/exchange/events/Criteria, WHERE "DAV:ishidden"=FALSE

Mailbox Event Bindings

MDBvu32

regevent.vbs


The AirNotifyDeviceInfo.XML in the user’s NON_IPM_SUBTREE is updated with the binding map and the device information.

Logging can be turned on to Brief or Verbose on the device. This creates a Serverlog0.txt and a Synclog.txt on the device.

AirNotifyDeviceInfo


Beneath the GUI: Device Info XML / Notify Guids

Information about the user’s devices, folders that are set up for notifications, and the device state information is stored in the user’s mailbox. It can be viewed through the following URL.

http://servername/exchange/user/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/AirNotify.xml

In the graphic above is a sample of the AirNotifyDeviceInfo.XML for a device configured to use a corporate service provider. There are two sections in this file. The Binding Map contains the folder-device mapping. The folder GUIDs and device IDs are stored. In this example, there are three folders configured for notifications to the same device.

In the Devices section, the device address for each of the devices the user has provisioned is stored. If a Corporate Service provider is used, the GUID for the provider is stored in the Carrier tag of the XML. The Notify GUID and the expiry are stored as well.


<?xml version="1.0" encoding="utf-8" ?> <DeviceInfo xmlns="AirNotify:"> <Version>1.1</Version> <BindingMap> <Folder> <FolderId>726a4c58dba56e409f3d3563a8bf953c-1c48ec9</FolderId> <DeviceId>3DC1E291F008003188000050BF325173</DeviceId> </Folder> <Folder> <FolderId>726a4c58dba56e409f3d3563a8bf953c-1c449ad</FolderId> <DeviceId>3DC1E291F008003188000050BF325173</DeviceId> </Folder> <Folder> <FolderId>21a89a3cbbfd2d45a1d02c7700f912af-2c46349</FolderId> <DeviceId>3DC1E291F008003188000050BF325173</DeviceId> </Folder> </BindingMap> <Devices> <Device> <Id>3DC1E291F008003188000050BF325173</Id> <FriendlyName>Pocket_PCx</FriendlyName> <DeviceAddress>2145078316</DeviceAddress> <Carrier>{E9EF8E03-4966-4E9D-B353-06B9D2FC41C8}</Carrier> <OMASyncInfo> <NotifyGUID>{ADFADFAA-7DF5-0799-801B-83879603C301}</NotifyGUID> <Expiry>2003-04-15T23:04:46.617Z</Expiry> </OMASyncInfo> </Device> </Devices> </DeviceInfo>


When notifications are enabled on the device, a notify enable command is sent to the server. This Notify command sends the DeviceInfo, lifetime and the folder list. A sync is forced even when there are no items to sync; i.e. the GetItemEstimate call returns zero. This is done in order to send the NotifyGUID to the server.

When a user disables Notifications by changing the schedule, a Notify command is sent with lifetime of zero.

When an event occurs on the server triggering a notification, the notification is formatted with the NotifyGUID from the AirNotifyDeviceInfo.XML on the server.

The device stores two Notify GUIDs in the registry: \\HKCU\Software\Microsoft\AirSync\Settings\NotifyGUIDOld and \\HKCU\Software\Microsoft\AirSync\Settings\NotifyGUIDNew.

The device processes notifications by comparing the GUID in the notification that it received with the GUIDs stored in the registry. If the notification contains a GUID that does not match the GUIDs stored in the registry, the notification is discarded.

The device generates a GUID and stores it in NotifyGUIDNew as soon as it sends a sync command. This GUID is sent to the server. The server updates the AirNotifyDeviceInfo.XML file with this NotifyGUID at the beginning of the sync session.

At the end of a successful sync, this GUID is copied over to NotifyGUIDOld on the device. The two GUIDs are identical if sync was successful.

If sync fails due to a connectivity issue or some other reason, both the GUIDs are considered valid. The device will process notifications that contain either of the two GUIDs stored in the registry.

1. NotifyGUID on the server corresponds to the GUID stored in NotifyGUIDOld on the device.

2. Device connects to the server, generates a new GUID, sends it to the server, and stores it in NotifyGUIDNew.

3. The device temporarily accepts notifications formatted with either NotifyGUIDOld or NotifyGUIDNew because it is possible that the new GUID never made it to the server.

4. The server updates the AirNotifyDeviceInfo.XML to this new GUID at the beginning of the sync session.

5. Device syncs and server gets the changes. The device copies the GUID from NotifyGUIDNew to NotifyGUIDOld.

If the device is set to use "When new items Arrive", an expiry is set by sending the lifetime. The lifetime for notifications sync is based on the mobile schedule. For example, if the device is setup for notifications during the peak time (8:00 A.M. to 8:00 P.M.), the expiry time in AirNotifyDeviceInfo.XML will show an expiry at 8:00 P.M. Moving the peak time in mobile schedule causes the device to resend the lifetime for notifications sync.

When the time is changed on a device that is enabled for notifications, the notification lifetime/expiry on the server needs to be updated. A sync is forced to send up a notification lifetime update when the time changes backward.

Notify GUIDs

Lifetime or Expiry


When a device that is enabled for Notifications is cradled, notifications are disabled temporarily by sending a Notify command with a LifeTime of zero. A folder list is not sent with the Notify command.

<Notify xmlns="AirNotify:"> <LifeTime>0</LifeTime> </Notify>

When the device is un-cradled, notifications are re-enabled.

Notify xmlns="AirNotify:"> <LifeTime>Remaining time in Notifications Mode</LifeTime> <Enable>….

Normally when a device is enabled for Notifications, the folder list is sent to the server with the Notify command. Since this would cause a performance hit each time the device is un-cradled, a registry is maintained on the device to indicate that this is a temporary condition. If the registry NotifyTempDisabled is set to one in the registry when the Notify command is sent, the folder list is not included.

Temporary disabling of notifications


Beneath the GUI: Up-To-Date Notifications Message Flow Overview

On the Exchange 2003 server, there are two components: an Outlook Mobile Access Sink, and an Outlook Mobile Access categorizer (MISCat.dll).

During setup, OMASINK.dll is copied to:

[17:08:15] Copying c:\program files\exchsrvr\bin\omasink.dll

And it is registered with the system

[17:13:39] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32 /u /s omasink.dll;180000> -- ID:31259 --

During setup, MISCAT.dll is copied to:

[17:08:15] Copying c:\program files\exchsrvr\bin\miscat.dll

And it is registered with the system:

[17:13:39] Interpreting line <CreateProcessSafe:C:\Program Files\Exchsrvr\bin;regsvr32 /u /s miscat.dll;180000> -- ID:31259 --

And is bound to SMTP here:

Event: SMTP Transport OnCategorize ID: {CD78B138-3DFC-49AE-99FC-FCD6300A9466} Name: Mobile Categorizer SinkClass: Exchange.MisCat Enabled: True SourceProperties: { priority = 200 }

Mess

OMASINK.dll

MISCAT.dll

Process Flow

Message Track


A netmon shows the message being sent out to the Internet. Note the RCPT TO

220 xpclient.homealone.local Microsoft ESMTP MAIL Service, Version: 6.0.2600.1106 MAIL FROM:<> SIZE=503 250 2.1.0 <>....Sender OK RCPT TO:[email protected] 250 2.1.5 [email protected] BDAT 503 LAST Received: from mail pickup service by alone.homealone.local with MicrosoftSMTPSVC Wed, 3 Dec 2003 15:15:46 +0000 To:<[email protected]> From:<[email protected]> Message-ID: <6e64b878346b2b4a8e4d040a9d9c96aa-20c0@OMA> Subject: 8b562609653fbb44b8e11a2b52c2282e-33f2 Date: Wed Dec 3 15:15:46 2003 Content-Type: text/plain; charset=iso-8859-1 X-OriginalArrivalTime: 03 Dec 2003 15:15:46.0070 (UTC) FILETIME=[53602B60:01C3B9B0] //SCKL040A AwFqAAADxgADBQHDEEf0TSfoMBerAOgWcZi5wwEB 250 2.6.0 <6e64b878346b2b4a8e4d040a9d9c96aa-20c0@OMA> Queued mail for delivery QUIT 221 2.0.0 xpclient.homealone.local Service closing transmission channel

NetMon


Beneath the GUI: Outlook Mobile Access Sink

When the binding fires, OMASink::OnSave() generates a notification and drops it in the SMTP Pickup directory to be handled by the Exchange transport. An example of the notification is shown below:

Received: from mail pickup service by alone.homealone.local with Microsoft SMTPSVC; Wed, 3 Dec 2003 15:15:46 +0000 To: <[email protected]> From: <[email protected]> Message-ID: <6e64b878346b2b4a8e4d040a9d9c96aa-20c0@OMA> Subject: 8b562609653fbb44b8e11a2b52c2282e-33f2 Date: Wed Dec 3 15:15:46 2003 Content-Type: text/plain; charset=iso-8859-1 X-OriginalArrivalTime: 03 Dec 2003 15:15:46.0070 (UTC) FILETIME=[53602B60:01C3B9B0] <?xml version="1.0" encoding="utf-8"?><DeviceInfo xmlns="AirNotify:"><Version>1.1</Version><BindingMap><Folder><FolderId>8b562609653fbb44b8e11a2b52c2282e-3347</FolderId><DeviceId>DUMPOWEFB</DeviceId></Folder><Folder><FolderId>8b562609653fbb44b8e11a2b52c2282e-3346</FolderId><DeviceId>DUMPOWEFB</DeviceId></Folder><Folder><FolderId>8b562609653fbb44b8e11a2b52c2282e-33f2</FolderId><DeviceId>DUMPOWEFB</DeviceId></Folder></BindingMap><Devices><Device><Id>DUMPOWEFB</Id><FriendlyName>Pocket_PC</FriendlyName><DeviceAddress>[email protected]</DeviceAddress><Carrier/><OMASyncInfo><NotifyGUID>{274DF447-30E8-AB17-00E8-167198B9C301}</NotifyGUID><Expiry>2003-12-03T20:51:21.376Z</Expiry></OMASyncInfo></Device></Devices></DeviceInfo>

The Body of the message is the information from the user’s AirNotifyDeviceInfo.XML

The X-Sender field (821) is set to blank to prevent non-delivery reports (NDRs) from coming back to the user. The From field (822) is set to the actual username.


The Outlook Mobile Access categorizer uses the DSAccess component to retrieve information from the Active Directory. The Outlook Mobile Access categorizer will check for the following when processing a notification:

1. Up-to-date notifications disabled on a global basis.(Exchange System Manger, Global Settings, Mobile Services).

2. User been disabled for up-to-date notifications.

3. The current time is within the expiry time specified in the XML.

If up-to-date notifications has been disabled, the bindings are cleaned up. This is described in the next section.

If the current time is within the expiry time, a notification will be sent out. Otherwise the notification is discarded.

The categorizer compares the subject of the notification with the folder ID in the XML. If there is no match, the notification is discarded. If there is a match, the categorizer retrieves the Device IDs bound to this folder from the Binding map section of the XML. It then looks up the Devices section of the XML to retrieve the Device address.

It creates a new notification message. If the device address is an SMTP address, the message will be addressed to this SMTP address. If a corporate service provider is used, the Carrier GUID in the XML is used to retrieve the wireless Carrier domain from the Active Directory. The phone number is concatenated with the Wireless carrier domain and the message is addressed to this domain.

An example of the notification is shown below:

Received: from mail pickup service by alone.homealone.local with Microsoft SMTPSVC; Wed, 3 Dec 2003 15:15:46 +0000 To: <[email protected]> From: <[email protected]> Message-ID: <6e64b878346b2b4a8e4d040a9d9c96aa-20c0@OMA> Subject: 8b562609653fbb44b8e11a2b52c2282e-33f2 Date: Wed Dec 3 15:15:46 2003 Content-Type: text/plain; charset=iso-8859-1 X-OriginalArrivalTime: 03 Dec 2003 15:15:46.0070 (UTC) FILETIME=[53602B60:01C3B9B0] //SCKL040A AwFqAAADxgADBQHDEEf0TSfoMBerAOgWcZi5wwEB

The body of the message contains the Base64 encoded NotifyGUID which is retrieved from the XML.

If there are multiple devices bound to this folder, the message is bifurcated and the other device addresses are added.

The Outlook Mobile Access categorizer is also responsible for cleaning up the bindings and batching of notifications.

When a user is enabled for notifications, the bindings are created in the user’s mailbox. The bindings on mailboxes have an adverse effect on store startup time and take up store sessions. Therefore it is imperative that the bindings be cleaned up when the user is disabled or has stopped using the device, etc.

When a user is disabled by the administrator, the binding is disabled by the Categorizer when the first notification fires after the user was disabled.

When the administrator disables push for a user, the push bit in the msExchOmaAdminWirelessEnable property is set to one ( false) on the user

Binding cleanup

Disabled user


object. The categorizer checks this bit and if it is set, it will delete the bindings and delete the Binding Map from the AirNotifyDeviceInfoXML file.

1. The binding map is read from the AirNotifyDeviceInfo.XML to determine which deviceIDs are registered with the folders.

2. The expiry time is read for each deviceID from the file.

3. All devices for which Current System time is greater than “Expiry + 1 week” are enumerated.

If the current system time exceeds the expiry time plus one week (this is hard-coded for Exchange 2003 RTM), then the binding in that folder will be deleted by the categorizer. The XML is modified to reflect the bindings that were deleted.

Expired Device


Beneath the GUI: Batching of Notifications

A notification is sent when any of the following things occur in a folder that the user has set up for up-to-date notifications Sync.


New e-mail

New calendar item

New/Edited contact

Each notification delivered to the device counts as an incoming SMS (the Sender should pay for this) and the end user incurs a cost for each notification (Due to the fact that an automatic sync is going to raise a General Packet Radio Service [GPRS] connection). The notification also affects battery life. It also causes increased SMTP traffic on the exchange server. Therefore, notifications are not sent for each event. A batching algorithm is used to send notifications only when the device is out of sync and has not already been notified. This makes up-to-date notifications cost effective.

The batching algorithm works as following:


The device is considered to be in one of two states: synchronized or pending sync. When a user syncs, the device sends the NotifyGUID and this gets written to the AirNotifyDeviceInfo.XML at the beginning of the sync session. The Categorizer keeps track of the last known NotifyGUID (tracking GUID) and the timeout for each device in memory.

1. An event in the user’s mailbox triggers a notification.

2. If the device is in a synchronized state, a notification is sent to the device, the device state is changed to pending sync and the timeout is set to the current time + 15 minutes.

(i.e.) if the tracking GUID in memory is not equal to the NotifyGUID in the XML, a notification is sent, the tracking GUID is changed to the NotifyGUID and the timeout is set to the current time +15 minutes.

3. If the device state is pending sync, a notification is not sent to the device unless the device has been in the pending sync state for longer than the timeout value. In this case, a notification is sent to the device, and the timeout value is reset. The timeout is 15 minutes and can be configured through the registry.

For example, if the tracking GUID in memory is equal to the NotifyGUID and the current time is less than the timeout, a notification is not sent; if the tracking GUID in memory is equal to the NotifyGUID and the current time is greater than the timeout, a notification is sent, the timeout value is set to time + 15 minutes.

When the device synchronizes with Exchange, the device state is changed to synchronized.

(i.e.) the NotifyGUID is updated.

An example of how notifications are batched: Initial Time = t t: email1 arrives �notification sent. t+2: email2 arrives �notification is not sent, since the device has not sync’d back yet t+4: device syncs �email1 & email2 are sync’d to the device t+10: email3 arrives �notification is sent t+11: notification is lost in carrier network t+20: email4 arrives �notification is not sent, since the device hasn’t sync’d back yet t+25: fallback timer kicks in � 15 minutes has elapsed since we notified the device. This may indicate the packet was dropped, so we will send on the next event t+28: email5 arrives � notification is sent t+31: device syncs � email 3/4/5 are sync’d

Worst case wait time for a message in case the SMS gets dropped is timeout value + time until the next e-mail that triggers a notification arrives.


Beneath the GUI: Up-To-Date Notifications Message Format

Example

To: [email protected] From: <> Message-ID: <344d4217f23ae84aaedceecda39f358e-1d1450e@OMA Received: from mail pickup service by DF-GROMMIT-01.platinum.corp.microsoft.com with Microsoft SMTPSVC; Mon, 24 Feb 2003 10:36:14 -0800 To: <[email protected]> From: <> Message-ID: <344d4217f23ae84aaedceecda39f358e-1d1450e@OMA> Subject: 7529a5b36290aa458b9e1fc2d5ff85a6-3c07 Date: Mon Feb 24 18:36:13 2003 Content-Type: text/plain : charset=iso-8859-1 //SCKL0409 AwFqAAADxgADBQHDEHy6gHshpMoKgFTifjPcwgEAAQ==

To: Contains SMTP device address assigned to the device/user by the carrier

From: Set to empty (‘<>’)

Message-ID: Structure of message ID is <GUID> + ‘@OMA’

To: Contains user’s exchange SMTP address

From: Set to empty (‘<>’)

Message-ID: Same as 821 header

Subject: Value is the FolderID where the new e-mail, calendar, contact item arrived

Date: Time of message submission

Content-Type: There will be a ‘text/plain’ body part with the character set equal to ISO-8859-1

SMTP Message Format

821 Headers of Interest

822 Headers of Interest


The message body contains a Wireless Datagram Protocol (WDP) port address followed by a base64 encoded string.

In this configuration, the carrier is responsible for converting the SMTP notification to an SMS and delivering it to the appropriate device. One such example is T-Mobile US’s implementation, which essentially fields e-mail addressed to <phone#>@voicestream.net, extracts the message body, and sends it to the device as an SMS.

At a high level, the requirements for up-to-date notifications support at such a gateway are as follows:

The SMTP Server must accept up-to-date notifications messages.

o Note: up-to-date notifications messages currently have empty 821 & 822 ‘from’ headers, concerns over allowing such messages through, you could potentially use the following criteria:

821 Message-ID = ‘*@OMA’

The SMTP message body itself must not be modified in the conversion to SMS. Data may be prepended or appended to the original body, provided the following still hold

o The original body (i.e. ‘//SCKL…..’ ) still fits within the SMS

o The original SMTP body (i.e. ‘//SCKL…..’ ) is preserved somewhere in the SMS text body

The subject of the message need not be in the SMS, and can be excluded in the conversion in order to conserve bytes.

Note: This need not concern you; it is mostly here to provide additional context for the carrier conversion requirements.

Must be WDP formatted message (documented in the WAP spec - the //SCKL stuff).

Must be sent to port 1034.

Must be received via WDP (over SMS) or UDP.

Must contain the base64 string immediately after the WDP format header.

Prepend / Appended data is irrelevant, except where it bumps the important information out of the payload.

Message Body

Requirements for SMTP->SMS Conversion at Carrier

Device Requirements for Up-To-Date Notifications SMS format


Lesson 4: Troubleshooting


This lesson will look at a number of troubleshooting tips, tricks, and techniques that will help you discover what is causing Exchange ActiveSync to fail and how to fix it.

Introduction


Troubleshooting: General


Up-to-date notifications is an extension to Server ActiveSync, so you need to ensure that Server ActiveSync is configured and working correctly.

Start by trying the basics.

Exchange ActiveSync needs Outlook Web Access to work. The initial checks should be to check that the Global Setting for Exchange ActiveSync are enabled, followed by ensuring the User has User Initiated Synchronization enabled.

Next check that Outlook Web Access works using Internet Explorer. Connect to the following Web pages:

http://<Exchange2003-backend>/exchange http://<Exchange2003-frontend>/exchange

Next check that Outlook Mobile Access works, but using Internet Explorer. Connect to the following Web pages:

http://<Exchange2003-backend>/oma http://<Exchange2003-frontend>/oma

Make sure that you can perform a cradle ActiveSync and an “over the air” ActiveSync.

It is also good to do a messagetrack to see if the message has left the system. Additionally you should turn up diagnostic logging a capture perfmon counter to ensure that the eventsink is actually firing.

You can check the bindings of a user by using regevent.vbs. To run this against a mailbox, you need to use the runas command to open a command prompt. Then run the following:

Things to Try

Outlook Web Access

Outlook Mobile Access

Exchange ActiveSync

Message Tracking, Diagnostic Logging and Perfmon

REGEVENT.vbs



This KB article is one of the first places to start:

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

SUMMARY

The purpose of this article is to provide steps to help you to troubleshoot issues with Exchange 2003 up-to-date Notifications. This article lists the following steps:

#1: Increase Logging to Maximum for MSExchangeActiveSyncNotify

#2: Turn On Message Tracking for This Server

#3: View the Event Log to Verify That the Message Was Processed

#4: Verify That the Message Was Processed by the Outlook Mobile Access Categorizer

#5: Verify That the Message Left the Corporate Messaging Organization or the Exchange 2003 Messaging Organization

MORE INFORMATION

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, 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

822176


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.

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".


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.

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" (without the quotation marks) 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.

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".

Increase Logging to Maximum for MSExchangeActiveSyncNotify

Turn On Message Tracking for This Server

View the Event Log to Verify That the Message Was Processed

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


4. Click the "Filter" tab, and then type "10310" (without the quotation marks) 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.

1. Note the MessageID from the Event 10310.


3. Expand the "Tools" container.

4. Double-click "Message Tracker".

5. Type the MessageID with "@OMA" (without the quotation marks) 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" (without the quotation marks)

1. Verify that your device is running Windows Mobile 2003.

2. Verify that you can connect to an Exchange 2003 server.

3. Verify that up-to-date notifications is enabled globally and at the user level.

4. Verify that your mobile operator supports up-to-date notifications (i.e. they support the conversion of SMTP e-mail message into SMS message).

5. Verify that your device is capable of receiving Short Message Server.

6. If you are using a device running Windows Mobile 2003 against an Exchange 2003 server, verify that the OPTIONS command is not blocked.

For more information on NexTags, please see the Exchange ActiveSync troubleshooting module.

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

Checklist


Troubleshooting: Debug Tracing


Regtrace can be used to enable tracing for the MSExchangeActiveSyncNotify object. For more information about regtrace, you may refer to the following Knowledge Base article:

238614 XCON: How to Set Up Regtrace for Exchange 2000

The Modules to add are: OMAsink MIScat. Make sure there is a carriage return between the modules.

Regtrace is included with Windows Server 2003. To view the output of regtrace, use traceviewer (tracevwr). Tracevwr can be found at \\exutils\tracevwr.

Note: Disable regtrace after generation the trace file.

1. Click Start, ActiveSync, Tools, Options, Server, Advanced.

2. Minimize the keyboard.

3. Change the logging level to Brief or Verbose.

4. Close the Options dialog.

Setting the logging level to brief logs the headers, whereas setting it to verbose logs sync requests and responses in addition to the headers. The log is saved in text format in the Windows\ActiveSync folder; for example, windows\ActiveSync\serverlog0.

By default, the log file gets cleared at the beginning of a sync session. It is important to rename the file before you start another sync. If you have

Regtrace

Device Logging


configured automatic synchronization, it is especially important to rename this file to prevent it from being overwritten.

With PocketPC 2003 devices, it is possible to specify the number of log files to generate before overwriting. This can be specified through a registry key on the device.

HKEY_CURRENT_USER\Software\Microsoft\AirSync\Logging.

The value for “Number of Logs” can be changed from the default of 1.

Steps to retrieve the log file: 1. Sync till the point of failure.

2. Disconnect the device. This is to prevent the log file from getting overwritten by the next automatic sync. If you have up-to-date notifications set up, disconnecting the device will force a sync wirelessly to re-enable notifications. Notifications are disabled when the device is cradled. If up-to-date notifications are used, it is best to change the number of log files as indicated before to avoid disconnecting the device.

3. Click on Start, Programs, File Explorer.

4. In File Explorer, browse to the My Device\Windows\ActiveSync folder.

5. Tap and hold on the file “ServerLog0” and rename it to some other name (for example, “Log0”).

6. Connect to the desktop.

7. In the desktop ActiveSync program, choose Explore, browse to the ActiveSync folder, and copy the log file to a folder on the desktop.

8. Turn the logging back to Brief or None.

Here is an Example Device Log:


=-= Build 13100 =-= =-= No XIP Information Available =-= alone =-=- [17/2/2004 1:25:39.0] -=-= =-=-=-= Client Request =-=-=-= POST Microsoft-Server-ActiveSync?User=wypfl9&DeviceId=EXN1JXGBB&DeviceType=PocketPC&Cmd=FolderSync Accept-Language: en-us MS-ASProtocolVersion: 2.0 Content-Type: application/vnd.ms-sync.wbxml -=-=-=- Start of Body -=-=-=- <?xml version="1.0" encoding="utf-8"?><FolderSync xmlns="FolderHierarchy:"><SyncKey>{DE58A70F-3B27-4D02-8FAC-A89D16748C81}1</SyncKey></FolderSync> =-=- [17/2/2004 1:25:39.0] -=-= =-=-=-= Server Response =-=-=- HTTP/1.1 401 Unauthorized Content-Length: 83 Content-Type: text/html Server: Microsoft-IIS/6.0 WWW-Authenticate: Negotiate WWW-Authenticate: NTLM WWW-Authenticate: Basic realm="alone" X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 6.0.2.5530 Date: Tue, 17 Feb 2004 09:30:53 GMT -=-=-=- Start of Body -=-=-=- <?xml version="1.0" encoding="utf-8"?><FolderSync xmlns="FolderHierarchy:"><SyncKey>{DE58A70F-3B27-4D02-8FAC-A89D16748C81}1</SyncKey></FolderSync> =-=- [17/2/2004 1:25:39.0] -=-= =-=-=-= Server Response =-=-=- HTTP/1.1 401 Unauthorized Content-Length: 83 Content-Type: text/html Server: Microsoft-IIS/6.0 WWW-Authenticate: NTLM TlRMTVNTUAACAAAACQAJADgAAAAGgokCs17SbT0taK4AAAAAAAAAAJoAmgBBAAAABQLODgAAAA9IT01FQUxPTkUCABIASABPAE0ARQBBAEwATwBOAEUAAQAKAEEATABPAE4ARQAEAB4AaABvAG0AZQBhAGwAbwBuAGUALgBsAG8AYwBhAGwAAwAqAGEAbABvAG4AZQAuAGgAbwBtAGUAYQBsAG8AbgBlAC4AbABvAGMAYQBsAAUAHgBoAG8AbQBlAGEAbABvAG4AZQAuAGwAbwBjAGEAbAAAAAAA X-Powered-By: ASP.NET MicrosoftSharePointTeamServices: 6.0.2.5530 Date: Tue, 17 Feb 2004 09:30:53 GMT


Next Tags


With Mobile Information Server 2002, NexTags was shipped on the CD and enabled tracing of the entire sync session. With Exchange ActiveSync, NexTags will not be shipped with Exchange Server 2003. It will be available to Microsoft® Product Support Services to use as required.

To troubleshoot Exchange ActiveSync issues, enable all in NexTags.

To use NexTags, follow the steps below:

1. Run nextags.exe on the server running Exchange ActiveSync.

2. On the 'Options' tab, specify a location for the output file in the 'Trace File' field.

3. Set 'Trim Percentage' to 30%

4. Set the ‘Limit file size to:’ 10mb

5. Leave ‘User Names:’ blank to capture all users. For individual users, enter the user's alias or aliases, separated by a semi-colon (;).

6. For 'Mode', be sure 'Real Time' is unchecked.

7. On the 'Tags' tab, navigate down the whole tree and enable everything.

8. Click 'Enable Tracing'.

9. Click 'Apply' to confirm all settings and 'OK' to exit.

When users specify an attempt to sync, Exchange ActiveSync will output all logging information to the file specified on the 'Options' tab. This is useful for troubleshooting and when working with Microsoft Product Support Services to determine the cause for synchronization failures.

NexTags


When you have finished, make sure that you click on ‘Disable Tracing’ to stop nextag.

The Nextags log can be read in conjunction with the IIS logs.

For more information on NexTags, please see the Exchange ActiveSync troubleshooting module.


Troubleshooting: Event Logs

Diagnostics logging can be turned on through Exchange System Manger under the MSExchangeActiveSyncNotify service.

The entries are Outlook Mobile Access Push Categorizer and Outlook Mobile Access Push Event Sink.

It is also possible to enable tracing and verbose logging for MSExchangeActiveSyncNotify object.

The following registry keys can be used to enable verbose logging the MSExchangeActiveSyncNotify object:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeActiveSyncNotify\Diagnostics] "10 OMA Push Cat"=dword:00000007

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\MSExchangeActiveSyncNotify\Diagnostics] "11 OMA Event Sink" =dword:00000007

Set the value data to 7 as shown below:

Note: Before enabling verbose logging via the registry, turn up diagnostic logging to “Maximum” for the MSExchangeActiveSyncNotify object in Exchange System Manager.

For more information on possible event logs see Module 12 Appendix C.


Troubleshooting: Performance Monitor Counters


MSExchangeActiveSyncNotify counters display performance statistics for Exchange ActiveSync Notifications.

The counters for the Event Sink (Outlook Mobile Access Sink) and the Outlook Mobile Access Categorizer (MISCat) are available in the Performance Microsoft® Management Console (MMC) under the object MSExchangeActiveSyncNotify object.

Number of onSave invocations .This counter is incremented each time the EES’s onSave method is called by ExOLEDB. Note that this counter will reflect both events you care about and events you ignore.

Number of onSave invocations per second.

Number of notifications submitted to the pickup directory. This counter is incremented after all Outook Mobile Access Sink actions have been completed and the notification is successfully written to the pickup directory.

Number of notifications submitted per second.

Ignored onSave invocations. This counter is incremented each time EES’s onSave method is called by ExOLEDB and the EES chooses to ignore the event.

Number of ignored onSave invocations per second.

OmaSink OnSave Events Total

OmaSink OnSave Events/sec

OmaSink Notifications Sent Total

OmaSink Notifications Sent/sec

Notifications Ignored Total

OmaSink Notifications Ignored/sec

OmaSink Notifications Discarded Total


Number of notifications dropped due to errors. Notifications that did not make it to the pickup directory for reasons other than ‘they were intentionally ignored’, i.e. XML file missing, Pickup directory not found, etc.

Number of notifications dropped due to errors per second.

Number of messages processed. Incremented when the categorization sink ‘picks up’ an Outlook Mobile Access message.

Rate of messages processed.

Number of notifications sent. Incremented when a notification is delivered via SMTP.

The rate at which notifications were sent.

Number of notifications ignored. Incremented when a notification is not delivered as a result of the notification batching algorithm.

Number of notifications dropped. Number of notifications that were not delivered due to error conditions.

Number of expired notifications. Incremented when a notification is not delivered due to system time being past notification expiry time.

Number of bifurcations. Incremented when a notification is bifurcated for multiple devices

Additionally there a number of counters for generic OLEdb events, under the MSExchange Oledb Event counter.

OmaSink Notifications Discarded/sec

Categorizer Notifications Processed Total

Categorizer Notifications Processed/sec

Categorizer Notifications Sent Total

Categorizer Notifications Sent/sec

Categorizer Notifications Ignored Total

Categorizer Notifications Discarded Total

Categorizer Notifications Expired Total

Categorizer Notifications Bifurcated Total


Lesson 5: Tools


Up-To-Date Notifications Troubleshooter This is a tool that is available as a download from Microsoft.com

http://www.microsoft.com/downloads/details.aspx?FamilyId=7718A338-A9F5-43D6-9E20-141189283C82&displaylang=en

The Up-to-Date Notifications troubleshooting tool allows administrators to solve common notification issues. . The administrator enters his domain name and credentials, and then the mailbox name of the user he is troubleshooting. The tool then displays a Web page showing a list of devices the user has, what delivery method and address the device uses, and when the device expires. The page also allows the administrator to send a test e-mail to the specified devices.

1. Copy the following files to a folder on your machine, including the Bin folder

default.aspx

sendmail.aspx

Global.asax

style.css

script.js

web.config

2. Go to Start, Program Files, Administrative Tools, Internet Services Manager.

3. Right-click Default Web Site and use the Virtual Directory Creation Wizard to set up a virtual directory.

4. Enter a name you want to use for the Web application (for example, AUTD).

Installation


5. Enter path to the directory that contains the content (in this case, D:\AUTD).

Note: If you are using SharePoint Portal Services on this server, you will need to exclude this Virtual Directory in SharePoint Portal Services Managed Paths.

6. To access the site, open up your browser and type the following:

http://<server name>/AUTD

This tool consists of two web pages: A main page that is used to input user and admin information (the default page of this application), and an Information page which shows user’s device information that will help the admin narrow down notification issues that the user might be having. There are also two modes for this tool.

There are two different application modes for this tool: Basic mode and Advanced mode. Running the up-to-date notification tool in Basic mode is used when both the Exchange user account and his mailbox are in the same domain. Advanced mode should be used in the case of cross-forest/domain topologies. That is, the administrator should only use this mode when the Exchange user account is one domain and his server in another. The default mode for the tool is the Basic mode.

The application mode can be set using the web.config file

To set the mode, change the value for the AppMode parameter under appSettings to one of the following:

Basic

Advanced </system.web> <appSettings>  <add key="AppMode" value="Basic" />  <add key="ExchangeAccessProtocol" value="http" /> </appSettings> </configuration>

Note: in the advanced mode, the main page has an extra field: Exchange Domain. Now the application requires the admin to put in the Exchange server domain – this is merely to look after the case where the Exchange user is in a different domain than his Exchange mailbox.

Note The Administrator using this tool must have “Read” privileges on the user’s mailbox. A possible way to do this would be:

Using Up-to-Date Notifications Troubleshooting Tool

Setting Application mode


Open up Exchange System Manager, navigate to the user’s mailbox store and right-click properties.

Select the security tab and click on the advanced button.

Click on the add button and enter administrator into the object name box and click on the check names button. Once underlined, click OK.

Now check Full Control – Allow, then click OK a few time to exit

Note: this has enabled the administrator to have FULL control over ALL mailboxes on the store. You should NOT recommend this to a customer. Basically an explicit Allow overrides any inherited Deny.

The Up-to-Date Notifications Troubleshooting tool has support for using SSL (to both Exchange front-end and back-end servers). The administrator must do the following on the web server hosting this tool to set up an SSL connection to front-end:

1. Install an SSL certificate from a trusted certification authority (CA) for the tool virtual directory on the Web server (for example, http://certserver01/certsrv ) on the Exchange front-end server.

2. Run the application by typing https:// instead of http:// in the browser window.

1. Install an SSL certificate from a trusted CA for the Exchange virtual directory (for example, http://certserver01/certsrv) on the Exchange back-end server.

2. In IIS on the Default Web Site, right-click the Exchange virtual directory and select Properties.

3. Select the Directory Security tab and then click Edit from Secure Communications and select Require Secure Channel.

The main page has the following fields and they all need to be filled out by the admin before the form can be submitted.

Admin domain\username

Admin password

Exchange domain\username

Exchange server domain*

*Note: This field shows up only in the Advanced mode and it is there for the reasons mentioned in the previous section.

Note: that in the above, the domain name can be either in FQDN form or NetBIOS form. Entering the wrong information in any of the above fields or leaving some of them blank will result in errors.

After the Admin and the user sections have been filled out, click BEGIN TROUBLESHOOTING to submit the form.

After you submit the information for the Main page, the Information page appears. This page will show device information pertaining to the user whose information was entered in the previous page.

Using SSL with the Up-to-Date Notifications Troubleshooting Tool

Exchange Front-end Server Requirements:

Exchange Back-end Server Requirements:

Main Page

Information Page


You can use this information to troubleshoot notification issues the user might be having by verifying the information in the displayed fields. The following section shows the information that will be displayed for the Information page:

Org Info (found in the small panel on the left):

• Carriers: Shows the number of carriers in your organization’s Active Directory.

User Info (found in the main panel in the middle):

• User Name: Shows the name of the Exchange user.

• Exchange Server: Shows the name of the Exchange server that the specified user has his mailbox in.

• Device: Shows the name of the user’s device.

• Delivery: Shows how notifications will be delivered to the device.

• Address: Shows the address of the above device.

• Expires: Shows the date and time that the device will expire by if it does not synchronize again, which will stop up-to-date notifications from being sent out.

• Send Mail: Feature that can be used to verify that mail flow is working from your Exchange server to the Mobile Operators network with the specified address.

You can validate these fields to determine whether the notification problem that the user is having is related to the values that these fields are set to. For instance, if the user is not receiving any notifications, one of the first things that you can do must check is ensure that the user’s account has not expired. Having an expired account would certainly prevent the user from being up-to-date.

If all the fields on this page are set to correct values, you can try sending a test mail to the device using the SEND MAIL button.


Review

1. What version of device works with up-to-date notifications?

2. What is the name and location of the store sink dll?

3. What is the name of the new mobile categorizer and what is it bound to?

4. What is the command line to view store events that are bound to a mailbox?

5. What is the KB article that is a good place for troubleshooting?

52 Appendix A

Appendix A

Step by Step Walk Through of Pocket PC Configuration

Pocket PC Configuration Start with looking at how the Pocket PC device gets configured.

When a user with a device running Windows Mobile 2003 synchronizes for the first time, you should the following dialog bubble on the device:

If you did not see the above bubble, you will need to check that your device is enabled for up-to-date notifications. To do so, go to:

Start ActiveSync Tools Options Mobile Schedule.

Click Yes to this Dialog.

The bubble

Appendix A 53

You will then be taken to this screen:

Pull down one of the sync frequencies, for peak or off-peak times. You should see “When new items arrive”.

Note: If that entry is missing, then your device can NOT use up-to-date notifications.

Peak Time: 30 Minutes.

Off Peak: When new items arrive.

Notice that you can enable to use up-to-date notifications during peak times, off-peak times, or both. Since up-to-date notifications utilizes Short Message Service messages to force the device to sync, it is recommended that such method of synchronization only be used when your mail activity is low.

Mobile Schedule

Recommended sync settings

54 Appendix A

From the Mobile Schedule Page, click on the “peak Times” button.

Here can adjust the scheduling options to define your own “peak” times (when you receive a greater influx of mail). Once Finished, click ok.

If you have never set up your device to use this feature, you will receive an error letting you know that you need to provision your device address.

You will be taken back to this screen:

Go to this screen and click on the “Device Address” Button.

Peak Times

Device Address

Appendix A 55

Enter the Short Message Service address of your device under Device E-mail Address.

If your administrator has set up corporate service providers, you can select your operator from the drop-down box and enter just your device phone number under Corporate Service Provider.

OK out of that Device Address screen.

If you enabled your device to use up-to-date notifications, your device will launch a sync automatically to provision itself.

When a new message comes into your inbox, calendar, or contacts, the event sink is fired and this sends a special Short Message Service message to your phone. Once you have received it, a sync will launch automatically.

56 Appendix B

Appendix B

Troubleshooting Process flow for Up to Date Notifications

The following chart will walk through the steps to troubleshoot up-to-date notifications:

Support Overview

Appendix B 57

The questions to ask are:

Is the user provisioned correctly?

Are the up-to-date notifications leaving the enterprise?

Are the messages stuck in the MSN SMTP connector?

The primary tool to use is the up-to-date notifications troubleshooter. Ask the customer to set up the tool if it is not already installed. Follow the chart below to troubleshoot the issue using the Troubleshooter:

1. The administrator gets the user alias and SMTP address of the user’ s

device.

2. The administrator launches the up-to-date notifications troubleshooting tool and enter the username.

3. Is the up-to-date notifications tool able to retrieve the user’s information? If the up-to-date notifications tool was not able to retrieve the user’s information, verify the device is provisioned. Refer to the section labeled “Device Provisioning”.

4. If the up-to-date notifications tool was able to retrieve the user’s information, is the device information correct? If not, ask user to retype device address and re-sync.

5. If the device information is correct, is the device expired?

6. If the device is not expired, can the administrator send a message from the UTD troubleshooter? Can the administrator send a message from a mail client to the device SMTP address (i.e. [email protected])?

Using the up-to-date notifications Troubleshooting tool

58 Appendix B

7. Did the device receive the message from the mail client? If not, disconnect

the Internet connection on the device and reconnect. If the device still does not receive the message, you may need to contact the carrier.

8. If device receives the message from the mail client, but the up-to-date notifications and the message sent from the up-to-date notifications troubleshooter are not getting to the device, the administrator will need to find out if the up-to-date notifications notification is leaving the enterprise.

9. If the device is expired, the user would need to set schedule d sync and re-sync. Then set the device scheduler for “when new items arrive”. Resync.

10. Verifying if the message has left the enterprise? To verify if the message has left the enterprise, follow the steps in the following article: 822176 Troubleshoot Exchange 2003 Always-Up-To-Date Notification.

The article walks you through increasing diagnostic logging via the Exchange System Manager for the MSExchangeActiveSync object, using event viewer to check for specific event ID’ s and using Message Tracking to track the up-to-date notification.

After following these steps, you will be able to confirm if the notification left the enterprise. See the following diagram:

See KB article 822176 Troubleshoot Exchange 2003 Always-Up-To-Date

Notification

Increase Diagnostic Logging

EventID 11324 - Verify that the Exchange Event has fired

EventID 10310 - Verify that the Exchange up-to-date notifications SMTP component has passed the message to the SMTP service

Use Exchange Message Tracking to verify that the message has left the enterprise

o Use the Event log 10310 to get the Message ID for the message

o Search Exchange message tracking for the Message ID

Are notifications leaving the Enterprise?

Appendix B 59

o Verify that the message has left the Exchange Environment

o Check what the exit point was: Connector to MSN Mobile or Straight SMTP to the Carrier

Assume message flow is functional with the organization. If messages destined for MSN are getting stuck in the MSN SMTP connector queue, it could be an indication that the SMTP connector is not configured properly.

As mentioned before, the administrator will be provided with a set of credentials for the SMTP connector. The password is very complex and you need to make sure that administrator is typing it correctly. Please refer to the section labeled “Problems creating and configuring the SMTP connector”. Some things to try:

The administrator may try to reset the password through the Exchange enterprise administration Web site.

Do not cut and paste. Manually type the password

Use Telnet on the Exchange server and Telnet to the MSN server to port 25. For example, Telnet 208.29.145.38 25 and see if you get the banner. To find out the MSN server’s IP address, you can use something like http://codeflux and do an NSlookup to the domain specified in the address space of the connector.

On the properties of the SMTP connector, do not use DNS. Choose the setting to forward to a host and type the fully qualified domain name (FQDN) or IP of the MSN SMTP server.

If none of this works and the Connector team feels that the connector is setup properly, you may need to contact MSN Operations.

For more information on troubleshooting SMTP connector issues, please refer to the following articles:

200525 Using NSlookup.exe

319426 HOW TO: Configure the SMTP Connector to Link to Internet Domains in Exchange

279616 XCON: Adding a Registry Key to Re-Categorize Messages

264270 XCON: Exchange 2000 Server Queues Summary Display and Troubleshooting

What if the messages are stuck in the MSN SMTP connector?

Verify the event viewer log for Outlook Mobile Access Event Sync

60 Appendix B

Is there a deviceInfo XML file? If not you will see event ID 11312 in Event

Viewer.

Verify that the device is provisioned. The device scheduler should be set to “when new items arrive”. The deviceInfo XML is located in the following location: http://servername/exchange/user/NON_IPM_SUBTREE/Microsoft-Server-ActiveSync/AirNotifyDeviceInfo.xml

Are there WirelessOnSave bindings for the user? If not, verify that the device is provisioned. The device scheduler should be set to “when new items arrive”. Use Explorer, MDBVU or MFCMAPI to view the bindings.

Did the Event sink read the pickup directory correctly? If not, you will see event ID 11319 in Event Viewer. You will need to restart the Exchange Information Store.

Increase Diagnostic logging

Appendix B 61

To increase diagnostic logging, modify the value data of the following registry keys to 7 as seen above in the diagram.

Check for event ID 11321 to verify the on save events are firing.

If not, you may need to use the Binding Cleanup Tool to remove the user’s bindings and re-sync

Are notifications enabled globally? If not you will see event ID 10307

error. Enable up-to-date notifications globally in Exchange System Manager.

Is the user enabled for notifications? If not you will see event ID 10305 error. Enable the user for notifications in Active Directory Users and Computers

Verify events for OMACat

62 Appendix B

Are the notifications being dropped because of the expiry time? You may

see event ID 1030x errors. If so, it is an expected behavior. Check if the user’s device is configured properly (check peak times setting). Have them sync manually.

Has the administrator intentionally disallowed sending to the user’s SMTP device address? If yes, create SMTP carrier and inform the user to choose the “Corporate Carrier Connector” setting on the device address tab of the device.

Are notifications being dropped because the users

device miss configured? (You will see Error 10309)

Are notifications being dropped because user entered

an invalid SMTP address? (You will see Error 10304)

Yes

No

Are notifications being dropped with a function and

error code? (You will see Error 10303 if not)

No

Yes

Have the user correct the SMTP address and do a manual sync

Have the user do a manual sync

Have the user do a manual sync

No

Yes

Exchange PSS

Enable tracing. To enable tracing, use regtrace. Refer back to the section labeled “Regtrace” for information on using regtrace for up-to-date notifications troubleshooting.

Verify events for OMACat (continued)

What if the notifications are leaving the enterprise?

Appendix B 63

Can you send a SMTP message straight to Carrier

then to the device

Is the SMTP connector to MSN functioning

Yes

Mobile Operator issueNo

Yes

Exchange PSS MSN SOCEscalate

Exchange PSSNo

Confirm what is the method of sending? Directly to the user’s SMTP

device address or through MSN.

If they are sending directly to the device address, send a message from a mail client to the device address. If the device does not receive the message, the administrator will need to contact the mobile operator and work with them.

If they are sending through MSN, they still need to do the previous step. If they are able to send to the device address, you will need to escalate to MSN.

64 Appendix C

Appendix C

Possible Event Logs

Outlook Mobile Access Sink logging SINK_E_DATABASE

A database error occurred while processing the <> operation for the item URL <>.

SINK_E_DISALLOWED_FOLDER

The registration was denied because an event binding is being attempted on a disallowed folder.%n The URL for the item is <>.

SINK_E_NOT_INITIALIZED

The event sink failed to initialize.%n Previous error messages indicate the specific components that failed to initialize.

SINK_E_OUTOFMEMORY

The event sink was not able to allocate enough memory to complete the task. Please check system memory and try freeing up resources to correct the problem.%n

SINK_E_INVALIDITEMURLFORMAT

The item URL does not have the expected format. The URL which failed is <>%n

SINK_E_GETITEMROW

A database error occurred while trying to retrieve the row for this item.

SINK_E_GETEVENTSESSION

A database error occurred while trying to retrieve the session for this item.

SINK_E_INTERNALERROR

An internal error has occurred. Consult the debug trace log for more information.

SINK_E_INPROCREGFAILURE

An error occurred updating the registry for in-proc sink support. Consult the debug trace log for more information.

SINK_W_NODEVICEFILE

The device information file could not be retrieved from the user's mailbox.%n The URL for the item is <>.

SINK_W_UNREGFAILURE

An error occurred removing an item from the registry during component deregistration.

SINK_E_ADSOPENFAILED

11302

11303

11304

11305

11306

11307

11308

11309

11310

11312

11313

11314

Appendix C 65

The OMA Sink was unable to open up an object in the Active Directory.%n%n The object was <> and the error code returned was 0x<>%n%n You need to verify that the object exists in the Active Directory and that the OMA Sink has access to the object.

SINK_S_STARTUP

Event Source Started

SINK_S_SHUTDOWN

Event Source Stopped

SINK_E_BAD_MATCHSCOPE

Registration for item <> failed.%n An invalid MatchScope of "<>" was requested.

SINK_E_PICKUP_FAILURE

Event Source failed in attempt to lookup the pickup directory.

SINK_REGISTRATION_CREATED

A registration was successfully created on URL <>

SINK_ONSAVE_CALLED

OnSave event triggered for item with URL <>, flags <>.

SINK_DEVICEINFO_RETRIEVE

The device information file was successfully retrieved from the user's mailbox.%n The URL for the item is <>.

SINK_NOTIFICATION_SENT

11316

11317

11318

11319

11320

11321

11323

11324

66 Appendix C

Notification successfully written to the pickup directory for item <>

SINK_ITEM_IGNORED

Item <> was ignored. Item flag: <>

SINK_E_PERF_INIT_FAILED

Outlook Mobile Access Categorizer logging OMACAT_PERF_INIT_FAILED

OMACAT_EVENT_DEVICE_EXPIRY

OMA Categorizer has removed bindings for user <> FID <> due to the expiration of all devices subscribed to that folder.

OMACAT_EVENT_DISABLED_CLEANUP

OMA Categorizer has removed all bindings for user <> since the admin has disabled that user for always up to date synchronization

OMACAT_EVENT_INIT_FAILED

OMA Categorizer is unable to initialize. The initialization function returned error code <>

OMACAT_EVENT_INIT_SUCCESS

??

XXXX

??

??

??

10301

10302

Appendix C 67

OMA Categorizer successfully initialized.

OMACAT_EVENT_MESSAGE_DROPPED

OMA Categorizer dropped the message with message ID <>, Recipient <>. The function <> returned error code <>.

OMACAT_EVENT_USER_DISABLED

OMA Categorizer dropped the message with message ID <>, Recipient <>. The user is disabled for OMA Push.

OMACAT_EVENT_SMTP_DISABLED

OMA Categorizer dropped the message with message ID <>, Recipient <>. The global AdminWirelessFlag is disabled for SMTP addressing.

OMACAT_EVENT_GLOBAL_DISABLED

OMA Categorizer dropped the message with message ID <>, Recipient <>. The global AdminWirelessFlag is disabled for OMA Push.

OMACAT_EVENT_NOTIFY_EXPIRED

OMA Categorizer dropped the message with message ID <>, Recipient <>. The Device Notification expired.

OMACAT_EVENT_ILLEGAL_XML

10303

10305

10306

10307

10308

10309

68 Appendix C

OMA Categorizer dropped the message with message ID <>, Recipient <>. The XML received in the message body is illegal.

OMACAT_NOTIFICATION_DELIVERED

OMA Categorizer delivered an SMTP notification on behalf of <>

10310

Documents

W12 Up to Date Notification