Move MailBox Issue at Exchange 2010


When i move this user mailbox from db1 to db4 which encountered this error:

Property expression ‘user1’ isn’t valid values are: Strings that includes @, cannot be the last character


1. Checked user at AD and confirmed no space and invalid character
2. Checked ADSI Edit > OU=OP > OU=Mail > CN=user1 no invlid character
3. Checked user can login to the outlook and OWA without any issue like file corruption

How to troubleshooting and can move user mailbox without this issue.

If need to run powershell, can i understand where to run it and what will be the easy command for me that never used powershell. Run In exchange 2010 or PC with Powershell login with import-module.  


Lucky ThamFreelancerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jason CrawfordTransport NinjaCommented:
What is the value of the mailbox's userPrincipalName?  Try exporting all AD attributes to see if you can find the culprit:

Get-ADUser <sAMAccountName> -Properties *

Open in new window

Lucky ThamFreelancerAuthor Commented:

Get-ADUser <sAMAccountName> -Properties *
At line:1 char:12
+ Get-ADUser <sAMAccountName> -Properties *
+            ~
The '<' operator is reserved for future use.
    + CategoryInfo          : ParserError: (:) [], ParentContainsErrorRecordEx
    + FullyQualifiedErrorId : RedirectionNotSupported

 Get-ADUser <sAMAccountName> -Properties *
Use the User1 name <SamaccountName> filed as suggested by Jason.

Get-ADUser <sAMAccountName> -Properties *

For Example for user1

Get-ADUser user1 -Properties
Hasin Ahmed ChoudharyExchange AdministratorCommented:
Check the UPN value of that mailbox from ADUC.  If it is blank then above error is obvious.
Jason CrawfordTransport NinjaCommented:
I apologize I should have been more clear.  Please remove the <> from the sAMAccountName value when running the Get-ADUser cmdlet.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.