Exchange Mailbox Moves: ‘FailedOther’ Stops at 95%

KB ID 0001376

Problem

If you don’t see this happen at least once in a migration I would be surprised!

  • StatusDetail: FailedOther
  • PercentComplete: 95%

 

Solution

 You can remove the move request and start it again, with both a BadItemLimit and AcceptLargeDataLoss flag, (these might seem scary, but I’ve migrated many thousands of mailboxes, and never seen a problem.)

But the mailbox is massive and it had been moving for hours! OK, we can change the parameters, and resume the move as well!

[box]

Option 1 (Remove and Restart the Move)

Remove-MoveRequest -Identity user-name

New-MoveRequest -Identity “user-name” -TargetDatabase “target-mailbox-database” -BatchName “user-name” -BadItemLimit “200” -AcceptLargeDataLoss

Option 2 (Resume Existing Mailbox Move)

Get-MoveRequest | ?{$_.DisplayName -eq “user-name“} | Set-MoveRequest -BadItemLimit 200 -AcceptLargeDataLoss

Get-MoveRequest | ?{$_.DisplayName -eq “user-name“} | Resume-MoveRequest

[/box]

The move should now restart/resume.

Related Articles, References, Credits, or External Links

NA

Exchange Mailbox Move Error”Property expression isn’t valid”

KB ID 0000238 

Problem

Seen when attempting to move a mailbox.

Error:
Property expression “username” isn’t valid. Valid values are: Strings that include ‘@’ where ‘@’ cannot be the last character

During the move.

When the move process has finished.

Note: If your error says

Property expression “username” isn’t valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.” Then click here.

Solution

This is caused because for that particular user there is no entry in the “domain” attribute on the user object.

1. Log onto a domain controller.

2. Start > Administrative tools> Active Directory Users and Computers.

3. Locate the user > Right click > Properties > Account Tab.

4. Put the domain name in the domain section. (use the drop down).

5. Now when you try and move the mailbox you will see this error instead.

Error:
The queue in ‘Mailbox Database xxxxxxxx’ database already contains a move request for {username}. While AD reports the mailbox as not being moved. It is possible that someone created the move request recently……..{text removed}…If you believe this to be an abandoned move request you can remove it by running ‘Remove-Move-Request -MoveRequestQueue ‘Mailbox Database xxxxxxx -MailboxGuid xxxxx-xxxxx-xxxxx-xx-xxx

6. Press CTRL+C to copy all that to the clipboard.

7. Open Notepad > Press CTRL+V to paste the text in.

8. Locate the command its asking you to run.

9. Launch the Exchange Management Shell > Paste in the command.

10. Now when you try and move the mailbox it should be OK.

 

Related Articles, References, Credits, or External Links

NA

Exchange 2010 Mailbox Move Error “Property expression isn’t valid”

KB ID 0000430 

Problem

Seen while trying to execute a move mailbox move.

Error:
Property expression “username” isn’t valid. Valid values are: Strings formed with characters from A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~. One or more periods may be embedded in an alias, but each period should be preceded and followed by at least one of the other characters. Unicode characters from U+00A1 to U+00FF are also valid in an alias, but they will be mapped to a best-fit US-ASCII string in the e-mail address, which is generated from such an alias.

Note: If your error says..

“Property expression “username” isn’t valid. Valid values are: Strings that include ‘@’ where ‘@’ cannot be the last character” click here

Solution

1. On the Exchange server, launch the Exchange Management Console > Below Recipient Configuration > Mailbox, locate the user/mailbox that you have a problem with > Right click > Properties.

2. On the General tab > Locate the users “Alias” > delete anything that isn’t A to Z (uppercase or lowercase), digits from 0 to 9, !, #, $, %, &, ‘, *, +, -, /, =, ?, ^, _, `, {, |, } or ~

3. Once you have changed > Apply > Try and move the mailbox again (Note: You may need to delete the move request, in the “Move Request” section.)

 

Related Articles, References, Credits, or External Links

NA

Mailbox Move Error – ‘Couldn’t switch the mailbox into Sync Source mode’

KB ID 0000795 

Problem

While attempting to move a mailbox between sites last week I got this;

Error details: Couldn't switch the mailbox into Sync Source mode.
This could be because of one of the following reasons:
Another administrator is currently moving the mailbox.
The mailbox is locked.
The Microsoft Exchange Mailbox Replication service (MRS) doesn't have the correct 
permissions. Network errors are preventing MRS from cleanly closing its session 
with the Mailbox server. If this is the case, MRS may continue to encounter this 
error for up to 2 hours - this duration is controlled by the TCP KeepAlive settings 
on the Mailbox server. Wait for the mailbox to be released before attempting to move 
this mailbox again.

Solution

I knew no one else was attempting to move it, and I had full exchange permissions.

In my case the two sites with Exchange were joined together with a site to site VPN, the error message was giving me a hint (though a cryptic one) with the ‘Network errors are preventing MRS‘ comment. What I needed to do was increase the ‘Keep Alive’ time for it to complete.

Note: I increased the keep alive time to 1 hour, most posts I’ve seen recommend 5 minutes, it’s up to you, I was running my mailbox moves overnight and I didn’t want to walk back into carnage. Just REMEMBER to DELETE the registry entry when the mailbox moves are compete!

1. Before you can attempt to move the mailbox again you need to remove the move request, either graphically (Exchange 2007/2010) from the Exchange Management console > Recipient Configuration > Move Request > Locate and delete the move request, or from PowerShell;

[box]
Remove-MoveRequest {Username}
[/box]

2. On the source mailbox server, Start > Run > Regedit > Navigate to the following registry key;

[box]
HKEY_Local_Machine > System > CurrentControlSet > Services > Tcpip > Parameters[/box]

Create (or edit if it’s already there) a 32 bit DWORD value.

3. Call the value KeepAliveTime and set it’s value to 3600000 (Note in milliseconds that’s 1 hour), if that’s to rich for you use 900000 (15 minutes).

4. Repeat the process on the destination mailbox server (and any hub transfer servers that will be in the ‘path’ of the mailbox move).

5. Don’t forget to remove these changes when you are finished.

 

Related Articles, References, Credits, or External Links

NA

Mailbox Move ‘Stuck’ Queued

KB ID 0001094 

Problem

When doing a migration I usually create a test account and move that to the new server. Then I can mail flow both from old to new server and to/from external addresses from both old and new servers. So when the mailbox just sat ‘Queued’ for a while I was starting to get concerned.

Even applying the Exchange ‘cup of coffee’ rule didn’t make a difference.

Solution

Nice simple one to fix. Windows Key+R > services.msc {enter}. Locate and restart the Microsoft Exchange Mailbox Replication service.

Now refresh the move request and it will either have moved (or be moving).

Related Articles, References, Credits, or External Links

NA