New local move request failed Exchange 2010

GarethABC
GarethABC used Ask the Experts™
on
Hi All

I get this error when trying a new local move request any ideas?
clicking on the help link tells me i have an error that doesnt have an article written about it!

Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:00:01


joe bloggs
Failed

Error:
Property expression "joe bloggs" 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.
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.140).aspx?v=14.2.247.1&t=exchgf1&e=ms.exch.err.ExD5AF6C

Exchange Management Shell command attempted:
'main.abc.local/ABC/Legal & Democratic Services/Users/joe bloggs' | New-MoveRequest -TargetDatabase 'MAILBOXDB 001'

Elapsed Time: 00:00:01
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
I think you are not entered mailbox name correctly. See examples:
http://technet.microsoft.com/en-us/library/dd351123.aspx
Commented:
simply use the AD Users and Computers on the Exchange 2003 Server to correct the error.

Right-Click on the user whose mailbox is displaying error - Go into properties and select "EXCHANGE GENERAL" tab - modify the "ALIAS"  -  click Apply.

You can use hyphen to bridge the space. After that all the mailboxes affected should move smoothly.
Commented:
abhiy is correct, but it took me a minute to realize that.

Spaces are not valid characters in email aliases in Exchange 2010, but the mailbox you're trying to move has a space in the alias. Remove that space from the alias name for that account/mailbox, and do the move again.

For what it's worth, the way I've done all my mailbox moves looks like this:

New-MoveRequest -Identity "alias" -BadItemLimit 40

Open in new window


BadItemLimit will allow the move request to skip n corrupt items during the move. Of course, those items are not moved, essentially lost, but they were corrupt anyway. If you find a mailbox that bumps up to that limit, the move request will fail. I think the max you can do with also using the -AcceptLargeDataLoss switch is 50.

Author

Commented:
thx all thats solved it :)

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial