Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5567
  • Last Modified:

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






0
antwerp2007
Asked:
antwerp2007
  • 15
  • 10
1 Solution
 
AmitIT ArchitectCommented:
Hi Antwerp2007,

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.
0
 
antwerp2007Author Commented:
Thank you for the respons , i ' ll gather asap the information and post it
0
 
antwerp2007Author Commented:
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 MSEXCHANGEADTOPOLOGYSERVICE.EXE ...
So i tested again and it the move relpication seems to start now.
Let you know the results asap
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
AmitIT ArchitectCommented:
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.
0
 
antwerp2007Author Commented:
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.CopyBatch
EntryIDs: [[len=70, data=00000000A91830FCE9C7CA4A9E35A9E16872F0FC07009C3193D91F55E44CA5875868DAA98AD7000000001C6500009C3193D91F55E44CA5875868DAA98AD7000001B7DAFB0000]]
--------
Folder: entryId [len=46, data=00000000A91830FCE9C7CA4A9E35A9E16872F0FC01009C3193D91F55E44CA5875868DAA98AD7000000001C650000]
--------
Operation: ISourceMailbox.ExportMessages
OperationSide: Source
Primary (3ed5925f-6ea1-467e-8d55-eff69d59f0bc)
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 TooManyBadItemsPermanentException has occurred.
Error details: This mailbox exceeded the maximum number of corrupted items that were specified for this move request.
   at Microsoft.Exchange.MailboxReplicationService.BaseJob.ReportBadItems(MailboxCopierBase mbxCtx, List`1 badItems)
   at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.CopyMessageBatch(List`1 batch, MailboxChanges mailboxChanges, Int32& numberOfUpdates)
   at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.CopyMessages(List`1 batch)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.WriteMessages(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context:
2/03/2011 19:54:01 [AABTS-EXCHANGE] Relinquishing job.
0
 
AmitIT ArchitectCommented:
Corrupt mail is one of the know issue for mailbox move failure...do check, if you have setup any rules...remove them also.
0
 
antwerp2007Author Commented:
OK, i check for any rules,used the following comand as test ;

New-MoveRequest -Identity 'username'  -TargetDatabase "Mailbox Database Name" -BadItemLimit 100 -AcceptLargeDataLoss
0
 
antwerp2007Author Commented:
First mailbox moved succesfully
0
 
AmitIT ArchitectCommented:
Thanks for the update...Try more, if you need any further help...let me know...will be checking tomorrow...
0
 
antwerp2007Author Commented:
Great!Thank you for the  help/info.
Will let you know the progress...
0
 
antwerp2007Author Commented:
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?
0
 
antwerp2007Author Commented:
i also got 1 message  and state failed property expression isnt valid on a mailbox.
will investigate how to correct it.
0
 
AmitIT ArchitectCommented:
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
0
 
AmitIT ArchitectCommented:
failed property expression isnt valid ?

Can you paste the screenshot for that error
0
 
antwerp2007Author Commented:
Sorry for long waiting.
I added the image from th message

Error-Move-mailbox.JPG
0
 
AmitIT ArchitectCommented:
Hi antwerp2007

Hope you are doing well. Secondly thanks for posting the screenshot. It looks like Alias name issue. Below is an article which discuss about it.

http://social.technet.microsoft.com/Forums/en-US/exchange2010/thread/ba4c922e-123f-4de5-a8d3-855ae128587d/

Another article tells how to fix it
http://www.petenetlive.com/KB/Article/0000238.htm

Hope this fix your issue.
0
 
antwerp2007Author Commented:
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.
0
 
antwerp2007Author Commented:
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
0
 
AmitIT ArchitectCommented:
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
0
 
antwerp2007Author Commented:
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).


0
 
AmitIT ArchitectCommented:
What is the error you are getting when sending emails. Run it as Administrator.
0
 
antwerp2007Author Commented:
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
0
 
antwerp2007Author Commented:
If you want i create another question for this issue
So we can close this one?
Thank you for assisting me!
0
 
AmitIT ArchitectCommented:
Ya that will be good...If you can post another ticket for other issue...will be assisting you again.
0
 
antwerp2007Author Commented:
OK, Thanks again!
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 15
  • 10
Tackle projects and never again get stuck behind a technical roadblock.
Join Now