Incorrect Push Binding May Be Created When You Use the Personal Device Setup Tool with the Airweb Page (315065)

SYMPTOMS

When you use the Personal Device Setup tool with the Mobile Information Server Preferencing page (Airweb) to create a device and to enable push notifications, an incorrect setting may be created on the push notification binding. You may receive the following non-delivery report (NDR):

IMCEADAVNP-http+3A__MMISNotify_Exchange2000EES_user1_5551239876@mobileinformationserver on 12/1/2001 1:05 PM

The message reached the recipient's e-mail system, but delivery was refused. Attempt to resend the message. If it still fails, contact your system administrator.
<mis-server.corp.nwtraders.com #5.2.0>

CAUSE

This issue can occur if you use the Personal Device Setup tool to delete a device, and then re-create the device using the same device name but a different device ID while the Airweb page is open in another browser window. When you do so, the binding is created with the previous device ID that is cached by the Web browser. When you enable push notifications, the new device ID is not retrieved from Active Directory, and the previous ID is used to create the bindings. If this device ID no longer exists, when you enable push notifications, you receive the NDR that is described in the "Symptoms" section of this article.

RESOLUTION

To resolve this issue, before you enable push notifications, close and reopen the Airweb page after you create a new device.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.