Hi Everyone-

I'm migrating my PF from 2007 to 2013 and ran into a weird issue.  I've gone through the steps outlined in this guide twice: http://technet.microsoft.com/en-us/library/jj150486(v=exchg.150).aspx

1st attempt: After running through all checks - the initial sync, waiting for 'AutoSuspended' failed because of too many bad items.  Read some more about the error and ended up deleting some old system public folders / public folders that it was had the error on (http://support.microsoft.com/kb/555978). I know without a doubt that the cleanup of a previous 2003-2007 migration was not completed.  I chalked it up to that.  I increased the baditemlimit to 20, and resumed the request.  Finally was able to reach autosuspend - locked down PF - and went in to finalize.  After finally restarting the legacy information store, was able to get it to attempt a final sync.  Attached below is the final error.

2nd attempt:  Wasn't sure if the PF's i deleted were sync'd and now causing issues on the 2013 system - went ahead and deleted PF mailbox on 2013, and Migration request.  Unlocked PF's on 2007 - everything came back fine.  Started over again, re-created PF mailbox and started new migration request.  Got to 'autosuspended' almost immediately.  Moved forward as normal, ultimately hitting the same error as attempt 1.

I've deleted all existence of the 'exchangeV1' entities out of the system PF.

Please advise

Thank you!

I've changed the names of my servers - Exchange 2007 = LEGACY2007.DOMAIN.NAME

  Exchange 2013 = NEW2013.DOMAIN.NAME

RunspaceId                       : f1b4ac3d-8a05-4abe-9bd3-87144947df9d
Name                             : PublicFolderMigration
Status                           : Failed
StatusDetail                     : FailedOther
SyncStage                        : IncrementalSync
Flags                            : IntraOrg, Pull, Suspend
RequestStyle                     : IntraOrg
Direction                        : Pull
Protect                          : False
Priority                         : Normal
Suspend                          : True
SourceVersion                    : Version 8.3 (Build 327.0)
SourceDatabase                   : LEGACY2007\Public Folders Storage Group\Public Folders
SourceServer                     : LEGACY2007.DOMAIN.NAME
BatchName                        : 
OutlookAnywhereHostName          : 
RemoteCredentialUsername         : 
AuthenticationMethod             : Basic
RemoteMailboxLegacyDN            : 
RemoteMailboxServerLegacyDN      : 
BadItemLimit                     : 5
BadItemsEncountered              : 303
LargeItemLimit                   : 0
LargeItemsEncountered            : 0
FolderToMailboxMap               : {\}
QueuedTimestamp                  : 10/22/2014 2:27:36 PM
StartTimestamp                   : 10/22/2014 2:27:43 PM
LastUpdateTimestamp              : 10/22/2014 2:35:18 PM
InitialSeedingCompletedTimestamp : 10/22/2014 2:27:46 PM
FinalSyncTimestamp               : 
CompletionTimestamp              : 
SuspendedTimestamp               : 
OverallDuration                  : 00:08:27
TotalFinalizationDuration        : 
TotalDataReplicationWaitDuration : 
TotalSuspendedDuration           : 00:04:09
TotalFailedDuration              : 00:00:46
TotalQueuedDuration              : 00:00:03
TotalInProgressDuration          : 00:00:22
TotalStalledDueToCIDuration      : 
TotalStalledDueToHADuration      : 
TotalStalledDueToReadThrottle    : 
TotalStalledDueToWriteThrottle   : 
TotalStalledDueToReadCpu         : 
TotalStalledDueToWriteCpu        : 
TotalStalledDueToReadUnknown     : 
TotalStalledDueToWriteUnknown    : 
TotalTransientFailureDuration    : 
TotalIdleDuration                : 00:00:01
MRSServerName                    : 
EstimatedTransferSize            : 0 B (0 bytes)
EstimatedTransferItemCount       : 0
BytesTransferred                 : 930.6 KB (952,985 bytes)
BytesTransferredPerMinute        : 
ItemsTransferred                 : 9
PercentComplete                  : 95
PositionInQueue                  : 
PreventCompletion                : False
FailureCode                      : -2146233088
FailureType                      : TooManyBadItemsPermanentException
FailureSide                      : 
Message                          : Error: This mailbox exceeded the maximum number of corrupted items that were 
                                   specified for this move request.
FailureTimestamp                 : 10/22/2014 2:35:17 PM
IsValid                          : True
ValidationMessage                : 
OrganizationId                   : 
RequestGuid                      : 5d826d67-05d5-49d4-9453-58bc40f69c5a
RequestQueue                     : DB01
ExchangeGuid                     : d08583f4-6475-45da-ac01-059dee1cd29e
Identity                         : 830182b4-863f-4214-b0e2-f11fbc7c1158\5d826d67-05d5-49d4-9453-58bc40f69c5a
DiagnosticInfo                   : 
Report                           : 10/22/2014 2:27:36 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' created request.
                                   10/22/2014 2:27:41 PM [NEW2013] The Microsoft Exchange Mailbox Replication 
                                   service 'NEW2013.DOMAIN.NAME' (15.0.913.7 caps:0FFF) is examining the request.
                                   10/22/2014 2:27:41 PM [NEW2013] Connected to target mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e', database 'DB01', Mailbox server 
                                   'NEW2013.DOMAIN.NAME' Version 15.0 (Build 913.0), proxy server 
                                   'NEW2013.DOMAIN.NAME' 15.0.913.7 caps:FFFFCB07FFFF.
                                   10/22/2014 2:27:41 PM [NEW2013] Connected to source mailbox '', database 
                                   'LEGACY2007\Public Folders Storage Group\Public Folders', Mailbox server 
                                   'LEGACY2007.DOMAIN.NAME' Version 8.3 (Build 327.0).
                                   10/22/2014 2:27:41 PM [NEW2013] Request processing started.
                                   10/22/2014 2:27:41 PM [NEW2013] Cleared sync state for request 
                                   00000000-0000-0000-0000-000000000000 due to 'CleanupOrphanedMailbox'.
                                   10/22/2014 2:27:43 PM [NEW2013] Stage: CreatingFolderHierarchy. Percent 
                                   complete: 10.
                                   10/22/2014 2:27:43 PM [NEW2013] Initializing folder hierarchy from mailbox 
                                   '': 38 folders total.
                                   10/22/2014 2:27:43 PM [NEW2013] Folder creation progress: 0 folders created 
                                   in mailbox 'd08583f4-6475-45da-ac01-059dee1cd29e'.
                                   10/22/2014 2:27:44 PM [NEW2013] Folder hierarchy initialized for mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e': 6 folders created.
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: CreatingInitialSyncCheckpoint. Percent 
                                   complete: 15.
                                   10/22/2014 2:27:44 PM [NEW2013] Initial sync checkpoint progress: 0/38 
                                   folders processed. Currently processing mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e'.
                                   10/22/2014 2:27:44 PM [NEW2013] Initial sync checkpoint completed: 6 folders 
                                   processed.
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: LoadingMessages. Percent complete: 20.
                                   10/22/2014 2:27:44 PM [NEW2013] Messages have been enumerated successfully. 9 
                                   items loaded. Total size: 818.8 KB (838,451 bytes).
                                   10/22/2014 2:27:44 PM [NEW2013] Stage: CopyingMessages. Percent complete: 25.
                                   10/22/2014 2:27:44 PM [NEW2013] Copy progress: 0/9 messages, 0 B (0 
                                   bytes)/818.8 KB (838,451 bytes), 5/38 folders completed.
                                   10/22/2014 2:27:45 PM [NEW2013] Copying messages is complete. Copying rules 
                                   and security descriptors.
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "schema-root"
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "microsoft"
                                   10/22/2014 2:27:46 PM [NEW2013] A corrupted item was encountered: Folder ACL 
                                   "Default"
                                   10/22/2014 2:27:46 PM [NEW2013] Initial seeding completed, 9 items copied, 
                                   total size 818.8 KB (838,451 bytes).
                                   10/22/2014 2:27:46 PM [NEW2013] Stage: IncrementalSync. Percent complete: 95.
                                   10/22/2014 2:27:46 PM [NEW2013] Folder hierarchy changes reported in source 
                                   '': 0 changed folders, 0 deleted folders.
                                   10/22/2014 2:27:47 PM [NEW2013] Incremental Sync 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e' completed: 0 hierarchy updates, 0 content 
                                   changes.
                                   10/22/2014 2:27:47 PM [NEW2013] Stage: IncrementalSync. Percent complete: 95.
                                   10/22/2014 2:27:47 PM [NEW2013] Automatically suspending job.
                                   10/22/2014 2:31:32 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' modified request.
                                   10/22/2014 2:31:55 PM [NEW2013] 'DOMAIN.NAME/.Privileged Accounts/Server 
                                   Support/admin, asimpson' resumed request.
                                   10/22/2014 2:31:56 PM [NEW2013] Job resumed with status 'InProgress'.
                                   10/22/2014 2:31:56 PM [NEW2013] Relinquishing job.
                                   10/22/2014 2:35:03 PM [NEW2013] The Microsoft Exchange Mailbox Replication 
                                   service 'NEW2013.DOMAIN.NAME' (15.0.913.7 caps:0FFF) is examining the request.
                                   10/22/2014 2:35:03 PM [NEW2013] Connected to target mailbox 
                                   'd08583f4-6475-45da-ac01-059dee1cd29e', database 'DB01', Mailbox server 
                                   'NEW2013.DOMAIN.NAME' Version 15.0 (Build 913.0), proxy server 
                                   'NEW2013.DOMAIN.NAME' 15.0.913.7 caps:FFFFCB07FFFF.
                                   10/22/2014 2:35:03 PM [NEW2013] Connected to source mailbox '', database 
                                   'LEGACY2007\Public Folders Storage Group\Public Folders', Mailbox server 
                                   'LEGACY2007.DOMAIN.NAME' Version 8.3 (Build 327.0).
                                   10/22/2014 2:35:03 PM [NEW2013] Request processing continued, stage 
                                   IncrementalSync.
                                   10/22/2014 2:35:03 PM [NEW2013] Folder hierarchy changes reported in source 
                                   '': 5 changed folders, 0 deleted folders.
                                   10/22/2014 2:35:03 PM [NEW2013] Content changes reported for mailbox '': 
                                   Batch 1, New 401, Changed 0, Deleted 0, Read 0, Unread 0, Total 401. 
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"abstract_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"account_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"adminfolderdescription_ex.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"alldayevent_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"appointment_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"approved_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Author_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"baseschema_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bcc_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bcc_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"bday_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"billinginformation_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"binding_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"browser_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"businesshomepage_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"busystatus_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Bytes_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"calendarfolder_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"calendarmessage_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"callbackphone_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Category_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cc_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cc_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Characters_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"childcount_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"childrensnames_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"closedexpectedcontentclasses_s.xml", 
                                   Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cmd_frm.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"cn_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"codebase_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comclassid_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Comments_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comment_d.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comment_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"companies_ex.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"Company_o.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"comprogid_s.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"computernetworkname_ct.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"conflict_excc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contactfolder_cc.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contacturl_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"contact_c.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-base_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-class_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-description_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-disposition-type_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-disposition_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-id_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-language_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-location_h.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                                   (IPM.Document.*xml) Subject:"content-media-type_m.xml", Folder:"exchangeV1"
                                   10/22/2014 2:35:17 PM [NEW2013] A corrupted item was encountered: Item 
                     

I have used two mail server (Exchange 2013 and Linux sendmail) for mailing in the same domain like abc.com.

I have converted authoritative domain in to internal relay for sending mail in Linux mail user, and create a send connector point to Linux mail system as a smart host. in that case my exchange user send mail to Linux user and internet via Linux smart host,

then I create a receive connector in exchange server for receiving mail from Linux mail system as edge transport custom connector & permission set to anonymous, when Linux user send mail to my exchange user it queued in my exchange message queue and the error is:

Last Error:A local loop was detected.

What's the problem?

We are providing Exchange 2010 today - in the past it was migrated from Exchange 2003. Now I am prepearing migration to Exchange 2013 - migration proces stopped with error message there is still Exchange 2003 server in configuration. I checked it through Exchange management console and there are realy 2 servers in server summary screen. I did not find legacy Exchange2003 anywhere else in configuration. So I search through internet and found some artical with manual removing old records through ADSIedit tool.
A removed the record from
Configuration\CN=Microsoft Exchange\CN=<Exchange Domain>\CN=Administratice Groups\CN=First Administratice Group\CN=Servers

there was one record with Exchange 2003 specification - so this has been deleted - but in the Exchange console I can still see the legacy Exchange2003 in the Server Summary.

Can somebody point me, what else I should check?

Note: There is still one record in:
Configuration\CN=Microsoft Exchange\CN=<Exchange Domain>\CN=Administratice Groups\CN=First Administratice Group\CN=Routing Groups\CN=First Routing Group\CN=Connection

which it seems define some connection between non existing Exchange2003 and current Exchange2010.

Should I remove this too? Is it safe?

Thanks for any help

Pavel

Hello All

I would like to get more hands on experience using Exchange 2010 beyond the basics of creating mailboxes. I would like to do this at home in my lab environment that consist of one AD domain server with a forest functional level of Server 2012 R2. I found some pretty good install guides. So to get to my question:

I don't have a domain name ex name@domain.com is there a way around this? if the email is going to be internal to my lab can I just make something up and use my domain exname@mydomain.local or .com

Thanks!!

---

Phil Balderos

Dears,

I'm facing a issue with Exchange 2013 SP1 CU5 "15.00.0913.022" suddenly after 2 month of the migration from Exchange 2010 i get the "Unknown" status for Content Index status on any database hosted on two servers only

my new Exchange 2013 topology is : 3 CAS servers & DAG contains 6 Mailboxes servers and 4 lagged Mailboxes servers

The following is the errors and warnings logs on my effected mailboxes servers:

The indexing of mailbox database DB53 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Engine.FeedingSkippedException: "Feeding was skipped for '3a5ec474-ea70-42b5-a123-d7ff7e5aadc3 (DB53)' due to the state 'Unknown', error code: 'Unknown'."

   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InternalExecutionStart()

   at Microsoft.Exchange.Search.Core.Common.Executable.InternalExecutionStart(Object state)

   --- End of inner exception stack trace ---

   at Microsoft.Exchange.Search.Core.Common.Executable.EndExecute(IAsyncResult asyncResult)

   at Microsoft.Exchange.Search.Engine.SearchRootController.ExecuteComplete(IAsyncResult asyncResult)

The FastFeeder component received a connection exception from FAST. Error details: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.GetItems(Guid flowIdentifier, String outputName)

   at SyncInvokeGetItems(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

----------------------------------------------------------------------------------------------------------------------------------------------------------------------

Event 169 (Search) of severity 'Error' occurred 14 more time(s) and was suppressed in the event log

-------------------------------------------------------------------------------------------------------------------------------------

An operation attempted against a FAST endpoint exprienced an exception. This operation may be retried. Error details: Microsoft.Exchange.Search.Fast.PerformingFastOperationException: An Exception was received during a FAST operation. ---> System.ServiceModel.CommunicationObjectAbortedException: The communication object, System.ServiceModel.Channels.ServiceChannel, cannot be used for communication because it has been Aborted.

 

Server stack trace:

   at System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

 

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Microsoft.Ceres.CoreServices.Admin.IAdminServiceManagementAgent.SystemInfo()

   at Microsoft.Exchange.Search.Fast.NodeManagementClient.CheckForAllNodesHealthy(Boolean retry)

   at Microsoft.Exchange.Search.Fast.IndexManager.<UpdateConfiguration>b__8()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.<>c__DisplayClass1.<PerformFastOperation>b__0()

   at Microsoft.Exchange.Search.Fast.FastManagementClient.PerformFastOperation[T](Func`1 function, String eventLogKey)

   --- End of inner exception stack trace ---

------------------------------------------------------------------------------------------------------------------------------------

Exchange Server Information Store has encountered an error while executing a full-text index query ("string("ItemWarmUpSearch31febf7b418e44878df6e5623e37c828*", mode="and")"). Error information: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Internal error while processing request (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is:

Microsoft.Ceres.InteractionEngine.Component.ProcessingEngineException: Internal error while processing request

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.LogAndRethrowException(Exception e)

   at Microsoft.Ceres.InteractionEngine.Component.CieProcessingEngine.ExecuteSearchFlow(String flowName, IEnumerable`1 inputData)

   at SyncInvokeExecuteSearchFlow(Object , Object[] , Object[] )

   at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)

   at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)

   at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)).

What i have tried to solve the issue with no luck is: 

1- Reseed the effected Databases

2- Reset the index manually by stop the Search and Search Host Controller services and delete the index folder and start the services again in order to force it to rebuild the index

3- Restart the mailbox server that has the index issue

4- Create the AD group "ContentSubmitters" and then grant Admistrators and NetworkService full access to the group as the following technet article http://support.microsoft.com/kb/2807668

Any Idea will be much appreciated.

Thanks,

Ayman Saleh

 

---

Ayman Saleh

I've been researching this and I think I found a solution, but need a sanity check.

I'm upgrading from Exchange 2007 to 2013 (co-existence migration), and when I try to migrate a couple test mailboxes I get an Error: “This user does not have an Exchange mailbox.”

https://social.technet.microsoft.com/Forums/exchange/en-US/d0c96836-3ad5-49c8-bd85-2df52f481b0c/exchange-2013-migration-says-the-user-does-not-have-an-exchange-mailbox?forum=exchangesvrdeploy

http://support.microsoft.com/kb/2812509/en-us

The “get-mailbox –arbitration” and “get-mailbox –arbitration |fl name,alias” commands show corrupted several corrupted mailboxes on the 2013 server:

SystemMailbox{1f05a927-ac1a-45fa-9abc-338f309be380}

SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}

Migration.8f3e7716-2011-43e4-96b1-aba62d229136

FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042

The remaining mailbox (SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}) is not corrupted.

Running the command to enable the migration mailbox fails.  Error: “This task does not support recipients of this type.  The specified recipient “Migration.{GUID}” is of type UserMailbox.

This thread suggests deleting them from ADUC and then running ADprep again to recreate them.  

https://social.technet.microsoft.com/Forums/en-US/bba16b29-0d1f-4f2b-943c-e2110ae0d8b6/fixing-corrupted-mailboxes-after-migration

Is it safe to delete all of the arbitration mailboxes (including the non-corrupted system mailbox) and then recreate them?

I have Exchange 2007 and 2013.  I want to migrate to 2013 but I'm having issues in the testing phase.  I have a test account that I moved the mailbox to the new server.  I have a test PC with a modified hosts file that points to the new Exch 2013 server IP address.

When I log in with this test user, Outlook appears to connect and download the mailbox.  However a Windows Security dialog box pops up saying Microsoft Outlook Connecting to test@domain.com and it has a username and password field.  No matter what is entered here, it is NOT accepted, nor if forcefully entering the wrong information is the account locked out.

I can click cancel here and it proceeds to update the inbox and then says All folders are up to date.  But at the bottom in Outlook 2013 it says Need password and Outlook's icon in the taskbar has a yellow triangle on it.  I can send myself a test email and I get it (I personally am on the 2007 server), but after it sends Outlook 2013 prompts again for the password, and since it does not accept anything, I have to click cancel.

I have done ALL the windows updates available on this test PC.  Exchange 2013 is on CU6 which is the latest at the time of this writing.

Another thing is in the Lync 2013 client it says "Exchange needs your credentials".  No matter what is entered here, it will not make this message go away unless you click the X on this warning bar.  Lync itself appears to work regardless.

Any ideas?

I just changed the ExternalClientAuthenticationMethod from Ntlm to Negotiage.  Now the Outlook prompt does accept the domain password, but I don't want anyone to have to enter any type of credentials just to get on.  Note, this test is on the same LAN as the servers, so I haven't even tackled an external test yet, though last time I tried it was the same results.

Hello every one,

I have a problem to migrate mailbox from exchange 2013 to exchange 2007 back.

Recently We have installed a pilot exchange 2013 and already migrate about 100 mailboxes.

But we still have some problems, and need transfer/migrate some mailboxes back to exchange 2007

i'm facing with this problem couple of days from now, can't move some mailboxes i'm geting this message:

Relinquishing job because the mailbox is locked. The job will attempt to continue again after 5/27/2013 10:27:43 AM.

I have just clicked on sign out button in 2013 ECP and can no longer log in again, I can log in to OWA

This is a new installation and yes I made a full backup before I started to configure it, so I can go back to that if need be but unless I know why it will probably happen again.

I am using Exchange 2013 CU6 installed on 2012 standard.

I have just figured out that if I clear Internet Explorer cache, I can login again, so it looks as if it is an IE10 fault rather than Exchange 

Hi All ,

Planning to have a coexistence scenario in my environment which is mentioned below

Exchange 2010 - ambiguous url in place - OA enabled 

For mapi/rpc traffic - mail.domain.in -  exchange 2010

For https traffic - mail.domain.in - exchange 2010

mail.domain.in will get resolved in to cas array in exchange 2010 .

After coexistence On our side we are not going to move the mail.domain.in namespace to exchange 2013 , Instead of that we are going to use a new namespace in exchange 2013 for internal outlook anywhere and it will be outlookmail.domain.in and for the remaining exchange 2013 services like pop,imap,owa,active sync url's,external OA will be having mail.domain.in as same as exchange 2010 namespace.

just consider outlookmail.domain.in is available on the san certificate installed in exchange 2013.

Note : 

On my ide I would assume Internal outlook 2010 mapi users will connect directly to exchange 2010 servers on the namespace mail.domain.in

Likewise i would assume Internal outlook anywhere 2013 users will connect directly to exchange 2013 servers on the namespace outlookmail.domain.in

Services like pop,imap,owa,active sync ,external OA connections for both exchange 2010 and exchange 2013 from the external world will be routed from firewall to exchange 2013 servers .Then https traffic for exchange 2010 mailbox users will be proxied to 2010 exchange server via exchange 2013 server.

question : I would like to know above mentioned scenario is possible or not ?

On my side I know in my environment i am having ambiguous url's in place and at the same time i don't want the exchange 2010 internal outlook users to connect via exchange 2013 rpc over http even though OA is enabled on exchange 2010.

So simply i can say i need my internal exchange 2010 mailbox users has to connect via tcp/ip.

All of you tell me your valuable suggestions.

Regards

S.Nithyanandham

Hello all,

Currently running a single server installation of Exchange 2013 CU1 on Server 2008 R2.

Checked prerequisites for updating to CU5 and all looked good.

Launched the CU5 install via GUI, not command prompt, which from what I remember when I installed CU1 using the GUI didn't work very well.

Anyway, CU5 failed telling me I have to uninstall CU1. Checked a couple forums and found the same answer.

Tried to uninstall CU1 via Programs and Features, but that failed because it couldn't find a file. Also tried Change and that errors out saying the installation failed and to run setup from an installation media location.

So, I enabled the services that where disabled by either the CU5 install or the CU1 uninstall and started chasing and correcting errors. I've got it to the point that where it looks like everything is working, but I can't send or receive. I'm trying to find an error message somewhere, but I'm not having any luck finding any.

I've tried to use the Queue Viewer and suspend the queue, but nothing shows up in the queue. I've looked at send and receive connectors and they look OK.

I've been up all night and I'm at a loss right now and could really use some help getting this train back on the tracks.

Thank you,

Dennis

hi,

I have existing Exchange Server 2010 Hybrid Deployment. Planning to migrate to Exchange 2013. However, while schema update, i am facing some errors/warnings as can be seen in attached screenshot. 

I have already checked and current functional level in DC is Windows Server 2003. What could be the best steps to troubleshoot the problems and proceed further with Exchange 2013 installation?

Thanks

I am trying to install Exchange 2013 on server 2012 r2. AD level is 2012 r2 and I currently have exchange 2010 sp3 with all the rollups running. DCdiag passes with no errors.

The setup fails at the first step which is schema and AD preparation with the following error.

Error:
The following error was generated when "$error.Clear();
	install-ExchangeSchema -LdapFileName ($roleInstallPath + "Setup\Data\"+$RoleSchemaPrefix + "schema85.ldf")" was run: "Microsoft.Exchange.Configuration.Tasks.TaskException: There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostExchange2003_schema85.ldf'. The error code is: 8245. More details can be found in the error file: 'C:\Users\hhemmati\AppData\Local\Temp\ldif.err'
   at Microsoft.Exchange.Configuration.Tasks.Task.ThrowError(Exception exception, ErrorCategory errorCategory, Object target, String helpUrl)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.ImportSchemaFile(String schemaMasterServer, String schemaFilePath, String macroName, String macroValue, WriteVerboseDelegate writeVerbose)
   at Microsoft.Exchange.Management.Deployment.InstallExchangeSchema.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".

The file ldiff.err contains the following

Entry DN: CN=ms-DS-GeoCoordinates-Altitude,CN=Schema,CN=Configuration,DC=palatribe,DC=com
Add error on entry starting on line 134: Unwilling To Perform

The server side error is: 0x20bb Schema update failed: duplicate OID.

The extended server error is:

000020BB: SvcErr: DSID-032603C0, problem 5003 (WILL_NOT_PERFORM), data 8379


An error has occurred in the program

I have been searching all over the place for an answer to this with no luck.

I am migrating an SBS 2011 Exchange server (2010) to Exchange 2013 on a W2012 Server (not a DC). I completed the install and moved one user's mailbox to the 2013 server. All users can process their email via OWA and Outlook. But, if the SBS 2011 server is disconnected, the migrated user cannot log on via OWA and I can't log in to administrator ecp. They just time out. I know the mailbox is migrated because if I disconnect the 2013 server and OWA into the SBS 2011 server it gets an error saying the mailbox server is unavailable. I must have missed a step in the migration. Can someone please point me at some documentation for completing the migration. 

Thank,

Lou

---

Louyo

I am able to use the Exchange server sizing spreadsheet to determine server size, disk IOPS, memory capacity but it assumes that all users are in cached mode.  How do I calculate if all of my users are using online mode.  This is a setup where we cannot use cached mode but we are having trouble sizing it properly.

I have Exchange 2013 installed on the only domain controller.

When I go to put Exchange 2013 into maintenance mode from the Exchange Management Shell using the command:

Set-ServerComponentState server.domain.local -Component ServerWideOffline -State Inactive -Requester Maintenance

I get the following error:

"Set-ServerComponentState : The term 'Set-ServerComponentState' is not recognized as the name of a cmdlet, function,
script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is
correct and try again.
At line:1 char:1
+ Set-ServerComponentState server.domain.local -Component ServerWideOffline -State ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (Set-ServerComponentState:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException"

How do I put this Exchange server into maintenance mode?

I am trying to put Exchange into maintenance mode as the CU6 Cumulative Update is failing with the below error:

Error:The following error was generated when"$error.Clear();
          try
          {
            $Target = $env:COMPUTERNAME
            try
            {
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
            }
            catch
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target isnot an ExchangeServer.Unable to set monitoring and server state to inactive.Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            throw;
          }" was run:"Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".Error:The following error was generated when"$error.Clear();
          try
          {
            $Target = $env:COMPUTERNAME
            try
            {
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
            }
            catch
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target isnot an ExchangeServer.Unable to set monitoring and server state to inactive.Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            throw;
          }" was run:"Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)".Error:The following error was generated when"$error.Clear();
          try
          {
            $Target = $env:COMPUTERNAME
            try
            {
              $exSrv = get-ExchangeServer $Target -ErrorAction SilentlyContinue
            }
            catch
            {
              Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup will continue.";
            }

            if ($exSrv -eq $null)
            {
              Write-ExchangeSetupLog -Warning "$Target isnot an ExchangeServer.Unable to set monitoring and server state to inactive.Setup will continue.";
              return
            }

            Set-ServerComponentState $Target -Component Monitoring -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "Monitoring has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component RecoveryActionsEnabled -Requester Functional -State Inactive
            Write-ExchangeSetupLog -Info "RecoveryActionsEnabled has been set to Inactivewhile setup is running."

            Set-ServerComponentState $Target -Component ServerWideOffline -Requester Functional -State InActive
            Write-ExchangeSetupLog -Info "The server state has been set to Inactivewhile setup is running."
          }
          catch
          {
            Write-ExchangeSetupLog -Warning "Unable to set monitoring and server state to inactive.Setup can notcontinue.";
            throw;
          }" was run:"Microsoft.Exchange.Data.Directory.ADOperationException: Active Directory operation failed on EXCH01.domain.local. This error is not retriable. Additional information: Insufficient access rights to perform the operation.
Active directory response: 00002098: SecErr: DSID-03150E49, problem 4003 (INSUFF_ACCESS_RIGHTS), data 0
 ---> System.DirectoryServices.Protocols.DirectoryOperationException: The user has insufficient access rights.
   at System.DirectoryServices.Protocols.LdapConnection.ConstructResponse(Int32 messageId, LdapOperation operation, ResultAll resultType, TimeSpan requestTimeOut, Boolean exceptionOnTimeOut)
   at System.DirectoryServices.Protocols.LdapConnection.SendRequest(DirectoryRequest request, TimeSpan requestTimeout)
   at Microsoft.Exchange.Data.Directory.PooledLdapConnection.SendRequest(DirectoryRequest request, LdapOperation ldapOperation, Nullable`1 clientSideSearchTimeout, IActivityScope activityScope, String callerInfo)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Data.Directory.ADDataSession.AnalyzeDirectoryError(PooledLdapConnection connection, DirectoryRequest request, DirectoryException de, Int32 totalRetries, Int32 retriesOnServer)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException, Boolean isSync)
   at Microsoft.Exchange.Data.Directory.ADDataSession.ExecuteModificationRequest(ADObject entry, DirectoryRequest request, ADObjectId originalId, Boolean emptyObjectSessionOnException)
   at Microsoft.Exchange.Data.Directory.ADDataSession.Save(ADObject instanceToSave, IEnumerable`1 properties, Boolean bypassValidation)
   at Microsoft.Exchange.Management.SystemConfigurationTasks.SetServerComponentState.InternalProcessRecord()
   at Microsoft.Exchange.Configuration.Tasks.Task.<ProcessRecord>b__b()
   at Microsoft.Exchange.Configuration.Tasks.Task.InvokeRetryableFunc(String funcName, Action func, Boolean terminatePipelineIfFailed)"."

I Have windows 2012 DC installed and This is a production server, I know that Its not recommended to install exchange server on the DC. I had to do it because of management instructions.

I have tried to install the exchange 2013 and received many errors at the time of installations and then finally I changed the path for installation to D drive. its installed successfully.

The issue is its not opening the OWA or ECP.

The owa virtual directory got deleted as part of troubleshooting to recreate it. but after that its not creating, I reset the iis and created the virtual drive for owa from the iis console but not through powershell and then i thought to install the SP1 so that it can be fixed.

At the time of installation client access front end service role ..it gives error

Error:
The following error was generated when "$error.Clear();
          $FEOWAVdirIdentity = $RoleNetBIOSName + "\OWA (Default Web Site)";
          $FEOWAVdir = get-OwaVirtualDirectory -Identity $FEOWAVdirIdentity -DomainController $RoleDomainController;

          if ($FEOWAVdir -ne $null)
          {
            Set-OwaVirtualDirectory -Identity $FEOWAVdir.Identity -ExternalUrl $FEOWAVdir.ExternalUrl -InternalUrl $FEOWAVdir.InternalUrl -ExternalAuthenticationMethods $FEOWAVdir.ExternalAuthenticationMethods -BasicAuthentication ([Convert]::ToBoolean($FEOWAVdir.BasicAuthentication)) -WindowsAuthentication ([Convert]::ToBoolean($FEOWAVdir.WindowsAuthentication)) -DigestAuthentication ([Convert]::ToBoolean($FEOWAVdir.DigestAuthentication)) -FormsAuthentication ([Convert]::ToBoolean($FEOWAVdir.FormsAuthentication)) -LiveIdAuthentication ([Convert]::ToBoolean($FEOWAVdir.LiveIdAuthentication)) -OAuthAuthentication ([Convert]::ToBoolean($FEOWAVdir.OAuthAuthentication));
          }
        " was run: "You must set a default domain if LogonFormat is set to UserName.".

* First, I install Exchange 2013 SP1 on my server, so step 14 of 18 to 100% then alert error:

=======================

Error:
The following error was generated when "$error.Clear();
          $name = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxUniqueName;
          $dispname = [Microsoft.Exchange.Management.RecipientTasks.EnableMailbox]::DiscoveryMailboxDisplayName;
          $dismbx = get-mailbox -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1;
          if( $dismbx -ne $null)
          {
          $srvname = $dismbx.ServerName;
          if( $dismbx.Database -ne $null -and $RoleFqdnOrName -like "$srvname.*" )
          {
          Write-ExchangeSetupLog -info "Setup DiscoverySearchMailbox Permission.";
          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -eq $null )
          {
          Write-ExchangeSetupLog -info "Mounting database before stamp DiscoverySearchMailbox Permission...";
          mount-database $dismbx.Database;
          }

          $mountedMdb = get-mailboxdatabase $dismbx.Database -status | where { $_.Mounted -eq $true };
          if( $mountedMdb -ne $null )
          {
          $dmRoleGroupGuid = [Microsoft.Exchange.Data.Directory.Management.RoleGroup]::DiscoveryManagement_InitInfo.WellKnownGuid;
          $dmRoleGroup = Get-RoleGroup -Identity $dmRoleGroupGuid -DomainController $RoleDomainController -ErrorAction:SilentlyContinue;
          if( $dmRoleGroup -ne $null )
          {
            trap [Exception]
            {
              Add-MailboxPermission $dismbx -User $dmRoleGroup.Name -AccessRights FullAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue;
              continue;
            }
            
            Add-MailboxPermission $dismbx -User $dmRoleGroup.Identity -AccessRights FullAccess -DomainController $RoleDomainController -WarningAction SilentlyContinue;
          }
          }
          }
          }
        " was run: "Failed to mount database "Mailbox Database 0487331505". Error: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionJetErrorRequiredLogFilesMissing: Unable to mount database. (hr=0x80004005, ec=-543)
Diagnostic context:
    Lid: 65256  
    Lid: 10722   StoreEc: 0xFFFFFDE1
    Lid: 1494    ---- Remote Context Beg ----
    Lid: 45120   dwParam: 0x667F9F
    Lid: 57728   dwParam: 0x668155
    Lid: 46144   dwParam: 0x66851E
    Lid: 34880   dwParam: 0x66851E
    Lid: 34760   StoreEc: 0xFFFFFDE1
    Lid: 41344   Guid: 581e05de-0b68-45e0-af85-c1d96eb3e939
    Lid: 35200   dwParam: 0x548
    Lid: 46144   dwParam: 0x66885A
    Lid: 34880   dwParam: 0x66885A
    Lid: 56264   StoreEc: 0x1388    
    Lid: 46280   StoreEc: 0xFFFFFDE1
    Lid: 1750    ---- Remote Context End ----
    Lid: 1047    StoreEc: 0xFFFFFDE1 [Database: Mailbox Database 0487331505, Server: ex2013.dothanhauto.com]".

========================

* After I run install Exchange 2013 SP1 again, so go to step 5 of 9 then alert error.

* Now, my Exchange 2013 not run. So bad. Please help me fix it! Thank you so much!

Hi

I am planning to migration public folder across the forest but unable find any documentation. can you guys share the step by step guide to move/migrate public folder. we have exchange 2013 in source and target forest.   

Please help!

Hello All,

I need a bit of help.  I took over a network that was running Small Business Server 2008 with Exchange installed.  I bought a new Dell and virtualized three servers.  One of my virtual servers has Windows Server 2012 and Exchange 2013. After I installed Exchange 2013, I went to migrate some mailboxes from the Exchange 2007 machine (SBS).  When I did, the test mailboxes moved but would not open in outlook. The mailboxes that I need to move are huge and the test box wasn't.

I contacted Microsoft and we could not figure it out.  So I just left all the mailboxes on the SBS Exchange 2007 system. I would like to remove the .VHD that has Exchange 2013 on it.  I am going to virtualize the SBS and then reformat the server that the SBS resides on.  I would then like to install 2012 R2 and Exchange 2007 on that server to migrate the mailboxes and kill the SBS virtual server.

First - Is this even possible?

Second - Can I kill the Exchange 2013 .vhd without any issues?

I don't know if Exchange 2013 has been improved and I should try it again but I am a bit gun shy now.  Any advice or help would be greatly appreciated.

Thanks

Will