Outlook disconnects during a move. Event ID 9660 in App log even after applying update rollup 1 to SP3

Not sure if this is normal or not. I don't think so. Haven't done mailbox moves in a while on Exchange. Using Exchange 2010 SP3 with Update Rollup 1. I had to apply rollup 1 to address a problem with mailbox moves outlined in this article: http://support.microsoft.com/kb/2763065.

The update addressed part of the issue but the server still logs event ID 9660 in the Application log which I have never seen before.
The bigger issue is I noticed Outlook goes into a disconnected state while the mailbox is being moved. This is not supposed to happen as far as I can remember. I have been told this is normal at the end of the move when it does it final cleanup but I don't think so.

 This means you really can't move a mailbox during the day without affecting the user.
 I don't remember any of these issues prior to SP2. Is anyone else experiencing this issue?

Like I said, we are running Exchange 2010 SP3 UR1 on Windows 2008 R2 SP1. Two CAS servers in a CAS array. Two MB servers in a DAG. Just moving a mailbox from one DB to another when both DB's are mounted on the same server produces the problem. During the move, the workstation (XP SP3) can successfully ping the CAS Array so that is not the issue. After the move, the client reconnects and all is well. I was always able to move mailboxes while the user was online and never had any issues.

I have two environments. Test and Prod. It happens in both. Both environments are at the same levels in terms of SP's etc.....I looked at the Log tab on the mailbox in the Move Request folder in EMC and everything looks fine. No issues or errors. UR1 fixed the cleanup issue. It still puts a ton of event ID 9660 warnings in the application log and I think this may have something to do with it. Any help on this would be appreciated.
Who is Participating?
shadowtuckAuthor Commented:
The answer is here. Apparently this is normal at the 95% mark.


Outlook will reconnect when the move is complete without closing and reopening.

In my test, CAS connectivity is always maintained. Outlook disconnects at the 95% mark of the move and prompts for credentials if you have OA enabled. Makes sense as it falls back to HTTP if MAPI fails. If you are not using OA in your environment no prompt will occur and Outlook will reconnect on its own when the move is complete.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
We have SP3 in our Lab environment but havent seen this issue ... not sure if its with RU1 for SP3

- Rancy
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Possible Bug with Exchange 2010, SP3, RU1

I would say worth calling MS and checking if they are haring of such issues

Released: Update Rollup 1 for Exchange Server 2010 SP3

- Rancy
shadowtuckAuthor Commented:
I have been told or at least read that the disconnect will happen right around the 95-99% completion percentage when it does final cleanup. This may be true and its fast enough where users don't notice. I need to do more testing to find out when it happens.

There was definitely an issue with the mailbox move before RU1. That is well documented and made the disconnect seem longer because the final cleanup would take an extra 3 minutes as it failed 6 times with 30 second intervals. After RU1, the mailbox move problems went away although it does log a significant amount of 9660 warnings in the Application log. This I believe is a bug also. The disconnect was my main concern. I'll try it again and be more specific as to the amount of time its disconnected and when it occurs.
shadowtuckAuthor Commented:
Found answer on my own in article online
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.