Exchange 2010 EvenID 2070, LDAP connects to demoted AD server

Running Exchange 14.3.224.4002 on Server 2008R2 SP1.
Every 20 minutes i see this Event appearing in my application logs:
Process MSExchangeMailboxReplication.exe () (PID=4116). Exchange Active Directory Provider lost contact with domain controller <demoted.domain.controller> Error was 0x51 (ServerDown) (Active directory response: The LDAP server is unavailable.).
Exchange Active Directory Provider will attempt to reconnect with this domain controller when it is reachable
Demoted this server as documented with DCPROMO. All DNS records from this server are removed a long time ago and Exchange was restarted several times. Performed a succesvol DCDIAG /test:dns. Even
did the rename trick on C:\Users\<username>\appdata\roaming\microsoft\mmc\Echange Management Console. Can someone please shine some light on this?

Hi,
This error indicates that the DC was closing the LDAP connection. I suggest to set the following registry value to 2 in order to increase the logging level on the DC for discovering this issue.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Diagnostics\16 LDAP Interface Events
After this step, DC will start generating other events every time it disconnected Exchange. Please collect and post these events for troubleshooting.
Refer to this blog for more information
http://blogs.technet.com/b/bill_long/archive/2014/03/19/ldap-send-queue-limits-cause-event-2070-and-2084.aspx
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]
Lynn-Li
TechNet Community Support

Similar Messages

After recover of Exchange 2010 hub; Outlook not connecting

Exchange 2010 sp 3, Windows Server 2008 R2 sp1
one of my hub (1 of 2) server failed this morning (no thanks to KB2993651) so in a fit of hurry, i reformatted the server,
deleted the computer account from AD and reinstalled Windows Server 2008 R2 sp1. here is what i did to recover:
from the command line of the server: netsh int tcp set global chimney=disabled; netsh int tcp set global rss=disabled
HKLM\System\CurrentControlSet\Services\Tcpip6\Parameters -> DWORD-32 (DisabledComponents) with a value of 0xffffffff
made the server a member of "Exchange Install Domain Servers", "Exchange Trusted Subsystem", "Exchange Servers"
and then i issued the command: setup /m:recoverServer
it went fine well. i also joined it back to Windows NLB cluster.
but when it's online, some Outlook users aren't able to connect. OWA also fails. i can't figure out what's wrong so for now i shutdown the server and am using only one Hub server.
maybe i missed a step? appreciate any help.
EDIT: in the same hub server was my DAG witness folder. i don't know if this has implications now that i lost the DAG witness server (this hub server)

Did you try starting the server after connecting to network ?
You could try starting the server after connecting to network and import the certificate and configure the same URLs as per my first post. You cannot open EMS and EMC if you start without network connection.
Use this URL to get the command to request new certificate. After running this command in EMS you will see a new request https://www.digicert.com/easy-csr/exchange2010.htm
For installing certificate please check thishttps://www.digicert.com/ssl-certificate-installation-microsoft-exchange-2010.htm.
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.

IOS 4.3.1 + Exchange 2010 "was" fine with the mailbox on Ex2007 server

Hi,
i had used my iphone with ios 4.3.1 and active sync.
The mailbox was hosted on the old exchange 2007 server.
A new exchange 2010 server was running the last 4 weeks and the iphone was connection with activesync against the new exchange 2010 through local wlan and over internet.
After i moved my profile to the new server i can´t connect anymore to the new server!
Any idea what happend?

It was working fine the last weeks with my mail account sitting on exchange 2007.
Today i moved several mailboxes from exchange 2007 to 2010 SP1.
I have some domain accounts that are created new and had their mailbox created on the exchange 2010 sp1 system.
With these accounts i can connect and retrieve mails.
But with my account (moved from 2007 to 2010) i can´t.
All i get is a blank mailbox on my iphone.
I even removed the mail account from my iphone and recreated the account.
But it won´t retrieve mails.
I refresh the offline addressbook at the exchange 2010 but nothing will help.
Message was edited by: juergenb52

Q10, Exchange 2010 ActiveSync - Email will not be deleted on server

Hey Everyone,
If you have a Q10 with Exchange ActiveSync, can you remove emails on the server using "Delete from Hub and server" option??
I am testing this function both with an ipad and Q10. Emails removed from Ipad are removed from Exchange Server whereas emails removed from Q10 with "Delete from Hub and server" option selected are only removed from Q10 but not on the server.
Is this a broken functionality or are there incorrect settings on the phone?
Any help is greatly appreciated!
-T

the deletes can take a few on my Z30 or Z10
I know a quick delete would be prefered but maybe the OS deems them as not fast needed
Click here to Backup the data on your BlackBerry Device! It's important, and FREE!
Click "Accept as Solution" if your problem is solved. To give thanks, click thumbs up
Click to search the Knowledge Base at BTSC and click to Read The Fabulous Manuals
BESAdmin's, please make a signature with your BES environment info.
SIM Free BlackBerry Unlocking FAQ
Follow me on Twitter @knottyrope
Want to thank me? Buy my KnottyRope App here
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V

Exchange 2010 - Outlook is dropping connections to Exchange servers

Hello Everyone,
I need some help in an urgent case that I'm dealing with.
We are running Exchange 2010SP3 with RU4, using external load balancer (F5).
This morning we got complains from any single user on our system telling that their Outlook clients is showing "Disconnected" or "Trying to connect" status.
First thing that we checked was if their mailboxes are accessible from OWA - the answer is yes.
Connection status is starting with "Connecting" then dropped.
We thought maybe it is coming from one of the CAS servers, so we started by removing each of the two servers at a time, but this helped only for few minutes, OWA was accessible and Outlook could connect to the servers, after few minutes, the connection was
dropped again.
MS Remote Connectivity checks are passing so it is even unclear because we are failing to see what and where is the real issue.
No errors on the hosts.
Any advice here? We have 300 disconnected users.

Do the Outlook clients connect through the F5 as well?
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

LDAP connection with windows catalogue server

Hi Gurus,
I want your help for below issue
Requirement is there is one customized table which will be accessed by SM30, user will enter user id and its email address should come automatically from windows global catalogue server(Non-SAP system), For this i referred one doc attached below
http://santy.wdfiles.com/local--files/sap-pages/SAP_User_Mgmt_Via_LDAP.pdf
According to this seems RFC creation, LDAP connector configuration, and LDAP server configuration required in SAP, i have asked basis team to do the same.
Now my question is is this the responsibility of Basis team to configure LDAP connector and LDAP server also how i can access LDAP directory through ABAP program?
please help me step by step if possible.

Reinfire,
I tried your terminal window patch but it failed to solve my issue. Most people seem to be trying to connect to NAS devices from their Macs. In my case, all my data is on a Drobo hanging off my Mac Pro. I've been using SMB to share video from my Mac to both a Boxee Box and a Raspberry Pi running Openelec (XBMC). While both these devices can handle afp, the old Boxee Box is less than astute with afp so SMB was the method of choice for stability.
Anyway, both devices can no longer see the SMB shares off the Mac Pro, even after your patch. After runnig you patch, I restarted and the nsmb.conf file is created. But, no luck on connecting with these apparently non SMB2 devices.
I can change all my shares over the afp but this will take a lot of button pushing that I'd rather not do. Any suggestions for this scenario?

Internal outlook client connectivity in exchange 2010 when coexist with exchange 2013

Hi all ,
on my side i would like to clarify few queries.
Say for instance i am coexisting exchange 2010 with exchange 2013 .Unfortunately if all of my exchange 2013 servers goes down .
Q1 .On that time will the internal outlook users having their mailboxes on exchange 2010 can be able to connect mailboxes without any issues ? In case if they face any issues what kind of issues will they be? Because why i am asking is we should have pointed
the autodiscover service to exchange 2013 during coexistence.
When an user closes and reopens the outlook after whole exchange 2013 environment failure ,outlook will first query the autodiscover service for the profile changes to get it updated on users outlook profile.In such case autodiscover service will not be
reachable and i wanted to know will that affects the internal client connectivity for outlook users having their mailboxes on exchange 2010.
Q2. Apart from outlook internal users connectivity ,what kind of exchange services(i.e owa,active sync,pop,external OA and imap) will get affected when whole exchange 2013 environment goes down during coexistence ?
I have read the below mentioned statement on this awesome blog but still i wanted to clarify with you all on my scenario.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx<o:p></o:p>
Internal Outlook Connectivity
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2010, they will still connect to the Exchange 2010 RPC Client Access array endpoint.
For internal Outlook clients using RPC/TCP connectivity whose mailboxes exist on Exchange 2007, they will still connect directly to the Exchange 2007 Mailbox server instance hosting the mailbox.
Please share me your suggestions and that would help me a lot .
Regards
S.Nithyanandham

Hi Winnie Liang ,
Thanks a lot for your reply.
Scenario 1 : for internal outlook connectivity
We have below settings for exchange 2010 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2010 cas serves
We are going to have below settings for exchange 2013 autodiscover.
mail.domain.com - will be the namespace for internal autodiscover URI for all the exchange 2013 cas serves
During coexistence mail.domain.com will be pointed to exchange 2013 cas servers . I mean to say if we try to resolve the mail.domain.com it will get resolved in to the exchange 2013 cas servers.
So on such case if anything happened wrong to the new environment or else if entire environment goes down .Do we face any issues while outlook users connect to existing mailboxes in exchange 2010 ?
Because why i am asking is ,on the below mentioned article i have read all the autodiscover request will go via exchange 2013 cas servers during coexistence.That means all the existing mailboxes in exchange 2010 will also have to query exchange 2013 cas
servers for autodiscover request.During the whole exchange 2013 environemnt failure whenever the user tries to close and open outlook .Outlook will first queries the autodiscover service for any changes happened on that particular mailbox and it will try to
get it updated on user profile.
http://blogs.technet.com/b/exchange/archive/2014/03/12/client-connectivity-in-an-exchange-2013-coexistence-environment.aspx
Would it be possible to make the exchange 2010 mailbox users to query only the scp points which belongs to the exchange 2010 cas servers for autodiscover request ?
Scenario 2: For exchange services
mail.domain.com - will be the namespace for all the exchange 2010 services (i.e owa,activesync,external outlook anywhere,pop,imap)
mail.domain.com - will be the namespace for all the exchange 2013 services (i.e owa,activesync,external outlook anywhere,pop,imap)
What about the above services will it get affected during whole exchange 2013 environment failure ?
Note : We are not facing this issue , i hope everything goes well in my environment while doing coexistence i am just asking this question on my own interest?
Regards
S.Nithyanandham
Thanks S.Nithyanandham

[SOLVED] Can't add a node to the cluster with error (Exchange 2010 SP3 DAG Windows Server 2012)

Hi there!
I have a problem which makes me very angry already :)
I have two servers Exchange 2010 SP3 with MB role started on Windows Server 2012. I decided to create a DAG.
I have created the prestaged AD object for the cluster called msc-co-exc-01c, assigned necessary permissions and disabled it. Allowed through the Windows Firewall traffic between nodes and prepared the File Share Witness server.
Then I have tried to add nodes. The first node has been added successfully, but the second node doesn't want to be added :). Now I can add only one node to the DAG. I tried to add different servers first, but only the first one was added.
LOGS on the second nodes:
Application Log
"Failed to initialize cluster with error 0x80004005." (MSExchangeIS)
Failover Clustering Diagnostic Log
"[VER] Could not read version data from database for node msc-co-exc-04v (id 1)."
CMDLET Error:
Summary: 1 item(s). 0 succeeded, 1 failed.
Elapsed time: 00:06:21
MSC-CO-EXC-02V
Failed
Error:
A database availability group administrative operation failed. Error: The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode()
(MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed. [Server: msc-co-exc-04v.int.krls.ru]
An Active Manager operation failed. Error An error occurred while attempting a cluster operation. Error: Cluster API '"AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired"' failed..
This operation returned because the timeout period expired
Click here for help... http://technet.microsoft.com/en-US/library/ms.exch.err.default(EXCHG.141).aspx?v=14.3.174.1&t=exchgf1&e=ms.exch.err.ExC9C315
Warning:
Network name 'msc-co-exc-01c' is not online. Please check that the IP address configuration for the database availability group is correct.
Warning:
The operation wasn't successful because an error was encountered. You may find more details in log file "C:\ExchangeSetupLogs\DagTasks\dagtask_2014-11-17_13-54-56.543_add-databaseavailabiltygroupserver.log".
Exchange Management Shell command attempted:
Add-DatabaseAvailabilityGroupServer -MailboxServer 'MSC-CO-EXC-02V' -Identity 'msc-co-exc-01c'
Elapsed Time: 00:06:21
UPD:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.
Please, help me if you can.

Hi, Jared! Thank you for the reply.
Of course I did it already :) I have new info:
when Exchange servers ran on the same Hyper-V node, the DAG is working well, but if I move one of VM to another node, It stops working.
I have installed Wireshark and captured trafic of cluster interface. When DAG members on the same HV-node, there is inbound and outbound traffic on the cluster interface, but if I move one of DAG member to another node, in Wireshark I see only outbound traffic
on both nodes.
It's confused me, because there is normal connectivity between these DAG members through the main interface.

Exchange 2010 to 2013 Migration: Authentication/Proxy Settings Issue

I'm in the final stages of preparing for our Exchange 2010 to 2013 migration. I'm noticing minor authentication issues on mobile devices (android & ios) and proxy setting issues with Outlook that require user intervention. In an effort to make the migration
as smooth as possible for our internal users, I'd like to get these settings ironed out before starting the migration.
Symptoms:
Outlook - I'm aware that internal Outlook usage has changed its connection protocol from RCP/TCP to RCP/HTTP, but it appears that Outlook isn't updating its settings in the "Microsoft Exchange Proxy Settings" after a users mailbox has been migrated
from 2010 to 2013. Currently, 2010 users with Outlook 2013 have the following settings configured in Outlook's Exchange Proxy Settings:
URL to connect to my proxy server for Exchange: webmail.domain.com
Connect using SSL only: Checked
Only connect to proxy servers that have this principal name in their certificates: Unchecked
On fast networks, connect using HTTP first, then connect using TCP/IP: Unchecked
On slow networks, connect using HTTP first, then connect using TCP/IP: Checked
After migrating a user's mailbox from 2010 to 2013, the above settings remain the same in Outlook and their client disconnects from Exchange and isn't able to reconnect. After manually enabling the checkbox for "On fast networks, connect using HTTP
first, then connect using TCP/IP", Outlook clients are able to connect to Exchange via their newly migrated mailbox.
Is there a way to automatically updating these 2 proxy settings in Outlook during the migration instead of having to manually change each user's configuration in Outlook?
Android & iOS - Currently, users on Android & iOS with Exchange 2010 mailboxes have the following configuration:
domain: blank
username: their AD username
server: webmail.domain.com
After migrating a mobile users mailbox from 2010 to 2013, neither OS (Android or iOS) is able to connect due to an authentication failure. On iOS, if I manually change the domain from blank to my company's domain, authentication succeeds and their 2013 mailbox
begins to update. On Android, the option to change the domain name from null is grayed out, requiring the user to delete the Exchange profile and re-add it with the domain name intact. Is there a way to configure Exchange 2013 to not require the domain name
for mobile users in the same way that it's been working for us with Exchange 2010?
Please let me know if you require cmdlet print outs of my virtual directories to help troubleshoot the issue.

Hi,
Generally, when the user mailbox is moved from Exchange 2010 to Exchange 2013, the Autodiscover service would detect the changes and update the new configuration automatically.
Please make sure the autodiscover service in your new Exchange 2013 is configured correctly. We can create a new mailbox in Exchange 2013 and check whether the new Exchange 2013 user can setup account successfully in Outlook or not. If the new user works
fine, it indicates the autodiscover service in Exchange 2013 should be proper for internal user.
Please restart the following Exchange service to have a try:
Microsoft Exchange RPC Client Access
Microsoft Exchange Mailbox Replication
Restart IIS service by running IISReset in a Command Prompt window.
Then check whether the Outlook client can connect to Exchange 2013 or not.
As for Android & iOS issue, I suggest we can ask a question in ActiveSync forum for more suggestion:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrmobility
Regards,
Winnie Liang
TechNet Community Support

How to force Outlook's Junk email fitler to not filter Exchange 2010 SP1 accepted domains?

Hello,
I wonder if there really is no way how to reach the result described in the title question. Because
http://support.microsoft.com/kb/2458522 says:
This issue occurs because of a functionality change that is introduced in Exchange Server 2010 SP1. In Exchange Server 2010 SP1, domains that are configured as accepted domains are no longer allowed in the junk email lists of a mailbox.
So please tell us Microsoft how can we force Outlook to accept internal domain as a trusted senders and not apply Junk email filter on it?
There was already a long discussion about the steps here
http://social.technet.microsoft.com/Forums/en-US/outlook/thread/15f857c6-0ed4-4004-9d90-cb5d16361752 so please don't offer anything described there.
Thank you,

Trying to deal with the Outlook Junk Email Filter is not very easy and had been a pain in the butt.
The ONLY way to ensure the Outlook 2010 Junk Email filter honors "white listed" emails is to stamp the email with SCL -1. Setting a transport rule will do that but it is not very flexible.
I was able to resolve these issues by simply enabling the Exchange 2010 Anti-Spam agents on each hub transport server. We have no Edge Server but we use a couple of Ironports at the gateway which provide the bulk of AntiSpam. We didn't think we would
need the Exchange AntiSpam so we hadn't initially enabled. After months of trying to resolve people's complaints of emails from internal system ending up in Junk, this solution worked for us.
This is the order in which it was done.
1. We set the receive connectors for the internal systems for bypassing Anti Spam. We basically have 2 receive connectors, one for internal system with no relay, and one for internal systems who are allowed external relay.
Get-ReceiveConnector "server\name of the recieve connector" | Add-ADPermission -User "“NT Authority\Anonymous Logon” -AccessRights ExtendedRight
-ExtendedRights ms-exch-bypass-anti-spam
Note: If you use SMTP Authentication, Exchange will only mark the emails as "Internal" and not assign a SCL of -1. It can only be on anonymous connections.
Note: We have a separate receive connector for the Ironports delivering external email that will not bypass Anti-Spam. These emails will receive a SCL rating of 0-9
2. We set the global SCL to 6 (default is 4). You can set it to whatever you want.
Set-OrganizationConfig -SCLJunkThreshold 6
So basically, any email tagged with SCL 7-9 will be moved to Junk by Exchange.
3. Set-ContentFilterConfig -SCLQuarantineEnabled $False -SCLDeleteEnabled $False -SCLRejectEnabled $False
We don't want delete, reject or quarantine anything on Exchange. Just move email to Junk folder if SCL 7-9 and have user deal with it.
4. Set the Internal SMTP Servers by adding each Exchange server's IP Address to the Global Transport Settings. I used EMC, Organization Config, Global Settings, Transport Settings properties, Message Delivery tab. Do NOT add any other "internal" servers
here, only the Exchange servers.
5. Then we installed the AS agents on each HT Server.
Starting with the first server
Stop MSExchange Transport service
D:\Program Files\Microsoft\Exchange Server\V14\Scripts>.\install-AntispamAgents.ps1
After installation, disable all the agents except for Content Filtering Agent. This agent has to be enabled for Exchange to stamp the email with SCL -1. I used EMC, Organization Config, Hub Transport. You will see a new tab called Anti-Spam. Disable everything
except Content Filtering.
Start MSExchange Transport service.
Repeat on each HT server. (You won't have to repeat the disabling of the agents as that is a global setting)
6. You can add global safe senders by doing the following.
$list = (Get-ContentFilterConfig).BypassedSenders
$list
$list.add("[email protected]")
$list.add("[email protected]")
Set-ContentFilterConfig -BypassedSenders $list
The message headers are stamped with
For emails sent through the Internal connector
X-MS-Exchange-Organization-Antispam-Report: MessageSecurityAntispamBypass
X-MS-Exchange-Organization-SCL: -1
OR
For external emails from a safe sender
X-MS-Exchange-Organization-Antispam-Report: ContentFilterConfigBypassedSender
X-MS-Exchange-Organization-SCL: -1
OR
For all other external emails
X-MS-Exchange-Organization-SCL: 0
Good Luck. This has basically stopped all the calls about "legitimate" email in Junk Email folder.

Exchange 2010 SP3 Move Mailbox fails on every mailbox with Fatal error MapiExceptionJetErrorIndexNotFound has occurred

We are currently running Small Business Server 2003 with Exchange 2003 SP2 and are migrating to Server 2008 R2 with Exchange 2010 SP3 as an interim before moving to Server 2012 R2 with Exchange 2013 SP1. The mailbox move reaches 95% before failing with the
message "Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
Diagnostic context:
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetPropsSpecific [7]
    Lid: 21921   StoreEc: 0x40380
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetReceiveFolderTable [104]
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetAllPerUserLtids [125]
    Lid: 17082   ROP Error: 0xFFFFFA84
    Lid: 29793
    Lid: 21921   StoreEc: 0xFFFFFA84
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0xFFFFFA84
    Lid: 25738
    Lid: 18570   StoreEc: 0xFFFFFA84
    Lid: 23370   StoreEc: 0xFFFFFA84
    Lid: 24302
    Lid: 32494   StoreEc: 0xFFFFFA84
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
   at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
   at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
   at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
   at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: ISourceMailbox.CopyTo
OperationSide: Source"
This is happening on every mailbox we attempt to move. Any help would be appreciated

Thanks for responding
I'm already using BadItemLimit of 50. The largest corrupt message that was skipped is 10.
We're on Small Business Server Standard Edition which only permits one mailbox store. I should mention that the interim machine (where Exchange 2010 is installed) is a Hyper V virtual machine
Here is the entire message from the log:
11/28/2014 7:18:07 PM [VRTL-SVR2008] 'PeacePresbyterianChurch.local/MyBusiness/Users/SBSUsers/Dev Mathura' created move request.
11/28/2014 7:18:27 PM [VRTL-SVR2008] The Microsoft Exchange Mailbox Replication service 'VRTL-SVR2008.PeacePresbyterianChurch.local' (14.3.123.2 caps:07) is examining the request.
11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to target mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'Mailbox Database 0224662151', Mailbox server 'VRTL-SVR2008.PeacePresbyterianChurch.local' Version 14.3 (Build 123.0).
11/28/2014 7:18:27 PM [VRTL-SVR2008] Connected to source mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)', database 'PEACE-SERVER\First Storage Group\Mailbox Store (PEACE-SERVER)', Mailbox server 'peace-server.PeacePresbyterianChurch.local' Version
6.0 (Build 7654.0).
11/28/2014 7:18:38 PM [VRTL-SVR2008] Request processing started.
11/28/2014 7:18:38 PM [VRTL-SVR2008] Mailbox signature will not be preserved for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)'. Outlook clients will need to restart to access the moved mailbox.
11/28/2014 7:18:38 PM [VRTL-SVR2008] Source mailbox information before the move:
Regular Items: 20, 1.906 MB (1,998,818 bytes)
Regular Deleted Items: 3, 7.803 KB (7,990 bytes)
FAI Items: 20, 0 B (0 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
11/28/2014 7:18:39 PM [VRTL-SVR2008] Initializing folder hierarchy in mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Folder hierarchy initialized for mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)': 31 folders total.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CreatingInitialSyncCheckpoint. Percent complete: 15.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: LoadingMessages. Percent complete: 20.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Mailbox 'Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)' contains 3 soft-deleted items (7.803 KB (7,990 bytes)). They won't be migrated.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Stage: CopyingMessages. Percent complete: 25.
11/28/2014 7:18:40 PM [VRTL-SVR2008] Copy progress: 0/38 messages, 0 B (0 bytes)/1.906 MB (1,998,550 bytes).
11/28/2014 7:18:41 PM [VRTL-SVR2008] Messages have been enumerated successfully. 38 items loaded. Total size: 1.906 MB (1,998,550 bytes).
11/28/2014 7:18:43 PM [VRTL-SVR2008] Initial seeding completed, 38 items copied, total size 1.906 MB (1,998,550 bytes).
11/28/2014 7:18:44 PM [VRTL-SVR2008] Final sync has started.
11/28/2014 7:18:45 PM [VRTL-SVR2008] Stage: FinalIncrementalSync. Percent complete: 95.
11/28/2014 7:18:46 PM [VRTL-SVR2008] Fatal error MapiExceptionJetErrorIndexNotFound has occurred.
Error details: MapiExceptionJetErrorIndexNotFound: Unable to copy to target. (hr=0x80004005, ec=-1404)
Diagnostic context:
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=78]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=75][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetPropsSpecific [7]
    Lid: 21921   StoreEc: 0x40380
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=45]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=140][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetReceiveFolderTable [104]
    Lid: 31418   --- ROP Parse Done ---
    Lid: 45095   EMSMDB.EcDoRpcExt2 called [length=69]
    Lid: 61479   EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=0]
    Lid: 23226   --- ROP Parse Start ---
    Lid: 27962   ROP: ropGetAllPerUserLtids [125]
    Lid: 17082   ROP Error: 0xFFFFFA84
    Lid: 29793
    Lid: 21921   StoreEc: 0xFFFFFA84
    Lid: 31418   --- ROP Parse Done ---
    Lid: 22753
    Lid: 21817   ROP Failure: 0xFFFFFA84
    Lid: 25738
    Lid: 18570   StoreEc: 0xFFFFFA84
    Lid: 23370   StoreEc: 0xFFFFFA84
    Lid: 24302
    Lid: 32494   StoreEc: 0xFFFFFA84
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, SafeExInterfaceHandle iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiUnk.ThrowIfErrorOrWarning(String message, Int32 hr)
   at Microsoft.Mapi.MapiProp.CopyTo(MapiProp destProp, Boolean reportProgress, CopyPropertiesFlags copyPropertiesFlags, Boolean copySubObjects, ICollection`1 excludeTags)
   at Microsoft.Mapi.MapiProp.ExportObjectHelper(IMapiFxProxy dest, PropTag[] tags, CopyPropertiesFlags copyPropertiesFlags, Boolean useCopyProps)
   at Microsoft.Mapi.MapiProp.ExportObject(IMapiFxProxy fxProxy, CopyPropertiesFlags copyPropertiesFlags, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.LocalSourceMailbox.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy fxProxy, PropTag[] excludeTags)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.<>c__DisplayClass7.<Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo>b__6()
   at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
   at Microsoft.Exchange.MailboxReplicationService.SourceMailboxWrapper.Microsoft.Exchange.MailboxReplicationService.ISourceMailbox.CopyTo(IFxProxy destMailbox, PropTag[] excludeProps)
   at Microsoft.Exchange.MailboxReplicationService.MailboxMover.FinalSyncCopyMailboxData()
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
   at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.FinalSync(Object[] wiParams)
   at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: ISourceMailbox.CopyTo
OperationSide: Source
Primary (d3391cdd-bc37-41ad-9e44-9f8880c47270)
PropTags: [ContainerHierarchy; ContainerContents]
11/28/2014 7:18:46 PM [VRTL-SVR2008] Relinquishing job.

Migrate Exchange 2010 to 2013 External Mail Flow

Dear All,
I am in the middle of Exchange Server 2010 to 2013 Migration. The scenario is I have single Exchange 2010 server with HUB/CAS/Mailbox and installed new Exchange 2013 with single CAS and single Mailbox server. The internal email flow between Exchange
2010 to 2013 and 2013 to 2010 is working. Having some issues and need assistance to resolve at earliest.
The issue with the external mail flow and I want to Exchange 2010 should be configured to send external email while migrating users to Exchange 2013. Once migrate all users to Exchange 2013 then will configure Exchange 2013 send connector.
How can I configure single name space of web URL for OWA both on Exchange 2010 to Exchange 2013, if user mailbox is in Exchange 2010 can access same OWA URL as user migrate to Exchange 2013.
How to configure SSL certificate, I have single URL certificate this would be enough for OWA, ActiveSync and Anywhere.
Is that possible if directly move the Exchange 2010 database to Exchange 2013 database, this will move all users mailboxes in one go or do I need to migrate users mailbox individual or in bulk.
Kindly guide if any thing missing that need to address during start the migration activity.
Thanks in Advance

Hi ,
Sorry for delay.
Question : Thanks for your valuable response. On
point no.2, I want to use same external URL for Exchange 2010 and Exchange 2013, is this possible if user is on exchange 2010 server or migrated on Exchange 2013 can use same external single name space URL to access OWA ?
Yes you can have the same External URL for the exchange 2010 owa and exchange 2013 owa.So users from exchange
2010 and exchange 2013 can access owa on the same URL from external world.For exchange 2010 users owa connections will be proxied from exchange 2013 to exchange 2010.
For mailbox connectivity issue in exchange 2013 :
1.From internal outlook clients ,Please check the internal outlook anywhere name is resolved to exchange
2013 server and also make sure the authentication set on the outlook anywhere is set to NTLM. Same time we need to have the internal outlook anywhere name on the SAN certificate.
2.Make sure the names used exchange on 2013 URL'S is available on the SAN certificate and also the certificate
needs to installed on the exchange server and that certificate has to be enabled for the required services like iis,pop.imap,smtp.
3.Make sure the outlook client request coming for internal outlook anywhere name and also to autodiscover
service is not reaching the proxy server if you have on your network.
In case if you have proxy server in your environment for internet access ,So for that we need to add the internal outlook anywhere name and autodiscover name
on the internet explorer proxy exceptions for all the internal outlook clients.We can globally achieve it through group policy.
4.please share me the output for the below mentioned command.
get-ClientAccessServer -Identity “server name” | fl AutodiscoverServiceInternalURI
5.If you are having outlook 2007 then make sure it fully patched with latest sp and updates.
6.On which operating system version those outlook 2007 clients are installed?
Please reply me if anything is unclear.
Thanks & Regards S.Nithyanandham

Removing Exchange 2010

Hi I have successfully completed a cutover migration from exchange 2010 to exchange online. We have dirsync running for password sync, NO ADFS. The current exchange 2010 is also a domain controller, as this server is no longer required I am going to demoting
this DC, as all data is migrated to exchange online and no users are using the Exchange I am thinking whether just demoting the DC will be sufficient or whether I need to uninstall Exchange 2010 before I shut this server down. If I do need to uninstall the
Exchange 2010 would this rewrite any AD attributes, am i right in thinking these exchange attributes for ad objects is an one way schema update and wont be lost, as these attribs are necessary for current exchange online to work properly eg, legacyexchangedn
in proxyaddress attrib and mailnickname etc.
Just need a short answer, If i demote dc and shutdown server would this suffice or do i need to uninstall exchange?

Decommission on-premises Exchange servers. After
you’ve verified that all email is being routed directly to the Exchange Online mailboxes, have completed the migration, and no longer need to maintain your on-premises email organization or don’t plan on implementing a single sign-on solution,
you can uninstall Exchange from your servers and remove your on-premises Exchange organization.
See here: http://technet.microsoft.com/en-us/library/jj874016(v=exchg.150).aspx
HossFly, Exchange Administrator

Exchange 2010 OWA usage in Exchange 2013

Hi,
I have Exchange 2010 with Sp3 Currently running in environment, Now we have plan to Migrate it to Exchange 2013.... Total number of mailbox is around 26000.
Before Migration we want below things to keep in mind...
1. We want to Use existing exchange 2010 OWA url ( mail.abc.com ), How to accompolish this as it will take couple of months to migrate all mailbox ?
2. Can i use my Existing Exchange certificate to get the above goal done ?
3. What will be the steps and pre-requsite to achieve the Goal ?
An Early reply would be appreciated !!
Amit

Hi Amit
First Change SCP of Exchange 2010 CAS VIP to Exchange 2013 CAS VIP.
Configure external DNS records accordingly.DNS entries should be pointed to Exchange 2013 CAS from Exchange 2010 CAS.
Ensure that you are having a seperate name for CAS array from external ews url
Outlook Anywhere should be enabled and Url should be external URL which points to Exchange 2013.
Authentication for OUtlook Anywhere should be - NTLM
for OWA exchange 2010 - FBA and windows
Point your new CAS server to the firewall or TMG . Now from exchange 2013 all request will be proxied to 2010 users
You cannot use the same certificate . YOu need to add seperate entries as the host name for new servers will vary
Apply a new certificate with all the required site names included in Exchange 2013 CAS.
Whats more you can refer my blog as well
http://exchangequery.com/2014/05/02/things-to-consider-before-configuring-autodiscover-in-exchange-20102013-coexistence-scenarios/
Cheers :)
Remember to 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 Check out my latest blog posts on http://exchangequery.com

Relay issue from Unix across Exchange 2003 OWA server in Exchange 2010 environment

Hi,
I'm trying to resolve an issue. We have one Exchange 2003 server left in our environment. The rest is now Exchange 2010. We are working to decommission this server. Monitoring the SMTP logs, I am working with the various groups to get the traffic
off this server and onto the Exchange 2010 environment.
The issue we are finding is with a work flow. This Java app for eBis sends email to users. This is done correctly through Exchange 2010 and gets delivered from our HUB/CAS servers to the target user mailbox. This email has several links the user must click
for approving or rejecting requests. Upon clicking Approve, a new email window opens (we use Outlook 2010). The TO address is in the format of [email protected] Upon clicking Send, our Exchange 2010 HUB/CAS servers accept the
email, because one of our send connectors has, as address space, *.domain.corp. However, the email address being used it not an alias on any Exchange 2010 mailbox, so it appears Exchange 2010 is sending this email on to the Exchange 2003 server, which
also is an SMTP server. I *think* this server is looking at the address after @ to determine where to send it (ebisserver.domain.corp, which is valid in our DNS), and sends it on to that server, where the java "listener" program intercepts
the mail, processes it and then saves it to a file somewhere.
We are at a loss as to how to get Exchange 2010 to do this instead of Exchange 2003... once this traffic is eliminted from Exchange 2003, I can proceed with decommission of this server. Any help troubleshooting this issue is appreciated.

The only reason the Exchange 2010 server would route outbound mail through an Exchange 2003 server is that you have an SMTP Connector defined on the Exchange 2003 server that has a more specific domain than you have on the Exchange 2010 server. You
should be able to see all your Send Connectors (an SMTP Connector on Exchange 2003 looks like a Send Connector in Exchange 2010) by running Get-SendConnector.
Ed Crowley MVP "There are seldom good technological solutions to behavioral problems."

Exchange 2010 EvenID 2070, LDAP connects to demoted AD server

Similar Messages

Maybe you are looking for