antwerp2007
asked on
problems with moving legacy mailboxes to new exchange 2010 server
Hello,
having dificulties to move (local move request) legacy mailboxes from exchange 2003 to brand new exchange 2010 server during migration.
I was only able to move the administrator mailbox from the old exchange 2003 server to the new exchange server after modification; adding administrator (domain admin) account on the manage full access permissions from the mailbox.
When trying to move other user mailboxes i recieve the error
Failed to communicate with the mailbox database.
MapiExceptionUnknownuser: Unable to open message store
or
MapiExceptionFailed: unable to communicate with the server
0x80004005
changing permissions does not work for other mailboxes.
need to solve this asap.
thank you
having dificulties to move (local move request) legacy mailboxes from exchange 2003 to brand new exchange 2010 server during migration.
I was only able to move the administrator mailbox from the old exchange 2003 server to the new exchange server after modification; adding administrator (domain admin) account on the manage full access permissions from the mailbox.
When trying to move other user mailboxes i recieve the error
Failed to communicate with the mailbox database.
MapiExceptionUnknownuser: Unable to open message store
or
MapiExceptionFailed: unable to communicate with the server
0x80004005
changing permissions does not work for other mailboxes.
need to solve this asap.
thank you
ASKER
Thank you for the respons , i ' ll gather asap the information and post it
ASKER
Hi Amitkulshrestra,
I just logged on again on the new exchange 2010 and while verifying the event logs, i noticed that meanwhile there was some kind of update actions from Process MSEXCHANGEADTOPOLOGYSERVIC E.EXE ...
So i tested again and it the move relpication seems to start now.
Let you know the results asap
I just logged on again on the new exchange 2010 and while verifying the event logs, i noticed that meanwhile there was some kind of update actions from Process MSEXCHANGEADTOPOLOGYSERVIC
So i tested again and it the move relpication seems to start now.
Let you know the results asap
That is good...I assume might be it took some time for the rights to replicate and applied at Exchange level...If move is successful test it for another one. If everything is working, then disable the logging as it creates load on the server.
ASKER
Oops, i'll retry with skipping a number of corrupt mails;
Lid: 31418 --- ROP Parse Done ---
Lid: 16465
Lid: 24657 StoreEc: 0x8004011B</errorMessage>
<errorContext>--------
Operation: LocalSourceFolder.CopyBatc h
EntryIDs: [[len=70, data=00000000A91830FCE9C7C A4A9E35A9E 16872F0FC0 7009C3193D 91F55E44CA 5875868DAA 98AD700000 0001C65000 09C3193D91 F55E44CA58 75868DAA98 AD7000001B 7DAFB0000] ]
--------
Folder: entryId [len=46, data=00000000A91830FCE9C7C A4A9E35A9E 16872F0FC0 1009C3193D 91F55E44CA 5875868DAA 98AD700000 0001C65000 0]
--------
Operation: ISourceMailbox.ExportMessa ges
OperationSide: Source
Primary (3ed5925f-6ea1-467e-8d55-e ff69d59f0b c)
Flags: None
PropTags: (null)</errorContext>
</baditem>
2/03/2011 19:54:01 [AABTS-EXCHANGE] Stage: CopyingMessages. Percent complete: 56.
2/03/2011 19:54:01 [AABTS-EXCHANGE] Copy progress: 5434/16011 messages, 525.1 MB (550,571,128 bytes)/1.133 GB (1,216,156,421 bytes).
2/03/2011 19:54:01 [AABTS-EXCHANGE] Fatal error TooManyBadItemsPermanentEx ception has occurred.
Error details: This mailbox exceeded the maximum number of corrupted items that were specified for this move request.
at Microsoft.Exchange.Mailbox Replicatio nService.B aseJob.Rep ortBadItem s(MailboxC opierBase mbxCtx, List`1 badItems)
at Microsoft.Exchange.Mailbox Replicatio nService.M ailboxCopi erBase.Cop yMessageBa tch(List`1 batch, MailboxChanges mailboxChanges, Int32& numberOfUpdates)
at Microsoft.Exchange.Mailbox Replicatio nService.M ailboxCopi erBase.Cop yMessages( List`1 batch)
at Microsoft.Exchange.Mailbox Replicatio nService.M oveBaseJob .WriteMess ages(Objec t[] wiParams)
at Microsoft.Exchange.Mailbox Replicatio nService.C ommonUtils .CatchKnow nException s(GenericC allDelegat e del, FailureDelegate failureDelegate)
Error context:
2/03/2011 19:54:01 [AABTS-EXCHANGE] Relinquishing job.
Lid: 31418 --- ROP Parse Done ---
Lid: 16465
Lid: 24657 StoreEc: 0x8004011B</errorMessage>
<errorContext>--------
Operation: LocalSourceFolder.CopyBatc
EntryIDs: [[len=70, data=00000000A91830FCE9C7C
--------
Folder: entryId [len=46, data=00000000A91830FCE9C7C
--------
Operation: ISourceMailbox.ExportMessa
OperationSide: Source
Primary (3ed5925f-6ea1-467e-8d55-e
Flags: None
PropTags: (null)</errorContext>
</baditem>
2/03/2011 19:54:01 [AABTS-EXCHANGE] Stage: CopyingMessages. Percent complete: 56.
2/03/2011 19:54:01 [AABTS-EXCHANGE] Copy progress: 5434/16011 messages, 525.1 MB (550,571,128 bytes)/1.133 GB (1,216,156,421 bytes).
2/03/2011 19:54:01 [AABTS-EXCHANGE] Fatal error TooManyBadItemsPermanentEx
Error details: This mailbox exceeded the maximum number of corrupted items that were specified for this move request.
at Microsoft.Exchange.Mailbox
at Microsoft.Exchange.Mailbox
at Microsoft.Exchange.Mailbox
at Microsoft.Exchange.Mailbox
at Microsoft.Exchange.Mailbox
Error context:
2/03/2011 19:54:01 [AABTS-EXCHANGE] Relinquishing job.
Corrupt mail is one of the know issue for mailbox move failure...do check, if you have setup any rules...remove them also.
ASKER
OK, i check for any rules,used the following comand as test ;
New-MoveRequest -Identity 'username' -TargetDatabase "Mailbox Database Name" -BadItemLimit 100 -AcceptLargeDataLoss
New-MoveRequest -Identity 'username' -TargetDatabase "Mailbox Database Name" -BadItemLimit 100 -AcceptLargeDataLoss
ASKER
First mailbox moved succesfully
Thanks for the update...Try more, if you need any further help...let me know...will be checking tomorrow...
ASKER
Great!Thank you for the help/info.
Will let you know the progress...
Will let you know the progress...
ASKER
Hi Amitkulshrestra,
mailboxes are moving well today,and i started the public folder replication...
there are still some instances that need to be replicated,is there any way to increase this?
mailboxes are moving well today,and i started the public folder replication...
there are still some instances that need to be replicated,is there any way to increase this?
ASKER
i also got 1 message and state failed property expression isnt valid on a mailbox.
will investigate how to correct it.
will investigate how to correct it.
Let Public folder replication finish by its own. It can take long time to finish. So once PF replication is finish, then point DB to new PF DB and leave Old DB up for some more time. Later Start removing the replica and leave it for a week more...Then shutdown the server and check if users are reporting any issue.
If no issue reported by user. Uninstall the server. PF move is a time consuming task...I normally give a month
If no issue reported by user. Uninstall the server. PF move is a time consuming task...I normally give a month
failed property expression isnt valid ?
Can you paste the screenshot for that error
Can you paste the screenshot for that error
ASKER
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you again for the great help, i will investigate the information.
I think that GFI Mail essentials is preventing the public folder replication... will try to sync again when stopping the GFI services temporary.
I think that GFI Mail essentials is preventing the public folder replication... will try to sync again when stopping the GFI services temporary.
ASKER
Hi Amitkulshrestra,
Changing the alias on SBS 2003 solved the issue for me, the last mailbox is moved.
I also uninstalled Mcafee Groupshield for exchange and GFI antispam to improve the replication progress from the public folders.
It was a good thing,most of the foldrs were moved.only 4 MB remains now but it didn't change for the past 10 hours.Reapplying the "Move all Replicas" instruction does not help.
I am thinking to export the remaining PF' to PST now
Changing the alias on SBS 2003 solved the issue for me, the last mailbox is moved.
I also uninstalled Mcafee Groupshield for exchange and GFI antispam to improve the replication progress from the public folders.
It was a good thing,most of the foldrs were moved.only 4 MB remains now but it didn't change for the past 10 hours.Reapplying the "Move all Replicas" instruction does not help.
I am thinking to export the remaining PF' to PST now
Thanks for the update. Its good to see lot of things worked for you. For 4 MB data, moving to PST and dumping back to new server will be good. Please goahead, if you face any further issue, let me know. So we can troubleshoot further
Thanks
Amit
Thanks
Amit
ASKER
All public folders are replicated now!
I am experiencing that a few external recipients are not receiving email anymore?
tried to enable logging on the SmallBusiness SMTP connector that was default created on the Ex2010 but it is not possible,greyed out.So i created a new smtp connector now and tried to disable the default one but got an error
(error -------------------------- ---------- ---------- ----------
Microsoft Exchange Error
-------------------------- ---------- ---------- ----------
Action 'Disable' could not be performed on object 'SmallBusiness SMTP connector'.
SmallBusiness SMTP connector
Failed
Error:
Property Enabled can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).
I am experiencing that a few external recipients are not receiving email anymore?
tried to enable logging on the SmallBusiness SMTP connector that was default created on the Ex2010 but it is not possible,greyed out.So i created a new smtp connector now and tried to disable the default one but got an error
(error --------------------------
Microsoft Exchange Error
--------------------------
Action 'Disable' could not be performed on object 'SmallBusiness SMTP connector'.
SmallBusiness SMTP connector
Failed
Error:
Property Enabled can't be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. The object's current version is 0.0 (6.5.6500.0).
What is the error you are getting when sending emails. Run it as Administrator.
ASKER
it is very strange , it think every email is relayed well (without any error) but in some other countries the email is sometimes not received on the destination?
i asked to check their spam and junk foldres also
i asked to check their spam and junk foldres also
ASKER
If you want i create another question for this issue
So we can close this one?
Thank you for assisting me!
So we can close this one?
Thank you for assisting me!
Ya that will be good...If you can post another ticket for other issue...will be assisting you again.
ASKER
OK, Thanks again!
First we need to find out where it is failing. For that you need to enable the diagnostic logging and set it to high.
How to do it?
http://technet.microsoft.com/en-us/library/dd335139.aspx
Then again try to move the mailbox and if it fails, check application logs. You will find where it is failing. If you are unable to determine the cause, export the application logs and post it here.
Add that ID, which you are using for mailbox move toExchange Admin group.
Apart from above, there are more troubleshooting steps.
http://technet.microsoft.com/en-us/library/dd638094.aspx
Try again with logging enabled.