XADM: Push Messages Generate NDR Shortly After You Configure a New Device (278450)
The information in this article applies to:
- Microsoft Mobile Information 2001 Server
- Microsoft Exchange 2000 Server
This article was previously published under Q278450 SYMPTOMS
When you are creating and provisioning a new device for a user, if a "Push" notification is sent immediately following this provisioning, the message may return the following non-delivery report (NDR):
Your message did not reach some or all of the intended recipients.
Subject: Message Subject
Sent: 01/1/2000 12:00 AM
The following recipient(s) could not be reached:
IMCEADAVNP-http+3A__WIRE2+2Ewirelesscorp+2Ecom_MMISNotify_Exchange2000EES_username_deviceid@DMI on 01/1/2000 12:00 AM
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.
<server.domain.com #5.2.0>
CAUSE
This behavior may occur because of replication latency when you are adding a device for a user. The device information, which is stored in Active Directory, must replicate to other Active Directory domain controllers for the message to be delivered successfully. If the Mobile Information Server attempts to locate the address of the device by querying a domain controller that has not yet received this information, the NDR is sent and the message is not delivered.
RESOLUTION
Allow Active Directory replication to occur before you attempt to send notification messages to the newly configured device. The amount of time this takes is dependent on the size and topology of your Active Directory.
Modification Type: | Minor | Last Reviewed: | 4/25/2005 |
---|
Keywords: | kbprb KB278450 |
---|
|