Exchange 2013 CU 2 - Cmdlet cancelled. Cmdlet New-MoveRequest

Hi All,
I'm struggling with some issue in Exchange 2013 CU2 with user mailbox migration from Exchange 2010. When starting a Migration Batch via ECP site or from powershell i got an warning:
Log Name: MSExchange Management
Source: MSExchange CmdletLogs
Date: 2014-01-09 14:52:30
Event ID: 5
Task Category: General
Level: Warning
Keywords: Classic
User: N/A
Computer: EXMBX1.Domain.local
Description:
Cmdlet cancelled. Cmdlet New-MoveRequest, parameters {TargetDatabase=MBXD1, ArchiveTargetDatabase=MBXD1_ARCH, WhatIf=True, Identity=Domain.local/User Name, BadItemLimit=0, BatchName=MigrationService:test_kar, CompletedRequestAgeLimit=7.00:00:00}.
And the migration batch is in "Syncing" state. Is there any solution for this ?
-- Kamil Tatar

Hi Kamil,
You can use the following cmdlet to check what's wrong in the result.
Get-MoveRequest -Identity "xxx" | Get-MoveRequestStatistics -IncludeReport | FL
Here is a similar thread for your reference.
Exchange 2013: batch to migrate users from 2010 database is hung at "Syncing"
http://social.technet.microsoft.com/Forums/exchange/en-US/90403f75-e530-478a-ab68-27823b730f68/exchange-2013-batch-to-migrate-users-from-2010-database-is-hung-at-syncing-after-a-disaster?forum=exchangesvrdeploy
Hope it helps.
If there are any problems, please feel free to let me know.
Best regards,
Amy
Amy Wang
TechNet Community Support

Similar Messages

Exchange 2013 migration warning, cmdlet canceled

I have an Exchange 2013 SP1 on 2012 R2 and I get this warning migrating a users mailbox from 2010
Cmdlet cancelled. Cmdlet New-MoveRequest, parameters {TargetDatabase=XXXX, WhatIf=True, Identity=xxxxx BadItemLimit=3, BatchName=MigrationService:XXXX, CompletedRequestAgeLimit=7.00:00:00}.
I removed user info.
Looking here I see some similar postings but nothing in the way of an answer. It completes fine, no issues, but these warnings indicate something is off.
Any answer for this?

Hi,
Based on my research, the warning may be caused by the disk storage performance on one of your Exchange servers. And here are some similar threads you can refer to:
http://social.technet.microsoft.com/Forums/en-US/00a48c77-3ddf-4d3b-b870-425a8a6e288e/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin
http://social.technet.microsoft.com/Forums/en-US/d93249da-22d9-496a-a5c0-529077ea33be/exchange-2013-cu-2-cmdlet-cancelled-cmdlet-newmoverequest?forum=exchangesvradmin
Thanks,
Angela Shi
TechNet Community Support

Exchange 2013 SP1 database missing?? New install of Exchange 2007 co-exist

Hi all,
Finally got Exchange 2013 SP1 installed except I am not so sure I have a database. This is installed on a Server 2008 system and is co-existing with Exchange 2007.
When I go to SERVERS and DATABASES I don't have anything listed. When I click SERVERS on the left hand pane and SERVERS at the top I see both servers, 2007 and 2013. But when I double click my new Exchange Server 2013 name I get the error:
The operation couldn't be performed because object '*\ExchangeServerName' couldn't be found on 'FirstDCName.mydomain.com'
Why would I get this error? The install itself was problematic so I am concerned something is broke.
Thank you in advance.

Hello,
Firstly, I recommend you check if the server name "*\ExchangeServerName" exists on DC via ADUC (select Computers).
Secondly, please run the get-exchangeserver | fl name cmdlet to check your exchange server name.
And then please check the exchange setup log to check if the exchange 2013 server is installed successfully. If not, please check if there is any error in setup log.
If you have any feedback on our support, please click
here
Cara Chen
TechNet Community Support

Exchange 2013: when I create a new user in 2012 AD no mailbox is created.

Hi,
I have two VMs both running Windows server 2012 R2.
S1-DC.domain.local (GC)
S2-EMS.domain.local (Exchange 2013 CU2)
When I add a new user account from the Admin Center on S1-DC.domail.local, no Exchange 2013 mailbox is being created.
I can add the AD user to Exchange 2013 manually, but I assumed a mailbox would be created automatically when an account is created.
What would be the cause of this?
thanks,
Fultz.
Have a good day.

There is no automatic provisioning of mailboxes when you create an AD user.
To have that automatically done, you can develop a Powershell script that will run periodically (Example: Every hour), will identify the newly created AD accounts and will provision a mailbox for them.
More details if you ask them in Exchange forums: http://social.technet.microsoft.com/Forums/exchange/en-US/home?category=exchangeserver
This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.
Get Active Directory User Last Logon
Create an Active Directory test domain similar to the production one
Management of test accounts in an Active Directory production domain - Part I
Management of test accounts in an Active Directory production domain - Part II
Management of test accounts in an Active Directory production domain - Part III
Reset Active Directory user password

Move Exchange 2013 installation to new virtual machine

Currently have: 1 virtual server - Server 2012 (DC, Global Catalog), Exchange 2013 CU1 installation (yes I know- dont install Exchange on DC etc etc ... ). Server2012/Exchange2013 is installed on one VMDK, EDB and logs are saved on another VMDK.
Want to do: Create second virtual machine and install Server 2012 (different name), add it as a member to the same domain (also in the same network), install Exchange 2013, move all mailboxes to the new server, uninstall the old Exchange 2013.
Question is- is it possible to somehow unmount the existing database (I am only using one database for mailboxes and public folders) and mount it to the new server or do I have to create a new database on the new server and move the mailboxes there? I've
heard that the Exchange EDB databases were supposed to be portable between same versions of Exchange.
Any advice is appreciated.

Hi,
Agree with Andy, to avoid down time, we can depend on database portability.
And here are the steps you can refer to:
1. Install new Exchange server on the member server.
2. Move Mailbox Database using Database Portability:
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx
3. Move the public folders (if any), re-home the offline address book, and move your SMTP connectors
http://support.microsoft.com/kb/822931
4. Remove the old Exchange server.
Thanks,
Angela Shi
TechNet Community Support
Thanks for the reply.
I'm a bit confused on the instructions from
http://technet.microsoft.com/en-us/library/dd876926(v=exchg.150).aspx- does step 4 instruct me to overwrite the newly created database (on the new server) with the old database and then mount it on the new server? Also, as the public folders are now in
a mailbox on the same database- aren't they moved with the database without extra hassle?
Also the link you gave me in Step 3 in your post refers to Exchange 2003.
Thanks in advance.

Exchange 2013 SP1 - The attempt to search the administrator audit log failed.

During migration process from Exchange 2010 to 2013, after moving Arbitration mailbox from Exchange 2010 database to Exchange 2013 SP1 database, cmdlet Search-AdminAuditLog fails with following error.
The attempt to search the administrator audit log failed. Please try again later.
+ CategoryInfo : NotSpecified: (:) [Search-AdminAuditLog], AdminAuditLogSearchException
+ FullyQualifiedErrorId : [Server=EX2013,RequestId=517873e3-a623-4363-bfdc-e5aa23595c33,TimeStamp=29. 4. 2014
8:38:37] [FailureCategory=Cmdlet-AdminAuditLogSearchException] 2774D0CF,Microsoft.Exchange.Management.SystemConfig
urationTasks.SearchAdminAuditLog
+ PSComputerName : ex2013.domainname.local

Hi,
First, please make sure the Microsoft Exchange Search and the Microsoft Exchange Search Host Controller service are running and please run the get-mailbox -arbitration cmdlet to check the result.
Besides, please check the properties of the DiscoverySearchMailbox and verify that the homeMDB attribute is set to a mounted database.
If the steps above don't work, please try to re-create a new Discovery System Mailbox to check the result. You can refer to the following article.
Re-Create the Discovery System Mailbox
http://technet.microsoft.com/en-gb/library/gg588318(v=exchg.150).aspx
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 shell mailbox move requests showing up on 2010 hub server

We're in the process of migrating from exchange 2010 to 2013. All servers are patched and up to date. We have two 2010 CASs (one for external OWA use only) and a mailbox cluster. Our exchange 2013 setup is almost a mirror with the exceptions of how the exchange
server roles have changed.
Any new-moverequest commands entered from the either of our exchange 2013 CAS servers fail to show up in the EAC/recipients/migration page.
If the local move request is done in the EAC the batch(es) show up just fine.
The more perplexing part is: while I was going through a 2010 hub (looking for a different issue) I noticed ALL the batches/mailbox moves that weren't showing up in the 2013 EAC were listed in the 2010 move request section.
I can't get any info on the moves in the 2010 console (because they're 2013 jobs) but i can get statistics and such from a 2013 shell.
any ideas?

Are you running ex2013SP1 CU6? Can you try to update n check?
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.

Introduce an "passive" Exchange 2013 in Exchange 2010 environment without user or administration impact.

Hi
We wish to introduce an Exchange 2013 server in our existing Exchange 2010 environment.
The Exchange 2013 server is only needed for migration purposes where we wish to leverage the new features of the migration-batch functionality.
It’s important that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, right now, since the customer wish to stay on 2010.
Can you guys come up with anything to be aware of?
Oblivious we disable the Autodiscover SCP for the Exchange 2013 server, so that the clients will not hit this server. Nor will we point any URLs to the Exchange 2013
I can see that a new “Default Offline Address Book (Exch2013)” is created and set as default when EX2013 is installed. We will change this back to the default EX2010.
The server will properly take part in the Shadow Redundancy feature, and is doesn’t seem to be possible to exclude the server or avoid, unless disabling Shadow Reduncancy.
I can only come up with these 3 things that will have a "direct" impact on the environment, but any input will be highly appreciated!
BR,
Martin

Hi,
I agree with Li Zhen’s suggestion. If you don’t migrate from Exchange 2010 to Exchange 2013, we can disable add services in Exchange 2013 and don’t use it any more.
If you want that the Exchange 2013 server will not have any “visible” impact on the Exchange 2010 environment, or take over any functionality, please keep the published server to pointed to Exchange 2010. Then the original configuration in Exchange 2010
would not be changed to the new configuration in Exchange 2013.
If you want to use Exchange 2013, then we can point the published server to Exchange 2013 and configure the virtual directories in Exchange 2013. Though all mailboxes are still located in Exchange 2010, all external requests would be proxy or redirected
from CAS 2013 TO CAS 2010 automatically.
For more information about Client Connectivity in an Exchange 2013 Coexistence Environment, please refer to:
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Regards,
Winnie Liang
TechNet Community Support

Exchange 2013 - Folders missing when importing PST to archive mailbox

Hello,
I'm having an issue when importing PST files to an Exchange 2013 archive mailbox using the command "New-MailboxImportRequest
test -FilePath '\\server\e$\ArchiveExport\test.pst' -IsArchive -BadItemLimit 5 -ErrorAction Stop"
The import is running without an error and shows the status complete. The size of the archive mailbox is exactly the same like the size
of the PST file!
But when I check the users archive mailbox some folders are missing. It seems that this happens only to default folders like "Inbox"
or "Sent Items". Other folders are visible.
The mailbox import log shows the following:
16.01.15 16:31:56 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.
16.01.15 16:31:56 [server] Copying 3 items, 4.789 KB (4,904 bytes). Skipping 0 items, 0 B (0 bytes).
If I start the import process again the log says the following:
16.01.15 16:46:54 [server] Merging folder '/Top of Personal Folders/Inbox [Inbox]' into '/Inbox [Inbox]'.16.01.15
16:46:54 [server] Copying 0 items, 0 B (0 bytes). Skipping 3 items, 4.789 KB (4,904 bytes).
So it seems that the mails are really there but just not visible.
I did some tests:
When I import the PST file directly to the users mailbox (without parameter -IsArchive) I can see all content of the PST file.
When I add the parameter -TargetRootFolder "Testfolder" the whole PST content shows up correctly under that folder.
Can anyone explain this?
Regards

Hi PhilippMair,
Thank you for your question.
If all subfolders were merged, we could use OWA to check if the missing folders is appeared. If we could see missing folders by OWA, I suggest we recreate outlook profile and reset outlook view.
In order to troubleshooting, I suggest we collect the import log to analysis if the subfolder of Inbox or Sent Item is exported.
In my test lab, inbox has three subfolders, there are 123,456,789; when I import PST file, I will see the following log:
1/20/2015 7:32:31 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox' into '/Top of Information Store/Inbox'.
1/20/2015 7:32:31 AM [EXCH2-CU1] Copying 18 items, 302.3 KB (309,594 bytes). Skipping 0 items, 0 B (0 bytes).
1/20/2015 7:32:32 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/123' into '/Top of Information Store/Inbox/123'.
1/20/2015 7:32:32 AM [EXCH2-CU1] Copying 5 items, 62.21 KB (63,699 bytes). Skipping 0 items, 0 B (0 bytes).
1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/456' into '/Top of Information Store/Inbox/456'.
1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 6.908 KB (7,074 bytes). Skipping 0 items, 0 B (0 bytes).
1/20/2015 7:32:33 AM [EXCH2-CU1] Merging folder '/Top of Outlook data file/Inbox/789' into '/Top of Information Store/Inbox/789'.
1/20/2015 7:32:33 AM [EXCH2-CU1] Copying 1 items, 21.31 KB (21,820 bytes). Skipping 0 items, 0 B (0 bytes).
We could check if there are any subfolder which would not be merged and copied. If your import log has any abnormal, I suggest you send log file to
[email protected] for our troubleshooting.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim

Exhcange 2003 to Exchange 2013 Through Exchange 2010

Hello everyone and thanks for your help in advance. I have been tasked with the upgrade of an exchange 2003 server to Exchange 2013. After reviewing the lack of upgrade paths directly to 2013, I think the best path would be to transition through
2010. The domain controller is also 2003. If I understand the process correctly, I should join the new Exchange box to the current domain. Then install Exchange 2010. My questions are:
1. Is installation as simple as the way I described?
2. After installation, is there a way to port the Exchange data from the old machine to the new machine without taking down the Exchange 2003 machine?
Unfortunately, I have only a very basic understanding of Exchange, so I need to take this in small steps. Any help would be appreciated.

Hi Kmcnet,
Base on my experience , if only a small number of mailboxes, the most convenient way is to export/import PST files.
I recommend you consider using the following method to upgrade the exchange to 2013:
1.Export all the users mailbox contents into a PST since its only 35 users
2.After you confirm the exported pst are fine remove the exchange 2003 server
3.Install Exchange 2013 in your environment and create new mailboxes for 35 users
4.Import the pst to their new mailboxes
Best regards,
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]
Niko Cheng
TechNet Community Support

New-MoveRequest -Remote legacy return error Database '04ba5257-54b1-4ee8-9b50-203c3f9107fe' doesn't exist.

I'm try to migrate from Exchange 2007 (on 2003 R2 x64) to Exchange 2010 (on 2008 R2) (all with last service pack) in different domain with a forest and domain trust.
I know it is Exchange 2013 forum but I don't see Exchange 2010 related forum.
1. I have made a Prepare-MoveRequest and all work fine
2. I have migrated other attribute with ADMT 3.2 and all work fine (the user can access the new domain and browse all file server of the old domain)
3. I' m logged on Exchange 2010 management shell and the command:
New-MoveRequest -Identity "[email protected]" -RemoteLegacy -RemoteCredential $Exchaneg2007Cred -RemoteGlobalCatalog dc01.exchange2007domain.com -TargetDatabase "EXHC2010DB01"
-TargetDeliverydomain "exchange2010domain.local" -Verbose -Debug
The system return the error:
Database '04ba5257-54b1-4ee8-9b50-203c3f9107fe' doesn't exist.
+ CategoryInfo : NotSpecified: (0:Int32) [New-MoveRequest], RemotePermanentException
+ FullyQualifiedErrorId : 8C654C28,Microsoft.Exchange.Management.RecipientTasks.NewMoveRequest
the database id '04ba5257-54b1-4ee8-9b50-203c3f9107fe' exists and is the Source Mailbox database on Exchange 2007
Any Idea or suggestion
LSo
LSo Lorenzo Soncini Trento TN - Italy

Hi LSo,
From your description, when you run the New-MoveRequest cmdlet on Exchange 2010 server, it occurs an error that Source Mailbox Database doesn't exist. In your case, I recommend you use the following cmdlet to verify if you can retrieve the source mailbox
database on Exchange 2010 server.
Get-MailboxDatabase -Identity "04ba5257-54b1-4ee8-9b50-203c3f9107fe"
Please take your time to post the result for my further research.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

What happend New-MailboxExportRequest cmdlet in exchange 2013 SP1 is missing?

Cmdlet New-MailboxExportRequest is not recognize cmdlet in Exchange 2013 SP1
How can i do export mailbox to pst file in exchange 2013 SP1?

You might be facing this issue because of not having the rights to execute the New-MailboxExportRequest CMDLET.
Follow the steps given below in order to export the mailboxes into PST file
1. Open the Exchange Console and run:
New-ManagementRoleAssignment -Name "Import Export PST" -SecurityGroup "Organization Management" -Role “Mailbox Import Export"
This will generate a new role group called Import Export PST to the Oranization Management group with the role Mailbox Import Export.
You should Close and Restart the Exchange Management System again so that the changes made will get reflected in the settings, otherwise you will still get the same erroriIf not
restarted. Now move to the next steps.
2. Assign “Mailbox Import Export” role to it.
3. Add Desired Users to Role Group
4. Create Network Share ( Exchange Trusted Subsystem group has read/write permission to NTFS Permissions)
5. Run PS New-MailboxExportRequest
6. Monitor New-MailboxExportRequest
Verify PST File has been created on the network Share and you are done.
If you get the same error again, then there will be some hardware or software issues due to which you are not able to export mailboxes into PST files. In that case, you can make
use of any third party tool like Stellar Phoenix EDB To PST converter, which will help you to export your exchange database files to PST files easily and quickly. You can try this software by downloading its demo directly from their site http://www.stellarinfo.com/email-repair/edb-pst-converter.php

It is there an alternative to the Test-SystemHealth powershell cmdlet for Exchange 2013?

Hello
The Powershell cmdlet Test-SystemHealth, that was available on Exchange 2010, is no longer available on Exchange 2013.
Test-SystemHealth cmdlet gathered data about the Microsoft Exchange system and analyzed the data according to best practices.
Are there any alternatives to this for Exchange 2013?
Thanks!

Haven't really played with it too much, but check out Get-ServerHealth
http://technet.microsoft.com/en-us/library/jj218703(v=exchg.150).aspx
Looks to have replaced Test-SystemHealth.

SCCM 2012 SP1 and Exchange 2013 Connector Get-Recipient cmdlet failed

I have been trying to get my Exchange Connector working with SCCM 2012 SP1 for a week or so now. Every post tells me that the Get-Recipient cmdlet failed is a security permissions error. I have given the service account running the connector full Exchange
Server Management rights including Recipient Management and Organization View-Only. I have even tested remote power shell to the CAS server and run the cmdlet with no issues.
For some reason it just does not want to work for me. Has anyone been running into this issue?

Now before you read the following error and say oh this is a permission issue I am telling you it is not. I have given the account full Exchange admin rights and I have even tested the Get-Recipient cmdlet remotely to the Exchange server and it works with
no issues. I have also noticed multiple forum posts with the exact same issues.
I have noticed one thing that stands outs "Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean"
I believe this issue may be related to changes in the powershell commands with Exchange 2013, but I do not know where or how to edit the ps1 script.
I am getting the error below:
ERROR: [MANAGED] Invoking cmdlet Get-Recipient failed. Exception: System.Management.Automation.RemoteException: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to
type System.Boolean."~~ at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)~~ at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings
settings)~~ at System.Management.Automation.PowerShell.Invoke()~~ at Microsoft.ConfigurationManager.ExchangeConnector.Connector.Invoke(PSCommand cmd)
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
STATMSG: ID=8817 SEV=W LEV=M SOURCE="SMS Server" COMP="SMS_EXCHANGE_CONNECTOR" SYS=MySite SITE=MySiteID PID=xxx TID=xxx GMTDATE=Thu Sep 19 07:00:01.653 2013 ISTR0="Get-Recipient" ISTR1="ParameterBindingFailed,Microsoft.Exchange.Management.RecipientTasks.GetRecipient"
ISTR2="Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."" ISTR3="" ISTR4="" ISTR5="" ISTR6=""
ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)
ERROR: [MANAGED] Exception: Cannot bind parameter 'Filter' to the target. Exception setting "Filter": "The value "$true" could not be converted to type System.Boolean."
SMS_EXCHANGE_CONNECTOR 9/19/2013 12:00:01 AM
4200 (0x1068)

Exchange 2013 SP1 cu8 - mssing cmdlet - Get-SendConnector command missing, cannot change smart host port

Hi Everybody,
For some reason my Exchange 2013 SP1 cu8 are missing a bunch of cmdlets.
When i run the exchange powershell and get all the cmdlet command - i noticed all the send and receive connectors are missing.
This all started when i needed to change the smart host port for a client because their internet provider was blocking port 25.
So i did the traditional cmdlet
Get-SendConnector
Set-SendConnector -Indentity "connector name" -Port 551
Both commands i get "The term Get-SendConnector is not recognized as the name of a cmdlet, function, etc"
When i type Get-ExCommand
Any reference to SendConnector and ReceiveConnector are not on the list.
Am I missing somethings? This is a classic example why GUI and cmdlet functions should both be available and not just on cmdlets.
I went on other Exchange 2013 SP1 cu7 servers to see, and they all have the Send and Receive connectors in the cmdlets.
The only difference with this particular setup, is that this is the first Exchange 2013 on-premise installation with Windows 2012 r2 Small Business Essentials. However, i very much doubt the on-premise installation add-on to SBS would cause any issues
to missing cmdlets.
I searched all over the internet and found nothing.
Now my biggest fear is to re-install Exchange and import the mailboxes manually.
Any help is greatly appreciated.
MattLok

Hello
check role asigment for your user:
Get-ManagementRoleAssignment -GetEffectiveUsers | Where { $_.EffectiveUserName -Eq "administrator" }
sorry my english

Exchange 2013 CU 2 - Cmdlet cancelled. Cmdlet New-MoveRequest

Similar Messages

Maybe you are looking for