Tag Archives: “ActiveSync Issues”

Microsoft Exchange Server 2010 Service Pack 2 – Update Rollup 2

Microsoft have released Update Rollup 2 for Exchange Server 2010 Service Pack 2 which resolves many issues that have been reported since the initial release of Exchange 2010 Service Pack 2

Summary of Fixes:

http://support.microsoft.com/kb/2519806 – A meeting request that is sent by an external user or by using a non-Microsoft email system is stamped as Busy instead of Tentative in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2556766 – Slow performance when you create many contacts by using Exchange Web Services in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2592398 – Email messages in the Sent Items folder have the same PR_INTERNET_MESSAGE_ID property in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2601301 – Customized contact objects revert to the default form after a public folder database replication in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2630808 – A user can log on to a mailbox by using Outlook for Mac 2011 unexpectedly in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2632201 – MAPI_E_INVALID_PARAMETER errors occur when a MAPI application receives notifications in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2635223 – A hidden user is still displayed in the Organization information of Address Book in OWA in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2636387 – Event ID 3022 is logged and you cannot replicate a public folder from one Exchange Server 2010 server to another

http://support.microsoft.com/kb/2636883 – Returned message items can disappear from the search results view when you use Outlook in online mode in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2641249 – Error message when you use the “Folder.Bind” method in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2641753 – An email message from an Exchange Server 2003 user is forwarded incorrectly to an external recipient of an Exchange Server 2010 user mailbox

http://support.microsoft.com/kb/2644144 – A read receipt is not sent when a receiver does not expand a conversation to preview the message by using OWA in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2644920 – The Get-FederatedDomainProof cmdlet fails in an Exchange Server 2010 SP1 environment

http://support.microsoft.com/kb/2645587 – An external email message is not delivered to mail-enabled public folders and you do not receive NDR messages in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2649499 – Updates for a meeting request are sent to all attendees directly in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2649679 – Text in tables is displayed incorrectly in the Conversation view in Outlook Web App in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2652730 – You encounter failures when you run the Test-EcpConnectivity cmdlet to test Exchange Control Panel connectivity in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2657103 – CPU resources are used up when you use the Set-MailboxMessageConfiguration cmdlet in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2660178 – “More than one mailbox has the same e-mail address” error message when you try to manage a mailbox in a tenant organization in an Exchange Server 2010 SP1 Hosting mode environment

http://support.microsoft.com/kb/2661277 – An ActiveSync user cannot access a mailbox in an Exchange Server 2010 forest

http://support.microsoft.com/kb/2661294 – An email address policy does not generate the email addresses of recipients correctly in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2663581 – OK button is not displayed when you change your password in Outlook Web App by using Firefox in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2664365 – Certain MailboxStatistics properties are not updated when a user uses a POP3 or IMAP4 client to access a mailbox in an Exchange 2010 environment

http://support.microsoft.com/kb/2664761 – DPM protection agent service may stop responding on Exchange Server 2010 servers that are protected by System Center DPM 2010

http://support.microsoft.com/kb/2665806 – Error message when you open an RTF email message that has inline attachments in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2673087 – Error message when you try to copy the Inbox folder to another folder in Outlook in online mode in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2677847 – The Microsoft Exchange File Distribution service consumes large amounts of memory in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2678361 – The user-agent information about an Exchange ActiveSync device is not updated in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2678414 – The display name of a contact in address book is empty in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2681464 – An EWS application crashes when it calls the GetStreamingEvents operation in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2685996 – Error message when a user who does not have a mailbox tries to move or delete an item that is in a shared mailbox by using Outlook Web App Premium

http://support.microsoft.com/kb/2688667 – W3wp.exe consumes excessive CPU resources on Exchange Server 2010 Client Access servers when users open recurring calendar items in mailboxes by using Outlook Web App or EWS

http://support.microsoft.com/kb/2693078 – EdgeTransport.exe process crashes in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2694280 – Whatif switch does not work in the Set-MoveRequest or Resume-MoveRequest cmdlet in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2694289 – Resource mailbox does not forward meeting request to delegates after one of the delegates’ mailbox is disabled in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2694414 – The update tracking information option does not work in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2694473 – File name of a saved attachment is incorrect when you use OWA in Firefox 8 in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2694474 – Incorrect delivery report when you send an email message to a recipient who has configured an external forwarding address in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2696857 – EdgeTransport.exe process crashes without sending an NDR message when you send a message to a distribution group in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2696905 – Day of the week is not localized in MailTips in Outlook Web App in an Exchange Server 2010 environment

http://support.microsoft.com/kb/2696913 – You cannot log on to Outlook Web App when a proxy is set up in an Exchange Server 2010 environment

[RESOLVED] – Microsoft Exchange 2010 – Appointments exceeding 24 hours changed to multiple day All Day Event on Mobile Phones/Devices

Microsoft Exchange 2010 Service Pack 1 ActiveSync does seem to have issues with Appointments exceeding 24 hours that are not all day events (i.e. Friday to Sunday).  I have personally seen this issue with the iPhone 4 and 3GS, both were upgraded to IOS5 which did not resolve the issue.  The latest update “Microsoft Exchange 2010 Service Pack 1 – Hotfix Rollup 6” also does not seem to resolve this problem.

You might wish to test if you have the issue with your ActiveSync enabled Smart Phone or Device, you should be able to replicate the issue by asking a collegue to send you a meeting invite that starts on Friday at 4pm and then finishes on Sunday at 2pm, Once you accept the invite you will find that it has been changed to several all day events (Fri, Sat and Sun) rather than an appointment between the specified time period.

After a long wait it appears that this issue is resolved in Rollup 1 for Exchange Server 2010 – Service Pack 2, you can obtain the Rollup using the link below:

http://www.microsoft.com/download/en/details.aspx?id=28809 – Update Rollup 1 for Exchange Server 2010 Service Pack 2 (KB2645995)

You can see the overall list of fixes/changes in Rollup 1 here:

http://support.microsoft.com/?kbid=2645995

The Fix we are most interested in is “A meeting item displays incorrectly as multiple all-day events when you synchronize a mobile device on an Exchange Server 2010 mailbox”

This was original raised in: http://support.microsoft.com/kb/2549255

You will need to ensure that you have updated your Microsoft Exchange 2010 Server to Service Pack 2 before you can install the Rollup so remember to factor extra time in for this.

You can obtain Microsoft Exchange Server 2010 – Service Pack 2 from here: http://www.microsoft.com/download/en/details.aspx?id=28190

Microsoft do seem to be aware of the issue and mention it in this Knowledgebase article

http://support.microsoft.com/kb/2563324 Current issues with Microsoft Exchange ActiveSync and Third Party Devices

Issue 1.6 – Appointment exceeding 24 hours changed to multiple day All Day Event
When an appointment item’s duration exceeds 24 hours, but is not marked as an All Day Event, Exchange ActiveSync changes the item on the device to become a multi-day All Day Event. The next time that the device synchronizes with the mailbox, the change is propagated from the item on the device to the item on the Exchange Server 2010 mailbox.

Solution
Microsoft is investigating this issue. This problem can occur when using any ActiveSync device synchronizing with Exchange Server 2010.

As you can see Microsoft do not currently have a solution to the problem and may well need to contact Apple and/or Google to produce a fix for both the iPhone and Android based handsets.

I would recommend contacting Microsoft Product Support and your mobile phone manufacturer if this issue is affecting you.  The more users that log the issue the higher priority it will be given and the quicker we can expect to see a fix emerge.