We are down to about 12% free space on our database LUN on our only MBX role server, so I created another db on another LUN and moved about a 100+ mailboxes over the weekend. When I came back into the office this morning, I noticed it hadn't freed up
the old space, and after further research I see that it won't recover that free space without an offline defrag. That's disappointing but glad we caught it now.
There were also about 70 mailboxes which reported this error:
Warning: Failed to clean up the source mailbox after the move.
Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)
The move request log begins with this, note the two different build numbers reported on the last two lines:
8/9/2014 4:52:40 AM [fl2000-excas002] The Microsoft Exchange Mailbox Replication service 'fl2000-excas002.domain.com' (14.3.178.0 caps:07) is examining the request.
8/9/2014 4:52:40 AM [fl2000-excas002] Connected to target mailbox 'Primary (da6554b0-4202-4217-89d8-502fb9ae5a49)', database 'Concord3', Mailbox server 'FL2000-EXMBX001.domain.com' Version 14.3 (Build 123.0).
8/9/2014 4:52:40 AM [fl2000-excas002] Connected to source mailbox 'Primary (da6554b0-4202-4217-89d8-502fb9ae5a49)', database 'Concord Database', Mailbox server 'FL2000-EXMBX001.domain.com' Version 14.3 (Build 181.0).
What would cause the log to reference two different builds for each of the databases? I upgraded our version to SP3UR6 last week (prior to creating the new mailbox db named 'Concord3'), but on the mailbox server the Information Store service never finished
stopping during the install, and the install seemed to work past it, and then the Information Store was still in the stopping state when the installer was attempting to restart the IS. I waited about a half hour and then rebooted the MBX and things seemed
to be working and I haven't thought about it again until I noticed these messages. Could it be related? Either way, should I be concerned and if yes, what do you recommend?
Thanks,
Jim