[ngw] stuck user move
Holly.Newman at KJMAIL.COM
Tue Apr 13 20:35:30 UTC 2010
There were no options to do anything in User Move Status - all the buttons were grayed out. I'll try the other stuff - thanks!
>>> "Tom Miller" <TMiller at hnncsb.org> 4/13/2010 1:32 PM >>>
You can try to reforce and/or restart the move via User Move Status. If not:
I'd try to move the user back, then top down primary domain --> domain --> post office rebuild. I've had some moves fail in the past and that worked for me.
If it fails again I'd put the mail into an archive, export address book, delete user, recreate on new post office, import address book, change fid with fid editor and bring in mail (don't forget sent items).
>>> "Holly Newman" <Holly.Newman at KJMAIL.COM> 4/13/2010 3:55 PM >>>
It's been so long since I've had a user move go bad I've completely forgotten how to deal with them.
Here's the status:
Standalone GWCheck before move was clean
Both POs are in the same domain
I was connected to that domain
1. Got a message from the Directory Services Agent on the domain
WARNING: The Administration Agent (ADA) at domain USERD reported an error during a Directory Service update.
Operation: Rename object in Post Office database Return Code: D109 Task ID: 4204
Object ID: USERD.AVIP.NChaiyav
SUGGESTION: Execute the Administration program at domain USERD and synchronize the above object.
2. Checked the User Move Status and found a D109 Invalid Parameter
The domain thinks the user is in the new post office
There is no User DB in the new post office
No activity on the POAs
What now? Is this one of the simple ones where I can just move the object back and start over?
Confidentiality Notice: This e-mail message, including attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ngw