Exchange 2007 hub transport MAPIdelivery queued

Hi,
I just encountered problem that Hub server cannot route mail to mailbox server and pending on MAPIdelivery queue. But there is no error on queue and I need to restart information store service on mailbox server but after a minute, it pending on MAPIdelivery
queue again.
anyone can help me for solve this urgent issue.
thanks
Keith

Hi,
To narrow down the issue, as what Rich mentioned above, we can use the Performance Monitor tool to collect related information and then analyze it.
A related article:
Getting started with Exchange 2007 Performance monitoring and Windows 2008
Hope this helps.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Similar Messages

Keep exchange 2007 Hub transport & CAS during migration to Exchange 2010

Hello,
during a migration from exchange 2007 to exchange 2010 is it supported to keep the old exchange 2007HUB and CAS in charge of the outside mail flow (send/receive) and OWA service.
Here is the scenario :
Actual OWA url : https : // webmail . compagnie . com (2007)
Future OWA url : https : // owa . compagnie . com 2010)
Keep the old url accessible for the users which have not be migrated to the new exchange 2010 MBX server.
Indicate to the migrated users to use the new url instead of the old one.
Keep the old hub transport server (2007) handle the mail flow (send/receive) to the outside.
At the end, when all the users will be migrated, configure the new 2010 Hub/cas to handle the mail flow (send/receive) to the outside.
Thanks a lot for your answers.
David

Thanks for your answers.
So if I have understood right, the only thing I have to take care about (in order to let the 2007 cas/hub server handle the external mail flow (on which the MX is bind) until all mailboxes are migrated) is to add the 2010 cas/hub server in :
Organization Configuration ---> send connector ---> Actual 2007 send connector --> Source server
Thanks a lot.
David
That will take care of the outbound message flow, yes.
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Exchange 2007 HUB Server Faulting application edgetransport.exe

Hello,
I'm having wired problem with my Exchange Server "Hub transport". it keeps queuing the mails and SMTP Gateway unable to send them to the Exchange HUB Server.
Environment:
Exchange Mailbox Role on separate server
Exchange HUB/CAS on separate server
IMSS Trend Micro as Edge SMTP Transport Server.
Faulting application edgetransport.exe, version 8.1.436.0 error keeps coming in the event viewer.
I have stopped the MS Exchange Services and Deleted/Renamed the Queue Directory Under C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue. When I started the services again, new Queue Directory created and mail flow started again.
When I try to access the Queue Viewer in Exchange, got the following error;
Any help would be appreciated.
edgetransport (6376) Transport Mail Database: Database 'C:\Program Files\Microsoft\Exchange Server\TransportRoles\data\Queue\mail.que': While attempting to move to the next or previous node in a B-Tree, the database engine skipped over 796 non-visible nodes
in 160 pages. It is likely that these non-visible nodes are nodes which have been marked for deletion but which are yet to be purged. The database may benefit from widening the online maintenance window during off-peak hours in order to purge such nodes and
reclaim their space. If this message persists, offline defragmentation may be run to remove all nodes which have been marked for deletion but are yet to be purged from the database.
   Name: MailRecipTable
   Owning Table: MailRecipTable
   ObjectId: 9
   PgnoRoot: 51
   Type: 2
   Unversioned Deletes: 796
   Uncommitted Deletes: 0
   Committed Deletes: 0
   Non-Visible Inserts: 0

Hi All,
Prior to this Application Error (1000) starts; I can see there is another warning which appears.
Recipient group membership cache loaded. Group:
[email protected], Time: 00:00:00.5304918, Members: 1490
Faulting application edgetransport.exe, version 8.2.176.0, time stamp 0x4a5b9add, faulting module MSVCR90.dll, version 9.0.30729.4148,
Failed extract of third-party root list from auto update cab at:
Anti-spam agents are enabled, but the list of internal SMTP servers is empty. If there are any MTAs between this server and the Internet, populate this list by using the Set-TransportConfig cmdlet in the Exchange
Management Shell.
edgetransport (5076) Transport Mail Database: The database engine (8.02.0176.0000) started a new instance (0).
edgetransport (5076) Transport Mail Database: The database engine has begun replaying logfile C:\Program Files\Microsoft\Exchange
Server\TransportRoles\data\Queue\trn.log.
The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server mubex01.Domain.com in Routing Group CN=First Routing Group,CN=Routing Groups,CN=First Administrative Group,CN=Administrative
Groups,CN=Domain Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com in routing tables with the timestamp 11/13/2014 11:38:50 AM.
A route to Mailbox server CN=MUBEX01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=Domain,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com could not be found
for store CN=Public Folder Store (MUBEX01),CN=Staff Storage Group,CN=InformationStore,CN=MUBEX01,CN=Servers,CN=First Administrative Group,CN=Administrative Groups,CN=RCSI MUB,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Domain,DC=com in routing tables
with timestamp 11/13/2014 11:38:50 AM. Recipients will not be routed to this store.
The Microsoft Exchange Transport service has started the background scan of the queue database. All messages that have not yet been delivered will be loaded.
The background scan of the transport queue database has completed. 25 message(s) were found.
Journal rules were loaded.
Recipient group membership cache loaded. Group:
[email protected], Time: 00:00:00.5148891, Members: 1490
Faulting application edgetransport.exe, version 8.2.176.0, time stamp 0x4a5b9add, faulting module MSVCR90.dll, version 9.0.30729.4148, time stamp 0x4a594e3d, exception code 0xc0000417, fault offset 0x00000000000552c0,
process id 0x13d4, application start time 0x01cfff366342a0f4.
Appreciate if someone could point me to the right direction on this dilemma.
Thanks,

Exchange 2010 hub-transport server

i have 2 exchange 2010 hubtransport servers.
ideally when i send email my email should be load-balanced but emails send using hubcas1 goes fine and hubcas2 kepts in queues
suppose if i send at a time 5 mail
3 emails go through hubcas1
2 emails stucks in queue in hubcas2

Hi,
As you said you have added both the hub transport servers in the source server option of the send connector.Same time you have mentioned you don't have the smart host to deliver the emails to the internet and also the server hubcas2 can able to resolve the
external domain namespaces .Then do the following .
step 1 :Then please enable the protocol logging on the send connector to see the why the connections from the server hubcas2 is rejected to send emails to internet.
Step 2: Then do the outbound email test from EXRCA tool by using the ip address or name which is mapped on the MX record which belongs to the server hubcas2.
Please feel free to reply me if you have any queries .
Regards
S.Nithyanandham
Thanks & Regards S.Nithyanandham

Exchange 2010 Hub Transport

Hi Spiceheads, I thought that with Exchange 2010 mailboxes will always use the local hub transport on that server first but alas I was wrong. We need to migrate an exchange 2010 box to virtual hardware, I setup and configured a new server with the old one still live, as soon as I installed the HT role on the new server mail immediately started flowing out of it first even though every mailbox and DB was still on the old server, of course this ended up causing our mail to get flagged as spam as the spf records didn't match, thankfully this lasted all of 3 minutes while I uninstalled the role from the new server, My question is - is there a way to add the HT role but still have mail flow out of the old HT server vs the new one?
I want to add the role so I can configure all the options first, including some third party software we have...

Hi allAfter a rather heated conversation with our MSP I come to you for guidance.We've recently acquired another business and need to add two new sites plus a butt hosted server to our network. The current layout is as follows (forgive my terrible diagram):Top is our business, bottom is the one we've purchase, red indicates how the VPNs are structured. We have extensive on-premise infrastructure at the Main Office (top left) so we are planning to retire my butt hosting once our systems have been merged but in the meantime we need to be able to access their system and vice versa so I am hoping for the following:In summaryNew link from my butt hosting to the Main OfficeNew link from the alt-main office to Main officeNew link from the new "other site" to Main OfficeNow, our VPNs are controlled by our MSP, after a two week delay waiting...

Removing Exchange 2007 hub server

Hi, my company has last remaining hub 2007 server while the rest is already migrated to Hub 2010 servers. All hub servers subscribed to Edge 2007 servers. i have issue when i want to remove last hub 2007 servers with error like "This
computer is configured as a source transport server for 1 connector(s) in the organization. These must be moved or deleted before Setup can continue". i read other post that i need to remove 'send connectors' from hub 2007. Do i need to remove
edge subscriptions too in hub 2007 server ? If i remove send and egde subscription from hub 2007 server, is it the action will impact the hub 2010 servers ?
2nd question, let say if i want to remove edge server, do i need to re-create send and receive connectors in hub 2010 servers?

If you are removing edge servers, you need to configure your systems so that Internet email bypasses them (in both directions). In answer to your #2 above, your send and receive connectors have to be configured for this
before you remove the edge servers. Whether you create new ones or modify existing ones for this depends on how the rest of your architecture is designed. Once this is done, you can remove your edge subscriptions and uninstall your
edge servers.

How to migrate Exchange HUB transport 2007 server with Exchange Hub transport 2010.

Hi,
How to migrate hub transport 2007 server with Exchange 2010 hub transport server.
Regards
Anil

Hi Anil
You do not do an in-place upgrade of Exchange - you build new Exchange 2010 Hub Transport Servers, you can utilize existing hardware by uninstalling and installing Exchange 2010 - but you must have Hub Transport Servers that match the Exchange version in
place for all Mailbox Servers that have the same Exchange version.
Essentially there must be Exchange 2007 Hub Transport servers in place whilst there are Exchange 2007 Mailbox servers.
Read "Upgrading from Exchange 2007 Transport -
http://technet.microsoft.com/en-us/library/dd346708%28v=exchg.141%29.aspx"
Exchange 2010 will synchronise certain configuration like Transport Rules and journaling when installing the first Exchange 2010 Hub Transport server, but from then on you must ensure synchronisation yourself.
Send Connectors and Recieve Connectors will need manual configuration.
Oliver
Oliver Moazzezi | Exchange MVP, MCSA:M, MCITP:Exchange 2010,Exchange 2013, BA (Hons) Anim | http://www.exchange2010.com | http://www.cobweb.com | http://twitter.com/OliverMoazzezi

Edge Transport Server - Exchange 2013 coexistence Exchange 2007

Hi Exchange-Gurus,
We have one Exchange Org.
sub AD Domain1: A.domain.com (with Exchange 2007 SP3 R10)
sub AD Domain2: B.domain.com (with Exchange 2013 CU6); DMZ contains Exchange Transport Server - Exchange 2013
Is it possible to install within the DMZ of AD Domain1 a Edge Transport Server - Exchange 2013?
Thanks.
Guitarman

Hi Guitar,
Thank you for your question.
Is it possible to install within the DMZ of AD Domain1
an Edge Transport Server - Exchange 2013?
A: Yes, we could create an Exchange 2013 Edge server on the DMZ of AD domain1.
Notice: Before we create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, we need to install Exchange 2007 SP3
Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/aa996719(v=exchg.150).aspx
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Routing email from exchange 2007 to 2010 .

Although this is an
hypothetical question but still would be a great help if anyone could answer this : " How email routing takes place from exchange 2007 user
to exchange 2010 user. I have exchange 2007 and 2010 ,provided i am using single forest with same domain name in both 2007 & 2010 environment "
Aditya Mediratta

Hi,
Firstly,I'd like to explain, message routing from Exchange 2007 to Exchange 2010 is message delivery between responsed Hub Transport servers：
When a Hub Transport server queries Active Directory to determine the Mailbox server hosting the destination mailbox, it also retrieves the version of the Mailbox server. If the Mailbox server is an Exchange 2007 server that's in the same site as the Hub Transport
server, the Hub Transport server will relay the message to an Exchange 2007 Hub Transport server in the same Active Directory site.
For more information about the emails routing process, you can refer to the following articles:
http://technet.microsoft.com/en-us/library/bb232193(v=exchg.141).aspx#Old
http://technet.microsoft.com/en-us/library/aa996349(v=exchg.141).aspx
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Upgrade to Exchange 2007 SP3 from SP2

Need Advice for Upgrade Exchange Server 2007 SP2 to SP3. My Existing environment is 4 AD. All are run in windows server 2003 and 3 Exchange Server 2007 that are run OS 2003 64 bit one SP1 and another two is SP2. and My next plan is Migration Exchange 2007
to 2013 and AD 2003 to 2012 R2. Please explain me any body for this matter as per as soon.
Md. Ramin Hossain

Hi Md,
Thank you for your question.
In addition, when Exchange 2007 and Exchange 2013 are co-existed in organization, and we want to create an EdgeSync Subscription between an Exchange 2007 Hub Transport server and an Exchange 2013 SP1 Edge Transport server, you need to install Exchange 2007
SP3 Update Rollup 13 or later on the Exchange 2007 Hub Transport server.
Exchange 2013 is Exchange 2013 Cumulative Update 2 (CU2) or later on all Exchange 2013 servers in the organization.
We could refer to the following link:
https://technet.microsoft.com/en-us/library/jj898581(v=exchg.150).aspx
We could refer to the following steps to migrate Exchange 2007 to Exchange 2013:
http://blogs.technet.com/b/meamcs/archive/2013/07/25/part-1-step-by-step-exchange-2007-to-2013-migration.aspx
We could ask to our Window Forum for Window 2003 migration.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Compatibility between Exchange 2007 service packs

Hi all, I have 5 servers Exchange:
- 3 Servers CAS and HUB
- 2 Servers Mailbox server in Microsoft Failover Cluster (MSCS)
Domain Controllers are all
Windows Server 2003 SP2
The versions of Exchange 2007 SP1 servers are all:
8.1 Build 240.6
I have thought about installing SP3 and RU13 in all 5 servers for Exchange, but I'm going to install SP3 and RU13 on 2 servers CAS / HUB and the following week at the other CAS / HUB server.
Finally, the following week in the two Mailbox Servers.
Is there any problem if I miss 2 servers CAS / HUB with SP3 RU13 and the other CAS / HUB in SP1, this will only be for a few days?
Is there any problem if I leave the servidors Mailbox Servers in SP1 while CAS / HUB are in SP3 RU13, this will only be for a few days?
regards
Microsoft Certified IT Professional Server Administrator

Hi Yupikaiey.
Only thing you should be concerned is if you have CAS-CAS proxy or the Mailbox Cluster part.
Your current plan looks good. Just stay alert for any uncommon issues popping up, which would normally mean due to the difference.
If you upgrade your servers in this order, you may avoid potential service interruptions.
Details below:
Version Constrains are more of between roles of 2007-2010-2013 and not between same version SPs or RUs.
Exchange 2013 Server Role Architecture
The Past: Exchange 2007 and Exchange 2010
Our goal was to make these server roles autonomous units. Unfortunately, that goal did not materialize in either Exchange 2007 or Exchange 2010. The server roles were tightly coupled along four key dimensions:
2.This also necessitated a tight versioning alignment – a down-level Hub Transport or Client Access shouldn’t communicate with a higher version Mailbox server; in some cases this was enforced (e.g., Exchange 2007 Hub Transport servers cannot deliver messages
to Exchange 2010 Mailbox servers), but in other cases they were not (e.g., an Exchange 2010 SP1 Client Access server can render data from an Exchange 2010 SP2 Mailbox server).
The versioning restriction also meant that you could not simply upgrade a single server role to take advantage of new functionality – you had to upgrade all of them.
The Present: Exchange Server 2013
If I upgrade the Mailbox server with a service pack or cumulative update, then for a given mailbox hosted on that server, all data rendering and content conversions for that mailbox will be local, thus removing version constraints and functionality issues
that arose in previous releases.
Exchange 2007 Servicing
http://technet.microsoft.com/en-in/library/dd421853(v=exchg.80).aspx
Deployment Order
Our test infrastructure guarantees that Exchange hotfixes work across multiple server roles. The order in which you apply the update rollup to the servers is not important except if you are deploying CAS-CAS proxying. Because the update rollups are not segmented
for different Exchange server roles or for specific file configurations, apply each update rollup package to all Exchange 2007 servers in your environment.
If you have multiple Active Directory sites, and if you deploy a Client Access server in the proxy sites that do not face the Internet, you must
apply the update rollup to the Internet-facing Client Access servers
and to the non-Internet-facing Client Access servers in the proxy site simultaneously. For other Exchange 2007 configurations, we recommend that you
apply the update rollup package to the Client Access servers before
you apply it to servers that are running other Exchange 2007 server roles, such as the Mailbox server role, the Hub Transport server role, and the Edge Transport server role.
Note:
Applying service packs and update rollups to clustered Mailbox servers requires specific planning and application steps. For more information about how to apply service packs to Exchange 2007 clustered Mailbox servers, see
Upgrading Clustered Mailbox Servers to Exchange 2007 SP1 or later. For more information about how to apply update rollups to Exchange 2007 clustered Mailbox servers, see
Applying Exchange 2007 Update Rollups to Clustered Mailbox Servers.
For Patching and compatibility between versions:
Determine the service pack level of Exchange.
Update rollups are service pack dependent. For example, an Update Rollup 5 package is available for Exchange 2007 and for Exchange 2007 Service Pack 1. To determine the service pack level of Exchange, examine the
ExchangeVersion property. For more information about how to view the
ExchangeVersion property and about the build number that is associated with each Exchange version, see
Exchange Server 2007: Platforms, Editions, and Versions.
References:
How to Install the Latest Service Pack or Update Rollup for Exchange 2007
Exchange Server Updates: build numbers and release dates
We are looking at doing the roll-up to SP3
Coexistence of Exchange2007 SP1 and Exchange 2007 SP3
Regards,
Satyajit
Please “Vote As Helpful”
if you find my contribution useful or “Mark As Answer” if it does answer your question. That will encourage me - and others - to take time out to help you.

Hourly limits when mass mailing via Hub Transport Severs

Hi Everyone
I need to know what are the parameters to be configured on an Exchange 2007 Hub transport server for:
- Altering the amount of mails that can sent by an application on an hourly rate externally via SMTP (my organisation wishes to send 10000 mails every hour)
- each mail must have a maximum size of 270Kb
Does anybody know:
(1) What are the two values that can be modified on the Hub Transport server
(2) How can we monitor performance impact? particularly if we increase the hourly rate from say 10000 to 15000?
Many thanks in advance

Hi,
Based on my knowledge, there is no value in Transport server to limit the maximum number of emails sending outbound per hour. For more information about it, please refer to transport server limits part in the following article:
http://technet.microsoft.com/en-us/library/aa997166(v=exchg.80).aspx
Hub Transport Server Properties > Limits Tab (RTM)
http://technet.microsoft.com/en-us/library/bb629486(v=exchg.80).aspx
As for the max message size limits for all emails, there are some parameters to set it in global limits (Set-Transportconfig –maxreceivesize 270Kb –maxsendsize 270Kb),connector limits (MaxMessageSize in
Set-SendConnector cmdlet), server side limits (Set-TransportServer cmdlet)and user limits
(Set-Mailbox -Identity Janas –MaxSendSize
). For more information about Exchange 2007 Message Size Limits, please refer to:
http://www.msexchange.org/articles-tutorials/exchange-server-2007/management-administration/exchange-2007-message-size-limits.html
If you have any Exchange issue, please ask a question in Microsoft Exchange forum for more suggestions:
http://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrgenerallegacy%2Cexchangesvrclientslegacy&filter=alltypes&sort=lastpostdesc
Regards,
Winnie Liang
TechNet Community Support

Behaviour of Microsoft Transporter Suite (Notes migration to Exchange 2007)

Dear Sir,
     I have a question about configuraiton of Microsoft transporter, not sure whether it is a behaviour or it can be fixed.
Question 1:
Lotus Notes 7.04 --> Exchange 2007
Microsft Transport: Scheduler set to every 15 min.
Q1. Does it mean that Notes sync to AD User account setting only in every 15 min only ?
Q2. It seems that it will not sync Notes email mailbox message with Exchange mailbox until manual press
    'Migrate selected mailbox', may I confirm that is it a design behaviour.
Q3. After created free/busy connector (Every 60 minutes of sync), it seems that it will not sync
      user calendar until manual pressed 'Synchronize Now'.
Q4. Can Mirocosft transport suit support workstation NSF file to PST file ?
Q5. In notes environment, ACL will be used to configure boss/secretary condition which allow send as permission.
    Does it mean that all permission will be reconfigured manually? Or any Microsoft tools to work on it.
Regards,
Joe

Hello Joe,
I checked with a specialist regarding your questions and here are the responses.
I hope this helps!
Q1. Does it mean that Notes sync to AD User account setting only in every 15 min only ?
If this is referring to Direcctory Synchoronization, then yes, it will synch any updates every 15 minutes. However, there is no reason to do a dirsync that often.
Q2. It seems that it will not sync Notes email mailbox message with Exchange mailbox until manual press
    'Migrate selected mailbox', may I confirm that is it a design behaviour.
This one seems to refer to migration. If you are wanting to migrate the mailboxes and email, you would have to manually migrate each user. In other words, this is not an automated process. So yes, this is by design
Q3. After created free/busy connector (Every 60 minutes of sync), it seems that it will not sync
user calendar until manual pressed 'Synchronize Now'.
A dirsync will have to be run after the Free/Busy Connector is created. However, it should only have to be run once. After that, when a user requests new calendar information, it will pull information for that user
Q4. Can Mirocosft transport suite support workstation NSF file to PST file ?
Yes, you will have to use the EMS to do this. It's not possible via the GUI.
Q5. In notes environment, ACL will be used to configure boss/secretary condition which allow send as permission.
    Does it mean that all permission will be reconfigured manually? Or any Microsoft tools to work on it.
There is not an automated way of doing this.
Kevin Ca - MSFT

Setup first Exchange 2013 with mixed mode exchange 2007/2010

my company has exchange 2007 hub and edge and exchange 2010. I'm planning to retire all exchange 2007 first follow migrate to exchange 2013. so I have few questions as below ?
1. Do I need to unsubscribe hub 2007 from edge first before uninstall ? Currently we have 2 hubs (2007 and 2010). How can I remove hub 2007 from exchange edge server 2007 ?
2. let say once my landscape just have exchange 2010, is it installing our first exchange 2013 will impact our mail flow ? my understand there is NO impact until we switch over 'mail IP' to CAS 2013. am I correct ?
3. what is minimum requirement for co-exist with exchange 2013 for exchange 2010 ? is it enough with SP3 or I need to apply SP3 RU5 ? in deployment assistant, the requirement is SP3 RU5 but most article i read just mention SP3.
thx.

1. I would remove the edge subscription for sure. Then it isn't strictly necessary to uninstall Exchange Edge if you're just going to flatten the box anyway because that server isn't in Active Directory except through the Edge Subscription process.
I'm not sure what you're asking about "NO impact".
2. The coexistence requirements are clearly documented in TechNet. I'll leave it to you to search it since you can do that just as well as I can. That said, I would recommend that you go ahead and install the latest rollup on all your servers
first.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Migrate mailbox from Exchange 2007 to Exchange 2013, mailbox stay in queue

Hi,
I'm trying to migrate a mailbox but the request is staying in queue, according to : Get-moverequest | Get-Moverequeststatistics
Configuration server Exchange 2007 SP3 :
Domain : test.com
OS : Windows 2008 server SP2 (not R2)
Firewall : OFF
Exchange roles are on separate three servers : CAS - MAILBOX - HUB.
Configuration Server Exchange 2013 :
Domain : new.com
OS: Windows 2012 R2
Firewall : OFF
This environment is on a closed network unable to reach internet.
I have try to restart the Replication service, but it didn't worked.
I've searched a lot but i can't find any information to help me. The mailbox stays in queue....
Anyone ever had this issue?
Thanks you and have a nice day.

Hi ,
Based on my knowledge below things need to checked.
1.Please check the content index state of the target database is healthy and ensure the entire mailbox database status was in healthy state.
2.If your exchange 2013 is an single server and target database copy doesn't have the second copy then we need to set the below parameter value to none.
DataMoveReplicationConstraint : None
Note : After the above change ,Microsoft exchange mailbox replication service needs to be restarted.
3.Restart the Microsoft exchange mailbox replication service and check the results.
4. Have you tried moving the same mailboxes to the different databases.
5.If the move request is in the failed state then we can export the details of the move request to find out the exact cause for the failure.
Get-MoveRequestStatistics -Identity "nithya" -IncludeReport | fl >c:\nithya.txt
Please feel free to reply me if you have any queries.
Thanks & Regards S.Nithyanandham

Exchange 2007 hub transport MAPIdelivery queued

Similar Messages

Maybe you are looking for