Hello all,

i checked all solutions from technet i found to this problem, but nothing helped

My environment:

2x Exchange 2013 CU7 with DAG Cluster, one 700GB Database, all Mailboxes migrated some months ago from Exchange 2010

The passive Copy has always "failed an Suspended" Content Index State after failover

I always get eventlog error MSExchangeFastSearch 1013 & 1009 when I try to rebuild the content index

1013: Indexing state not found in FAST catalog for MDB 78A30F80-896D-4E4E-91CA-C792E02F60BC12

1009: The indexing of mailbox database MBXDB1 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.CatalogReseedException: The database '78a30f80-896d-4e4e-91ca-c792e02f60bc (MBXDB1)' needs to be crawled but is not mounted on the preferred active server. Requesting a reseed.

  bei Microsoft.Exchange.Search.Engine.SearchFeedingController.PrepareToCrawl(NotificationsEventSourceInfo ciWatermarkInfo)

  bei Microsoft.Exchange.Search.Engine.SearchFeedingController.DetermineFeederStateAndStartFeeders()

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

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

  --- Ende der internen Ausnahmestapelüberwachung ---

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

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

What i tried:

• rebuild passive Content Index with update-mailboxdatabasecopy – catalogonly
• Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller. Delete Content Index Folder in filesystem. start the services
• Adding Contentsubmitters group ((http://support.microsoft.com/kb/2807668))
• rebuild the DAG copy, not only the catalog:  Database update-mailboxdatabasecopy – deleteexistingfiles
• check activationpreference via ECP und Powershell. The passive copy has preference 2, the active copy preference 1

Especially I don’t understand the activationpreference error

thank you in advance Boris

I have exchange 2013 CU2, on windows server 2012 r2 and the physical machine is HP ProLiant ML310e Gen8.
Now I want to implement a DAG server, can anyone please guide me through the requirements like which machine I should purchase for the DAG and can I use windows server 2008 R2 standard. and how to make the physical connection with the existing server.
I have 1TB on existing server, does the server I implement in DAG should have the same amount of Storage.
thanks all and appreciate your assistance.

Hello Everyone,

I am finishing up an Exchange 2013 migration from 2007.  I am currently still in coexistence and had some questions around the Global Address List and Free Busy Information.

How to I tell if my clients are pulling address book information from my Exchange 2013 or 2007 Global Address List?  I don't want to remove the 2007 system if the clients are pulling from it.  All mailboxes are moved to Exchange 2013.

How do I make sure my clients are pulling the Fee Busy Information from Exchange 2013 or 2007?  If I remove my 2007 servers will my clients lose Free Busy Information?

How do I tell what Exchange version my clients are getting this information from?

Thanks for any assistance!

Ian...

I recently took over a network that had a Exchange 2010 server that needed to be updated to Exchange 2013.  There were a lot of migration problems because of legacy issues and we have resolved almost all of them down to this final one. I have searched online and can't really find anyone who has dealt with this issue in a recent version of Exchange server.   I get a warning in the ECP for Exchange 2013 as follows:

Warning

The object domain.local/Company/Program Users/Microsoft Schedule+ FreeVBusy Connector (<old server name ie not 2010 or 2013>) has been corrupted and it's in an inconsistent state. The Following validation errors happened:

Database is mandatory on UserMailbox.

I tried to post a screenshot of the error but I am not allowed yet being a new poster I guess.  From the research I have done this is a left over from 5.5/2000 days.  Is that correct? The 2010 server is still online so I can use that to remove this problem or with the 2013 server.  Once I handle this problem then I will decommission the 2010 server from the network.   

Thanks.

I have a fully migrated (from Ex 2010 to) Exchange 2013 environment; all users are running on 2013, Outlook 2010.  Simple environment...one site has two all-in-one machines, the other site has one all-in-one machine. 

About a month ago we had a fairly serious internal communication failure that disconnected an entire site of users from Exchange. I had to exercise one of my free TechNet support tickets to get it fixed.  Somewhere along the way during the repair, the migration of mailboxes got muddied up, which I go into detail below.  I did contact back to the support tech (who was fantastic btw), and he said that nothing he did would have affected the situation, and moved on.

Situation:

If we create a NEW user (new meaning after the failure repair) and place the mailbox in site 1, then realize it would be better served from the server in site 2, we can open the ECP, choose the user, choose the new mailbox dbase and migrate them over, no problems at all. 

If we choose a user that was in existence PRIOR to the failure repair, open the ECP, choose that user, choose the new mailbox dbase and start the migration, the job ends in less than 5 minutes.  The email generated looks like what's below and the user is never moved.  Nothing ever shows up in the logs...

_____________________________________________

Migration batch XXX to XXX has completed successfully.               

________________________________

Synced:               None   

Total mailboxes:              None                  

Please don't reply to this e-mail. It was sent from an unmonitored account.        

______________________________________________

We CAN move mailboxes using the Exchange Command Shell no matter when it was created; and while it's cool at and all, the boss that doesn't want to use PowerShell. She would prefer using the ECP (as do I).

I'm grasping at straws on this one trying to figure out what's wrong and how to fix it, other than it appears that the ECP is struggling to communicate to the subsystem on these 'older' accounts. 

It's not the 'bad item' count either...I set it at 10,000 on a box that had nothing in it... same results.

Appreciate any insight or assistance...

Chris R

I currently have an Exchange 2013/2007 coexistence scenario which gives me trouble with the RPC over HTTP part with users with a 2007 mailbox. the MS RCA website performs 2 tests with the MAPI address book endpoints, once against a 2007 mailbox server and once a against a GC/DC, the last one fails. The logs are from our test domain, but the exact same happens in the production domain. running CU8 (recently upgraded, but problem was exactly the same with CU7)

	Testing the MAPI Address Book endpoint on the Exchange server.
	The address book endpoint was tested successfully.
	Additional Details   Elapsed Time: 7872 ms.
	Test Steps   Attempting to ping the MAPI Address Book endpoint with identity: exmb11.domain.test:6004.   The endpoint was pinged successfully.   Additional Details   The endpoint responded in 156 ms. Elapsed Time: 4153 ms.

	Testing the MAPI Address Book endpoint on the Exchange server.
	An error occurred while testing the address book endpoint.
	Additional Details   Elapsed Time: 3079 ms.
	Test Steps   Attempting to ping the MAPI Address Book endpoint with identity: tdc01421.domain.test:6004.   The attempt to ping the endpoint failed.    <label for="testSelectWizard_ctl12_ctl06_ctl02_ctl09_ctl00_tmmArrow">Tell me more about this issue and how to resolve it</label>   Additional Details   The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process. Elapsed Time: 3079 ms.

---
texmb11 = ex2007 mailbox
texfr11 = ex2007 CAS
tdc01421 = DC/GC
texch31 = 2013 multirole
---

other symptoms :

Browser test
https://texch31.domain.test/rpc/rpcproxy.dll?texmb11:6004 --> 503 (which is correct)
https://texch31.domain.test/rpc/rpcproxy.dll?tdc01421:6004 --> 404.0 Not Found

RPCPing
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success

rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Fails!

so the Ex2013 RPCProxy doesn't proxy to the DC/GC, but the RPCProxy to an ex2007 mailbox server works fine, so the authentication methods configured are correct i'd say..

the same tests using the ex2007CAS server as RPC proxy all succeed!:

MS RCA is all green

https://texfr11.domain.test/rpc/rpcproxy.dll?texmb11:6004 --> 503
https://texfr11.domain.test/rpc/rpcproxy.dll?tdc01421:6004 --> 503 

rpcping -t ncacn_http -s texmb11 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success

rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success!!

Logs

all tries against the 2013 CAS server generate '404' log entries in several logs int the Logging directory, the most explicit being the one in Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttp : HttpProxy_xxxxxx.LOG

2015-04-30T19:58:00.153Z,895cdf07-f2eb-4beb-b787-da02ba11b0c2,15,0,1076,0,,RpcHttp,webmail.domain.test,/rpc/rpcproxy.dll,,Basic,true,DOM\user,,,MSRPC,10.10.142.132,TEXCH31,404,,MailboxGuidWithDomainNotFound,RPC_IN_DATA,,,,,,,,,4,,,,1,,,0,,0,,0,0,,0,2,0,,,,,,,,,1,1,0,,1,,2,2,,?TDC01422.domain.test:6004,,BeginRequest=2015-04-30T19:58:00.153Z;CorrelationID=<empty>;ProxyState-Run=None;ProxyState-Complete=CalculateBackEnd;EndRequest=2015-04-30T19:58:00.153Z;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:RPC server name passed in by client could not be resolved: TDC01422.domain.test   at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveToDefaultAnchorMailbox(String originalRpcServerName  String reason)    at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveAnchorMailbox()    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__3b();

the error suggests the name could not be resolved. but nslookup works fine. i can ping the tdc01421 correctly form texch31, it returns me the ipv4 address. i can telnet to port 6004 from texch31 server to tdc01421 giving me the correct 'ncacn_http' answer..

i look at the 'ValidPorts' and ValidPorts_Autoconfig_Exchange reg keys and filled them with the same i have on the 2007cas servers (all ex servers, all dc/gc's, all of them with netbios & fqdn ports 6001,6002 & 6004..) but also no success.

im out of ideas by now..

Hello,

When I run TestOutlookConnectivity -ProbeIdentity OutlookSelfTestProbe as suggested on Technet, the following error message is returned:

This is a brand new Exchange 2013 installation on WinServer 2008r2. OWA works. Mails flows.

Thank you for your support

We have an Exchange 2013 Project and plan the publishing of the Outlook Anywhere Service. We have the following scenario:

- Outlook Anywhere with preauthentication from the Internet

- Preauthentication Basic or NTLM

- No direct access to the Exchange CAS Server from Internet (Reverse Proxy, or LB)

- No TMG 

Now I'm looking for a solution which can do preauthentication.

Best Regards - Bueschu

Bueschu

Hi all,

We have a customer who has Exchange 2007 email system and Symantec EV 7 for archiving email. We need to migrate their email from Exchange 2007 to Exchange 2013 and activating Exchange 2013 archives. The customer asks to use this tool "Archive 2-Anywhere" from Archive360 to migrate archives from Symantec EV to Exchange 2013.

My question is I need to do this (migrating a user mailbox archive) in parallel with moving his mailbox to new exchange?

Hi all,

Due to the POODLE vulnerability and TLS 1.0 showing as enabled on one of our external scans, we were informed that we would need to disable SSL 3.0 and TLS 1.0 on our Exchange server.

Apparently, this wouldn't even be possible until Update Rollup 9 was released on 3/16/15:

Rollup resolves:

KB 3029667 SMTP is not transported over TLS 1.1 or TLS 1.2 protocol in an Exchange Server 2010 environment

After installing this update, SSL 3.0 and TLS 1.0 were disabled and the servers rebooted (cross site, same domain, two Exchange servers).  After resolving some issues with certificates that apparently broke as a result of the changes, we found that EWS was not working - the log full of these errors:

Hello Friends,

Do we have a server side script in Exchange that will print email from an account as they arrive?

Regards,

Binu Kumar - MCP, MCITP, MCTS , MBA - IT , Director Aarbin Technology Pvt Ltd - Please remember to mark the replies as answers if they help and unmark them if they provide no help.

After setting up archiving, are users able to access their archived mailbox from their mobile phones witch active sync? Also does Outlook create OST files for archived mailboxes? Any other possible gotchas with archived mailboxes?

Thanks for any input!

Hi all,

I will have 2 CAS servers in main site and one in DR. Also will have two MBX servers in main site and one in DR. MBX servers will be configured in DAG and the two CAS servers in main will be configured in Windows NLB. The current exchange 2007 infrastructure consists from two CAS\HUB\MBX servers configured with Neverfail software for high availability solution. When I configure windows NLB between the two new exchange 2013 CAS servers in main, I need to put the exchange hostname i.e. webmail.domain.com as the NLB cluster hostname but this will break exchange 2007 and clients connectivity, right? what is the best practice?

Hi Everyone,

I'm hoping others on this forum have some thoughts on whether it is worthwhile deploying only the Exchange 2013 CAS role for the purposes of SMTP relay.

When using Exchange Online, most guides suggest installing the IIS virtual SMTP component in an environment if SMTP relay is required. This is simple enough, however Microsofts future plans for IIS vSMTP look uncertain.

So my question is, has anyone deployed only the Exchange 2013 CAS role in an environment solely for the purposes of SMTP relay?
One pitfall I'm thinking about is the autodiscover service. Once the CAS role is installed an AD SCP is created, so this could cause potential problems.

I'm not concerned about having to extend the AD schema, or the cost. It's the other technical bits :)

cheers!

I can't install exchange server. please help me to solve this problem.

Error:

The following error was generated when "$error.Clear();

          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))

          {

          if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)

          {

          $sysMbx = $null;

          $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";

          $dispname = "Microsoft Exchange";

          $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );

          if ( $mbxs.length -eq 0)

          {

          $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);

          if ($dbs.Length -ne 0)

          {

          $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);

          if ($arbUsers.Length -ne 0)

          {

          $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;

          }

          }

          }

          else

          {

          if ($mbxs[0].DisplayName -ne $dispname )

          {

          set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;

          }

          $sysMbx = $mbxs[0];

          }

          # Set the Organization Capabilities needed for this mailbox

          if ($sysMbx -ne $null)

          {

          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");

          set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;

          # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.

          # This can be remove after BUG(O15#2555914) is fixed.

          if ($sysMbx.RetentionPolicy -eq $null )

          {

          $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});

          set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;

          }

          }

          else

          {

          Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");

          }

          }

          else

          {

          write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."

          }

          }

        " was run: "Database is mandatory on UserMailbox.".

Error:

The following error was generated when "$error.Clear();

          if (($RoleIsDatacenter -ne $true) -and ($RoleIsDatacenterDedicated -ne $true))

          {

          if (test-ExchangeServersWriteAccess -DomainController $RoleDomainController -ErrorAction SilentlyContinue)

          {

          $sysMbx = $null;

          $name = "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}";

          $dispname = "Microsoft Exchange";

          $mbxs = @( get-mailbox -arbitration -Filter {name -eq $name} -IgnoreDefaultScope -resultSize 1 );

          if ( $mbxs.length -eq 0)

          {

          $dbs = @(get-MailboxDatabase -Server:$RoleFqdnOrName -DomainController $RoleDomainController);

          if ($dbs.Length -ne 0)

          {

          $arbUsers = @(get-user -Filter {name -eq $name} -IgnoreDefaultScope -ResultSize 1);

          if ($arbUsers.Length -ne 0)

          {

          $sysMbx = enable-mailbox -Arbitration -identity $arbUsers[0] -DisplayName $dispname -database $dbs[0].Identity;

          }

          }

          }

          else

          {

          if ($mbxs[0].DisplayName -ne $dispname )

          {

          set-mailbox -Arbitration -identity $mbxs[0] -DisplayName $dispname -Force;

          }

          $sysMbx = $mbxs[0];

          }

          # Set the Organization Capabilities needed for this mailbox

          if ($sysMbx -ne $null)

          {

          Write-ExchangeSetupLog -Info ("Setting mailbox properties.");

          set-mailbox -Arbitration -identity $sysMbx -UMDataStorage:$true -Force;

          # No RetentionPolicy assigned to E-Discovery arbitration mailbox currently, we need to set it here.

          # This can be remove after BUG(O15#2555914) is fixed.

          if ($sysMbx.RetentionPolicy -eq $null )

          {

          $arbitrationRetentionPolicy = @(Get-RetentionPolicy -DomainController $RoleDomainController | where {$_.Name -eq 'ArbitrationMailbox'});

          set-mailbox -Arbitration -identity $sysMbx -RetentionPolicy $arbitrationRetentionPolicy[0].Identity -Force;

          }

          }

          else

          {

          Write-ExchangeSetupLog -Info ("Cannot find E-discovery arbitration mailbox with name=$name.");

          }

          }

          else

          {

          write-exchangesetuplog -info "Skipping creating Discovery Arbitration Mailbox because of insufficient permission."

          }

          }

        " was run: "Database is mandatory on UserMailbox.".

Md. Ramin Hossain

Following recent acquisition of another company we faced the following situation:

Company A has Exchange 2013 Organization up and running and already using new Public Folders migrated from 2010 when we upgraded.

Company B has Exchange 2010 Organization with their own PF infrastructure.

When it comes to migration, there's already public folder mailbox which was created when first migration occured.

I cant figure next steps to merge those PF infrastructures at the moment, as removing public folder mailbox prior migration is not an option, since we already have big amount of data in 2013 Organization.

Have anyone done similiar task and if so, how did you overcome this limitation?

hello,

I have exchange 2007 version 8.1 and I want to migrate to exchange 2013, so in order to to that I need to upgrade the exchange 2007 to sp3.

I install the sp3 without any issue but the version of the exchange 2007 still 8.1, I try to re install but it show that the sp3 already installed.

any idea about this issue?

thank you

Hi,

We have an internal abc.net domain which is not resolve able in internet and want to deploy exchange server with abc.com name that we also have and is resolve able in internet.

the problem is we have Active Directory service for abc.net and all user accounts have .net suffix.

is it possible to deploy exchange for .com and link them together? and define user@abc.com mail addresses for abc.net domain users?

what should I do to design such mail flow?

please help me through this,

Thanks in advance.