Error after a move mailbox

Exchange 2010 sp3, 2 hubs, 2 mbs
i'm moving several mailboxes to a lower db size limit and have encountered the following error:
Warning: Failed to clean up the source mailbox after the move.
Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)
so far, I have three mailboxes that gave that error. all of them returned 100% completed but with warning.
should I continue the move of mailboxes?
I have seen that many times in Exchange 2010.
If the mailbox is successfully moved and users can connect to the new mailbox, I would continue.
You should be able to see the source mailbox as disconnected on the source database:
http://technet.microsoft.com/en-us/library/bb232039(v=exchg.150).aspx
Disconnected Mailboxes
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Similar Messages

OWA Error after Exchange 2010 Mailbox move to 2013

Hello,
We have been experiencing an issue when we move a users mailbox from Exchange 2010 on-prem to Exchange 2013 on-prem. As a domain admin I was able to access the users mailbox via OWA 2010 with out issues. However, now that they have been
moved over to 2013 I am getting the following error message:
X-OWA-Error: SDServerErr;Microsoft.Exchange.Data.Storage.AccessDeniedException
X-OWA-Version: 15.0.995.28
X-FEServer: CASServer
X-BEServer: Mailboxserver.domain.com
Date: 1/29/2015 5:27:38 PM
Full Access permissions appear on the mailbox still via the 2013 ECP console for my account. I have tried running the
Set-Mailbox UserName -ApplyMandatoryProperties command but receive a message that no settings have been modified.
I have also tried to remove/re-add inheritable permissions on the users AD account to no avail.
I have a large group of mailboxes to move over to 2013 and hoping their is a decent solution out there to prevent this from happening.
Greatly appreciate any feedback on this request.
Cheers

Hi,
Please re-add the full access permission for the administrator:
Get-Exchange Server "servername" | Get-Mailbox | Add-MailboxPermission -User Administrator -AccessRights FullAccess
If Administrator is still located in Exchange 2010 and has the full access permission to an Exchange 2013 mailbox ([email protected]) which is moved from Exchange 2010, please use the following URL to open the mailbox:
https://Exch13.domain.com/owa/[email protected]/
Then check whether the issue persists.
Regards,
Winnie Liang
TechNet Community Support

Move mailbox from exchange 2010 2003 , Transient error MapiExceptionLogonFailed has occurred.

We are currently migrating from Exchange 2003 to Exchange 2010, same domain.
We have successfully moved some mailboxes from exchange 2003 to exchange 2010 without any problems.
Now we need to move 1 mailbox back from exchange 2010 to exchange 2003.
After creating the moverequest it stucks on 0% and the log shows the error below.
After using Bing I found this post -> http://social.technet.microsoft.com/Forums/exchange/en-US/ef41ae05-8816-4c0c-968a-c48f0e3d50b5/move-mailbox-back-from-exchange-2010-to-exchange-2003-failure?forum=exchangesvrdeploylegacy
This suggest ->
After I give FULL permissions to each Mailbox Stores on Exchange 2003 server, I was able to move my mailbox back onto the Exchange 2003 server. In details:
Simply right click Storage Group\Mailbox Store and go to Security, in there you may see Exchange Servers group already there, if no add it in, then give it FULL permissions! and thats it!
Create a new move request but still stuck on 0% and error as below
20-3-2014 16:32:10 [ex2010p11] 'contoso.com/Users/exadmin' created move request.
20-3-2014 16:32:11 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'exchangep21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:11 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:11 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:11 [ex2010p21] Request processing started.
20-3-2014 16:32:11 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (1/60).
Error details: MapiExceptionLogonFailed: Unable to make connection to the server. (hr=0x80040111, ec=1010)
Diagnostic context:
Lid: 13720 dwParam: 0x6D9 Msg: EEInfo: Flags: 0
Lid: 11672 dwParam: 0x6D9 Msg: EEInfo: NumberOfParameters: 4
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp
Lid: 8856 dwParam: 0x6D9 Msg: EEInfo: prm[1]: Unicode string: ex2003
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[2]: Long val: -545057711
Lid: 12952 dwParam: 0x6D9 Msg: EEInfo: prm[3]: Long val: 382312662
Lid: 45169 StoreEc: 0x824
Lid: 44273
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 56945
Lid: 59431 EMSMDB.EcDoConnectEx called [length=163]
Lid: 34855 EMSMDB.EcDoConnectEx returned [ec=0x3F2][length=56][latency=0]
Lid: 59505 StoreEc: 0x3F2
Lid: 52465 StoreEc: 0x3F2
Lid: 60065
Lid: 33777 StoreEc: 0x3F2
Lid: 59805
Lid: 52209 StoreEc: 0x3F2
Lid: 56583
Lid: 52487 StoreEc: 0x3F2
Lid: 19778
Lid: 27970 StoreEc: 0x3F2
Lid: 17730
Lid: 25922 StoreEc: 0x3F2
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName,
Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize, Client xropClient, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMapiStore(String serverDn, String userDn, String mailboxDn, Guid guidMailbox, Guid guidMdb, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag
storeFlags, CultureInfo cultureInfo, Boolean wantRedirect, String& correctServerDN, ClientIdentityInfo clientIdentity, String applicationId, Client xropClient, Boolean wantWebServices, Byte[] clientSessionInfo, TimeSpan connectionTimeout)
at Microsoft.Mapi.MapiStore.OpenMailbox(String serverDn, String userDn, String mailboxDn, String userName, String domainName, String password, String httpProxyServerName, ConnectFlag connectFlags, OpenStoreFlag storeFlags, CultureInfo cultureInfo,
WindowsIdentity windowsIdentity, String applicationId)
at Microsoft.Exchange.MailboxReplicationService.MapiUtils.OpenSystemMailbox(Guid mdbGuid, String serverDN, String dcName, NetworkCredential cred, String& systemMailboxDn)
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.OpenSystemMailbox()
at Microsoft.Exchange.MailboxReplicationService.LocalMailbox.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncStateStr)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass57.<Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState>b__56()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.Microsoft.Exchange.MailboxReplicationService.IMailbox.SaveSyncState(Byte[] key, String syncState)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.ClearSyncState()
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<>c__DisplayClass23.<CleanupOrphanedDestinationMailbox>b__22(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CleanupOrphanedDestinationMailbox(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IMailbox.SaveSyncState
OperationSide: Target
Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)
Key: F2FA63B0116C564EA4C598D69786443D9E4FB582FF27D2449142F949D567E1E7E0CA914F6695624C98892FA527AAA91E
SyncStateLength: 0
20-3-2014 16:32:41 [ex2010p21] The Microsoft Exchange Mailbox Replication service 'ex2010p21.contoso.com' (14.3.151.0 caps:07) is examining the request.
20-3-2014 16:32:41 [ex2010p21] Connected to target mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'ex2003\Basic\Basic', Mailbox server 'ex2003.contoso.com' Version 0.0 (Build 7638.0).
20-3-2014 16:32:41 [ex2010p21] Connected to source mailbox 'Primary (82b54f9e-27ff-44d2-9142-f949d567e1e7)', database 'EX2010DB', Mailbox server 'ex2010p20.contoso.com' Version 14.3 (Build 174.0).
20-3-2014 16:32:41 [ex2010p21] Request processing started.
20-3-2014 16:32:41 [ex2010p21] Transient error MapiExceptionLogonFailed has occurred. The system will retry (2/60).

Hello，
When you move mailbox from exchange 2010 to exchange 2003, please check if the following situations exist:
http://technet.microsoft.com/en-us/library/dd638157(v=exchg.141).aspx
Before you move mailbox again, please clear the previous move request.
I recommend you use EXBPA to check your exchange server 2003 and exchange 2010.
Please check if inheritable permission is missing on the mailbox store on Exchange Server 2003.
Cara Chen
TechNet Community Support

Mailbox move completes but get "Failed to reset the target mailbox after the move" 481/481

moving a mailbox from exchange 2013 to exchange 2010: it completes but the process tries to reset the target mailbox as a final step about 481 times then gives permanent exception error:
Failed to reset the target mailbox after the move. Attempt 481/481. Error: SuitabilityDirectoryException
Target mailbox reset operation was not replicated. Error: TargetMailboxConnectionWasLostPermanentException
Anand_N

I have tried moving several different accounts, none of them admin accounts, all getting the same error. I am logged in as domain admin with full rights to exchange. The issue occurs when moving mailboxes from exchange 2013 to exchange 2010.
1/30/2014 7:24:56 AM [e1] Move has completed and final clean up has started.
1/30/2014 7:24:57 AM [e1] Source mailbox 'Primary (4bfda0fd-c991-4d40-8f0f-394411ef6848)' was successfully cleaned up after the move.
1/30/2014 7:24:57 AM [e1] Failed to reset the target mailbox after the move. Attempt 1/481. Error: CouldNotFindDCHavingUmmUpdateTransientException.
1/30/2014 7:24:57 AM [e1] Post-move cleanup failed. The operation will try again in 30 seconds (1/481).
1/30/2014 7:25:32 AM [e1] Failed to reset the target mailbox after the move. Attempt 2/481. Error: SuitabilityDirectoryException.
1/30/2014 7:25:32 AM [e1] Post-move cleanup failed. The operation will try again in 30 seconds (2/481).
This is four hour wait period. before getting the error :
Target mailbox reset operation was not replicated. Error: TargetMailboxConnectionWasLostPermanentException
Anand_N

Warning: Failed to clean up the source mailbox after the move

Hi!
After moving a mailbox between databases (EMC or EMS), there is a warning: Warning: Failed to clean up the source mailbox after the move. Erro details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634).
Users can successfully access mailboxes, but these mailboxes stay in disconected mailbox node on EMC, and it is shown on EMS afer command [PS] C:\> Get-MailboxDatabase | Get-MailboxStatistics | where {$_.DisconnectReason -ne $null} and their databases are
the old ones.
We have recently upgraded from SP2 to SP2 RU4, but we´re not sure when this problem started.
Our Environment:
Windows Server 2008 R2 Enterprise SP1
Windows Roles: File Services, Web Server (IIS)
Exchange Server 14.02.0318.001 (Build 247.5) Roles MBX, DAG with one more MBX identical Server
Antivirus: Forefront Endpoint Protection Version: 2.1.1116.0
Virtualization: Yes – Hyper-V
Applications: Backup Agent CA, SCCM Agent, SCOM Agent, HP Management Tools
Any idea?
Thankyou in advance!
Fabio Martins MCDST/MCSA Brasil!!!

I recently upgraded our Exchange 2010 servers (CAS/HUB and MBX) from SP1 to SP3 RU6 and now I'm encountering this issue when doing mailbox moves. I opened a support case with Microsoft and it appears that they are aware that SP 3 RU1 doesn't fix
the issue in all cases. Below is the response I received from the support engineer.
=====
Based on my research and case experience, we have several customers report that even if they are running Exchange 2010 SP3 RU1 or later version(for example, one of customer is running Exchange 2010 SP3 RU4 and another is also in CU6 environment), they also
have such issue. When they move mailbox, it completed with warning message that source mailbox can’t be cleaned up after the mailbox move operation. This issue occurs because the Mailbox Replication service does not check a certain flag when you move the mailbox.
Additionally, a move process for a mailbox that fails takes 30 seconds by default. When a move process for a mailbox fails, the Mailbox Replication service tries five more times to move the mailbox. Therefore, there is a 2.5 minute delay for each mailbox move
process when you move many mailboxes at the same time.
Currently, the workaround is to remove the “SoftDeleted” mailboxes manually after move the mailbox using the command you shared to us.
==========================================
1. List all disconnected mailboxes in a database and display DisconnectReason if its SoftDeleted or Disabled
Get-MailboxStatistics -Database "DB9" | Where-Object {$_.DisconnectDate -Notlike $NULL} | Format-Table DisplayName, DisconnectDate, MailboxGuid, DisconnectReason –Wrap
2. Remove a specific softdeleted mailbox
Remove-StoreMailbox -database “DB9” -identity “User Alias here” -MailboxState SoftDeleted
==========================================
And as I know, it has no impact on the mailbox usage, so we can ignore the warning message currently. Please rest assured that once we got more information about the issue, we will inform you ASAP.

Move Mailbox error

Hello,
I tried move mailbox from 2010sp3 to 2013sp1.
All mailboxes seem ok except 2 mailboxes.
1. One mailbox error message is "Error: MigrationPermanentException: Mailbox 'XXXX' has a completed move request associated with it. Before you create a new move request for the mailbox, run the Remove-MoveRequest cmdlet to clear the completed move
request.
I use exchange powershell type"get-moverequest" and I can't find any list.
2. Another mailbox error message is"Error: MigrationPermanentException: The Mailbox database "YYYY" is not the same version as the cmdlet.
All mailboxes are from same database"YYYY", only one mailbox have this message.
Thanks

Hi Newbee,
Thank you for your question.
Issue one:
We could refer to the following steps to check if the issue persist:
Restart the service of “Microsoft Exchange Information Store” on Exchange 2010 and Exchange 2013
Run the command of “Get-MoveRequest” to check if we could get list
Check other mailboxes if it work which move from Exchange 2010
If we could get list by Get-MoveRequest, we could run the following command:
Get-MoveRequest | where {$_.status -eq “Completed”} | Remove-MoveRequest
Issue two:
There are some steps we could refer to:
Run the move-request for this specific user again
Make sure source and target database without any problems
Change move ways to check if the issue persist, for example EAC or EMS
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

Exchange 2013 - can no longer move mailboxes from Exchange 2010 to Ex 2013.

Migrating to Exchange 2013 from Exchange 2010. Created Ex 2013, moved some mailboxes OK. Then could no longer move mailboxes. No errors. The Migration email says complete. Synced: none, Total Mailboxes: none.
Tried several mailboxes. Same result.
Ex 2010 is SP3 RU6, (at least it says RU6 is installed in Programs/Features. The build is for SP3 w/o RU6???)
Ex 2013 is SP1 aka CU4.
How to proceed???
john11

After many attempts to fix the issue (move remaining 4 mailboxes from Exchange 2010 to Exchange 2013) I contacted Microsoft and we resolved the issue. Here's how.
btw - Thanks for the suggestions from Ed. However, they did not seem to move us forward.
What did work:
1. On the Exchange 2010 box, create a new database. (Someone else suggested this also). Then move the remaining Exchange 2010 mailboxes to this new db. Then after that, move the 4 mailboxes to Exchange 2013 using the GUI on Ex 2013. This only worked for one
of the four mailboxes. The other 3 failed.
2. Apparently, we need to restart the Microsoft Exchange Mailbox Replication service on the Exchange 2013 after several failed move attempts to clear cache related to the moves.
3. Then on the Exchange 2013 box, use this Exchange shell command:
New-MoveRequest -identity "[email protected]" -TargetDatabase "Exchange 2013 DB name" -BadItemLimit '500' -verbose
This moved the remaining 3 mailboxes including the Discovery mailbox. It took some time. But we could check the progress using
Get-MoveRequest
The MS Tech was terrific. Really knew his stuff. And all mailboxes are on Exchange 2013. Well, the last one is still moving, but I am optimistic.
Thanks for the suggestions. I had to get this done and the MS Tech made that happen.
john11

Restore Exchange DB after Recreation of mailboxes to New Exchange(low priority)

Hello to Everyone
Recently one client of mine had a problem with an exchange migration that he tried (2010 to 2013) and he needed to restore his old EDB from windows backup to restore 10 Mailboxes that he had already migrated. We run the whole procedure with eseutil,
ISINTEG etc. The problem was that the client had already deleted the mailboxes and the AD Users and recreated them on a new database. When I tried to export or move the mailboxes the Power Shell reported unknown error and as I understood tried
to Read from active directory GUID and couldn't find the same and Stopping.
We solved the problem with the OST to PST files relied on the computers but I would like to hear from your experience if we had other Alternatives?
I could think only to restore Exchange and the domain controller on a VLAN so they have the same AD Objects and then Export all mailboxes to PSTs and then Re import them to the New Exchange Server.
Thank you
Alexios

Not sure the steps you took, however based upon your brief explanation it sounds as though you were able to restore and rollup the logs using eseutil, correct?
Did you then use the RDB process to mount this DB onto an Exchange 2010 Server?
Assuming the above is correct you should then be able to restore the mailbox from the source DB into a temporary user mailbox as outlined here
http://technet.microsoft.com/en-us/library/ee332351%28v=exchg.150%29.aspx
If the above doesn't work for you the other option would be to use a 3rd party tool like Lucid8's DigiScope
http://www.lucid8.com/product/digiscope.asp which would allow you to easily open the Offline 2010 EDB to see all the mailboxes and their contents. You can then easily export to PST or directly
recover/migrate data from the offline 2010 EDB into the 2013 Production Exchange Server
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope
1. Yes Troy that is correct. I soft repair the db but it was continuing to be in dirty state. So I hard repaired it and came to a clean state.
2. I then Created a recoveryDB and tried to move mailboxes to temp mailboxes or export mailboxes etc.
3. There was no luck with the above, the power-shell reported that the mailbox GUID has changed and don't match with the AD signature, I am thinking this is probably because the client has already recreated all the mailboxes to a new db with the same
usernames-mails. In the end and after one day of tries I recommended a third party tool that I tried and I have seen that finds all the data of the mailboxes or if we have the OST of the users to convert them to PST. They used the second suggestion with OST
and I restored everything.
I posted this problem for brainstorming and if anyone else had the same problem or might have an idea why this happened. :)
Thanks

IOS 4 Error: "Unable to Move Messages" when Deleting Multiple Messages

Using an iPhone 4 and IOS 4.x (all versions to date including 4.1) if I'm in the All Inboxes view and use Edit to select multiple messages from more than one Exchange account and then delete them I get the following error:
Unable to Move Messages
The messages could not be moved to the mailbox Trash.
Deleting multiple messages from a single Exchange account is fine, but when selecting messages from more than one account the message pops up as many times as messages I'm trying to delete. I currently have three Exchange accounts on both 2003 and 2007 servers. This issue persists across multiple iPhone 4s as well as after a complete restore and manual setup of the Exchange accounts from scratch.

Not sure if this will work for the first poster, but it might for you, Busta999.
I have my email set up as an IMAP account and was getting the same "unable to move..." message for individual deletions. I suspected the problem for me had to do something with the trash bin on the phone and the trash bin on the server not communicating properly. I tried this and it worked for me, although from other posts, I see it doesn't work for everyone:
1. Go to "Settings"
2. Select "Mail, Contacts, Calendars"
3. Select the mail account in question
4. Select "Account Info"
4. Select "Advanced"
5. Select "Deleted Mailbox"
6. Under "On My Server", Click the "Trash" folder (or whatever your trash folder is called on your server). This should put a check mark beside it.

Can't connect via outlook after remote move request.

Hi All,
i want to ask something about outlook connectivity,i was do remote move request from different forest. after move request completed, i try login the account
using ms outlook 2010. but got some error like this, "Cannot open your default e-mail folders. You must connect to Microsoft Exchange with the current profile before you can synchronize your
folder with your outlook data file (ost)."
if i try login using OWA, its successful,
i was enable/disable MAPI from this mailbox, but not the solution. finding in google, i found this
link . but not the solution.
anyone have some experience with my trouble?.
thanks in advance.

Hi Rambosality,
According to your description, I understand that outlook cannot connect to Exchange server with error “Cannot open your default e-mail folders. You must connect to Microsoft Exchange with….” When move mailbox.
I want to double confirm some points, please help to collect answers for following question:
1. All account or some special account experience this issue?
2. How about re-create Outlook profile for test?
Please try to use Test-OutlookConnectivity and Test-OutlookWebServices test end-to-end Microsoft Outlook client connectivity, availability service and etc. More details for this command, please refer to:
http://technet.microsoft.com/en-us/library/dd638082(v=exchg.141).aspx
http://technet.microsoft.com/en-us/library/bb124509(v=exchg.141).aspx
Additional, I find an article about RPC Client Access Cross-Site Connectivity Changes. It discuss about RPCClientAccessServer setting after move mailbox cross-site, for your reference:
http://blogs.technet.com/b/exchange/archive/2012/05/30/rpc-client-access-cross-site-connectivity-changes.aspx
Best Regards,
Allen Wang

Error during Exchange 2007 mailbox provisioning with IDM 8.1.1.1

Hi
We want to create Exchange 2007 mailboxes from IDM.
When we let Exchange set the SMTP address (EmailAddressPolicyEnabled=true), it works fine
But when we set the SMTP address in IDM with the attribute PrimarySmtpAddress (and EmailAddressPolicyEnabled=false) there are an error and an information in the provisioning task
Error : PowerShell:6c13f14c-3825-4064-a585-48b4756de3a3 is not a mailbox user
Information : Added exchange mailbox to the user based on the RecipientType change from: 'User' to: 'UserMailbox'
We see that the mailbox has the SMTP address set by Exchange.
After 5mn, the task ends successfully and we see that the SMTP address is the one set by the IDM attribute PrimarySmtpAddress.
We guess that this error is caused by the active directory replication delay between controllers.
Does anybody know how to solve this problem ?
Thank you

Hi Patrick
Thank you for your answer.
The cmdlet enable-mailbox can be used with the PrimarySmtpAddress option and, in this case, the EmailAddressPolicyEnabled option is automatically set to false.
Cf. the MS technet help : "The PrimarySmtpAddress parameter specifies the primary SMTP address for the mailbox. By default, the primary SMTP address is generated based on the default e-mail address policy. If you specify a primary SMTP address by using this parameter, the command sets the EmailAddressPolicyEnabled attribute of the mailbox to $false, and the e-mail addresses of this mailbox aren't automatically updated based on e-mail address policies."
I have tested this option on our Exchange 2007 environment and it works fine.
In IDM if PrimarySmtpAddress is used but not EmailAddressPolicyEnabled, there is an error : "PowerShell:The e-mail addresses for this recipient are automatically generated based on e-mail address policies. To modify the primary SMTP address for this recipient, you must disable automatic updating of e-mail addresses based on e-mail address policy”
If PrimarySmtpAddress is used and EmailAddressPolicyEnabled is set to false, then the log shows that 2 powershell commands are run by the gateway, the second immediately after the first.
Enable-Mailbox with the parameters -Identity and -Database, run with no error
Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with the error “…is not a mailbox user.”
After 5 mn (the retry delay) another powershell command is run :
Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with no error.
The solution would be that IDM, when PrimarySmtpAddress is set, runs only the command Enable-Mailbox with the parameters PrimarySmtpAddress, which set automatically EmailAddressPolicyEnabled to FALSE
Gilles

Strange Data Mapping Errors after SEM 6 Upgrade. Please assist.

Hi All, I encountered these sudden Mapping errors after I tried to do Testing in Post Upgrade Sand Box. Here I am trying to to perform Collected Reported Financial Data under Data Collection Method for a particular Company Code 3040. Kindly help me with some quick responses as this is kind of high priority. The errors and the Diagnosis Notes I am unable to follow as I do not where I shall write those Mapping Rules they are referring to. I do not even know if that need to apply any SAP Notes as such. Once again Highly appreciate your quick response and Many Thanks in Advance.
Regards, BIP
Input conversion for field Period Value LC has invalid format Message no. UCT8210 Diagnosis The mapping rule for target field Period Value LC contains a move with a selected Input Conversion indicator. Therefore, the system performs an input conversion prior to creating the target data. However, an error in the input conversion occurred while moving the source key figure to the target key figure Period Value LC. This means that the format used for the input conversion is incompatible with the target data. System Response The system will not perform the move. Procedure Examine the mapping rule for field Period Value LC. Either select the Conversion Exit indicator or deselect the Input Conversion indicator. Execute the method again. -
3040 is incompatible with input format for field /1FB/COMPANY Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field /1FB/COMPANY from the mapping rule for the target field. 3040 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field /1FB/COMPANY. However, the value 3040 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 3040 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field /1FB/COMPANY. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field /1FB/COMPANY. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field /1FB/COMPANY. If incorrect values were selected, make sure that the mapping rule used by source field /1FB/COMPANY has been defined correctly. If the mapping rule is correct and value (3040) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 3040 for field /1FB/COMPANY and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field /1FB/COMPANY, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field /1FB/COMPANY is unsatisfactory: You can define a source selection for field /1FB/COMPANY in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field /1FB/COMPANY. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule. -
Cannot derive the source selection from target field Version Message no. UCT8252 Diagnosis Field Version has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Version. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Version. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Versionthrough mapping), choose one of the alternatives below: Change the mapping rule for field Version so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Version. -
Cannot derive the source selection from target field Group Currency Message no. UCT8252 Diagnosis Field Group Currency has one of the following roles: Consolidation unit Group currency key Fiscal year Posting period Version To delimit the volume of the source data to be read, the system usually derives the source selection from the target selection of such a field. However, the system cannot derive a source selection from field Group Currency. System Response It is possible that a greater volume of source data is being read than is necessary. This can lead to performance issues. Procedure Check whether a mapping rule is defined for field Group Currency. If a mapping rule is defined, you can disregard this warning message. However, if you discover after method execution that the system did not process a large amount of data, and that system performance was not satisfactory, you may want to examine the source selection by choosing the Source button in the log. If the reason for the disregarded data is that too much source data was read because of the unrestricted selection on the source field (which is linked with target field Group Currency through mapping), choose one of the alternatives below: Change the mapping rule for field Group Currency so that the system can derive a delimiting source selection. Implement the Business Add-In (BAdI) UC_DATATRANSFER with the method INVERT to delimit the selection for the source field that is linked via mapping to the target field Group Currency
1 is incompatible with input format for field FISCPERIOD Message no. UCT8258 Diagnosis During execution, the method derives the source selection for source field FISCPERIOD from the mapping rule for the target field. 1 is one of the values that were derived for the source selection. The system requires that this value is in the correct SAP-internal format because the Conversion Exit indicator has been selected in the move operator for field FISCPERIOD. However, the value 1 is incompatible with the SAP-internal format. System Response The system attempts to interpret value 1 as an external format and convert it to the internal format. If this fails, the system is unable to restrict the source selection using source field FISCPERIOD. In this case, the system may read more source data than was originally intended, which can affect performance. Procedure In the log, choose the Source button to display the source selections that are used to read the source data. When this appears, examine values selected for field FISCPERIOD. If the correct values were selected, you can ignore this message. To prevent this message from being issued, you can select the indicator in the mapping rule used by source field FISCPERIOD. If incorrect values were selected, make sure that the mapping rule used by source field FISCPERIOD has been defined correctly. If the mapping rule is correct and value (1) derived for the source selection does not affect the overall result, you can ignore this message. If the source selection does not contain the value 1 for field FISCPERIOD and, because of this, source data that is supposed to be read is not being read, make sure that the mapping rule has been defined correctly. If the source selection does not contain any value for field FISCPERIOD, make an estimation as to how much excess source data is being read and whether this might affect system performance. If you do not expect any performance problems, you can ignore this message. In any event, you have the following alternatives if the mapping rule is defined correctly, but the source selection on field FISCPERIOD is unsatisfactory: You can define a source selection for field FISCPERIOD in the Customizing settings for the method on the Selection tab page. Then the method uses this source selection instead of the source selection derived from inverse interpretation of the mapping rule. You can implement the Business Add-In (BAdI) UC_DATATRANSFER and use the method INVERT to determine the source selection on field FISCPERIOD. Then the method uses the result of the INVERT method for the source selection instead of the source selection derived from inverse interpretation of the mapping rule
Input must be in the format ___,___,__~ Message no. 00088 Diagnosis Your entry does not match the specified input format. System Response The entry in this field was rejected. Procedure The entry must comply with the edit format. The following edit format characters have a special meaning: "_" (underscore) There should be an input character at this point; this should be a number for numeric fields. "." (decimal point) (applies to numeric fields) The decimal point occurs here (setting in the user master record). "," (thousands separator) (applies to numeric fields) This separator occurs (optionally) for more than three figures. Depending on the setting in the user master record, it can be a period or a comma. "V" (applies to numeric fields) The operational sign appears here. If used, it must by at the right margin of the field. The sign is either "-" or " "(space). "~" (tilde) (applies to numeric fields) As of and including this character, leading zeros must also be entered. Otherwise, this character has the same meaning as an underscore. Leading zeros need not be entered on the left of the tilde. They are not output at this position. All other characters have their normal meanings and must be entered in the same position as in the edit format.

Hi Dan,
Could you Kiindly advise me where we need to write the Mapping Rules in Consolidation Monitor? All he time the errors refering to Mapping Rules. The only Tab I seen "Mapping" is in Data Basis But as per my Understanding Iwe do not have much to do there as it is system generated Mapping Tab.
Where we actually go and select/deselct those Input Conversion Indicator/ Conversion exit Indicator.
Highly appreciate your advise.
Thanks and Regards,
BIP

Error: MigrationPermanentException: Warning: Target mailbox unlock

Hi,
I'm migrating some users from one Exchange 2013 SP1 CU6 database to another one. Some users fail with warnings:
Error: MigrationPermanentException: Warning: Target mailbox unlock operation was not replicated. If a lossy failover occurs after the target mailbox was unlocked, the target mailbox could remain inaccessible. Error
details: Mailbox changes failed to replicate. Database doesn‎'t satisfy the constraint SecondCopy because the commit time 7/12/2014 4:22:54 PM isn‎'t guaranteed by replication time 7/12/2014 4:14:25 PM.
Part of the problem is likely that on the passive DAG member, the Microsoft Exchange Migration Workflow service keeps crashing and restarting.
I migrated probably 300 users no problem prior to CU6 (we were on CU4/SP1), this issue now happens on 1/10 migrated users. As far as I've seen, this causes the users no issues what so ever, however I haven't had a fail over to the passive DAG member since
these migrations.
Simply re-running the migration jobs don't help. Thinking of CU7 but can't see anything in the release notes mentioning this at all.

Hi,
From your description, I recommend you run the Resume-ClusterNode cmdlet to resume the node from the paused state or brings back drained workloads to the node and check the result.
For your reference:
Resume-ClusterNode
https://technet.microsoft.com/en-us/library/hh847243.aspx
Hope this can be helpful to you.
Best regards,
If you have feedback for TechNet Subscriber Support, contact
[email protected]
Amy Wang
TechNet Community Support

Exchange Server 2010 Move mailbox to database but display MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)

I have 2 exchange server "A" and "B". Server "A" have "Test1" database and Server "B" have "Test2" database. I tried move some mailboxes from "Test1" to "Test2"
but sometimes mailboxes cannot finished and display below error. I used Domain administrator to move mailboxes and grant "Manage full access permission" to these mailboxes but still failed. Finally, I clear the failed move request
and repeat the move mailboxes action several times.  Then, the move request completed without error. Have any suggestion? Please help. Thank you!
Mailbox move for 'xxx.com/xxx/xxx/xxx - Users/xxx/Peter' (331d5b4e-0bd1-428a-ae28-d97581ae0d7f) has failed.
Error code: -2147024891
MapiExceptionNoAccess: Unable to open message store. (hr=0x80070005, ec=-2147024891)
Diagnostic context:
    Lid: 18969   EcDoRpcExt2 called [length=132]
    Lid: 27161   EcDoRpcExt2 returned [ec=0x80070005][length=202][latency=0]
    Lid: 32881   StoreEc: 0x80070005
    Lid: 50035
    Lid: 64625   StoreEc: 0x80070005
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 26426   ROP: ropLogon [254]
    Lid: 56503
    Lid: 12716   StoreEc: 0x80070005
    Lid: 20794
    Lid: 28474   StoreEc: 0x80070005
    Lid: 22330   dwParam: 0x0        Msg: 14.03.0123.002:NHK-S08-MBD02
    Lid: 1750    ---- Remote Context End ----
    Lid: 23354   StoreEc: 0x80070005
    Lid: 25913
    Lid: 21817   ROP Failure: 0x80070005
    Lid: 26297
    Lid: 16585   StoreEc: 0x80070005
    Lid: 32441
    Lid: 1706    StoreEc: 0x80070005
    Lid: 24761
    Lid: 20665   StoreEc: 0x80070005
    Lid: 25785
    Lid: 29881   StoreEc: 0x80070005
Context:
Mailbox: Primary (331d5b4e-0bd1-428a-ae28-d97581ae0d7f)

Hi Gordon
This could happen if there is any mailbox which has occupied more space than its normal quota allocated.
As suggested by geo try to clean all the DB's first
You can probably run Get-Mailboxdatabase | Clean-Mailboxdatabase which will clean all of your DB's wait for some time until it gets completed
Also try running the command with the MRS server parameter switch and specify a CAS FQDN and see the results if it gets succeded
Get-Mailbox -Database 'DBNAME'| New-MoveRequest -TargetDatabase DBNAME -BatchName "BATCHNAME" -BadItemLimit 100 -AcceptLargeDataLoss -MRSserver CAS server FQDN Good Luck !!Please mark as helpful if you find my contribution useful or as an answer if it does answer your question.That will encourage me - and others - to take time out to help you.
Regards,
Sathish

HT1657 Tried to rent movie but saying error cannot download movie at this time?

Tried to download a rental the other day when trying to download it said I did not have enough space when I did this is due to my iPad having an expired previously rented movie.
Still after this had gone it was saying I did not have enough space. I reset my iPad to then hopefully start downloading my rental and it is now saying error cannot download movie at this time?
Help.
Thanks

you need to change the device time: http://techsultan.com/installing-emulators-on-ios-without-jailbreak-emu4ios-meth od/

Error after a move mailbox

Similar Messages

Maybe you are looking for