Hi All, 

I've been banting this around today in the office and I was always under the assumption that if a NODE loses quorum Active Manager Changes the DAC value to 0 and changes it back to 1 when contact to another server in the cluster with quorum. I was questioned about this today and after researching I'm no longer feeling 100% about this? 

"The starting bit is always 0, and because the bit is held in memory, any time the Microsoft Exchange Replication service (MSExchangeRepl.exe) is stopped and restarted, the bit reverts to 0. In order to change its DACP bit to 1 and be able to mount databases, a starting DAG member needs to either:"

http://blogs.technet.com/b/exchange/archive/2011/05/31/exchange-2010-high-availability-misconceptions-addressed.aspx

This seems to imply that this decision only happens once at startup. If this is true it would mean that the event of a network outage where boxes are still running yet without network we could still have a Split Brain situation when connectivity is restored. 

Input would be appreciated 

Thanks

Josh

Hello,

We had an Exchange 2013 running for almost a year without any troubles. For a weird reason the VM hosting the AD stopped once (nothing in the event mgr could tell us what went wrong). It had been restarted and Exchange was working again. A day after, the VM hosting the AD stopped again. Did some windows update and the AD seems to be working now (however, still don't what what is wrong with this installation). The trouble is, that Exchange does not work correctly. Here are the symptoms (or what is still working).

Using Outlook, mail flow to outside the domain works (however it seems that the routing takes a very long time, more than an hour). Using OWA, when sending an email it stays in the Draft folder. Outlook client is connected to the server, no errors are reported. When trying to log to ECP the following error page is returned:

[LdapException: The LDAP server returned an unknown error.]
   System.DirectoryServices.Protocols.LdapConnection.Connect() +160800
   System.DirectoryServices.Protocols.LdapConnection.BindHelper(NetworkCredential newCredential, Boolean needSetCredential) +264
   Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithLogging() +10608880
   Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithRetry(Int32 maxRetries) +726

[ADTransientException: Active Directory server  is not available. Error message: Active directory response: The LDAP server returned an unknown error.]
   Microsoft.Exchange.Data.Directory.PooledLdapConnection.BindWithRetry(Int32 maxRetries) +2527
   Microsoft.Exchange.Data.Directory.LdapConnectionPool.CreateOneTimeConnection(NetworkCredential networkCredential, ADServerInfo serverInfo, LocatorFlags connectionFlags) +1155
   Microsoft.Exchange.Data.Directory.TopologyProvider.PopulateDomainNamingContexts(String partitionFqdn) +339
   Microsoft.Exchange.Data.Directory.TopologyProvider.GetRootDomainNamingContext(String partitionFqdn) +94
   Microsoft.Exchange.Data.Directory.ADSession.GetRootDomainNamingContext(String partitionFqdn) +305
   Microsoft.Exchange.Data.Directory.ADDataSession.GetNamingContext(ADNamingContext adNamingContext) +639
   Microsoft.Exchange.Data.Directory.ADObject.ValidateSingleADObjectLinkValue(ADPropertyDefinition propertyDefinition, ADObjectId value, List`1 errors) +539
   Microsoft.Exchange.Data.Directory.ADObject.ValidateRead(List`1 errors) +2589
   Microsoft.Exchange.Data.ConfigurableObject.ValidateRead() +70
   Microsoft.Exchange.Data.Directory.ADDataSession.ObjectsFromEntries(SearchResultEntryCollection entries, String originatingServerName, IEnumerable`1 properties, ADRawEntry dummyInstance, Boolean dualSearchResults) +4516
   Microsoft.Exchange.Data.Directory.ADDataSession.ObjectsFromEntries(SearchResultEntryCollection entries, String originatingServerName, IEnumerable`1 properties, ADRawEntry dummyInstance) +113
   Microsoft.Exchange.Data.Directory.ADDataSession.InternalFind(ADObjectId rootId, String optionalBaseDN, ADObjectId readId, QueryScope scope, QueryFilter filter, SortBy sortBy, Int32 maxResults, IEnumerable`1 properties, Boolean includeDeletedObjects) +6027
   Microsoft.Exchange.Data.Directory.SystemConfiguration.ADTopologyConfigurationSession.FindLocalServer() +212
   Microsoft.Exchange.Management.Security.Utility.GetVirtualDirectoryObject(Guid vDirObjectGuid, ITopologyConfigurationSession session, PropertyDefinition[] virtualDirectoryPropertyDefinitions) +307
   Microsoft.Exchange.Management.Security.AdfsFederationAuthModule.InitStaticVariables() +605
   Microsoft.Exchange.Management.Security.AdfsFederationAuthModule..ctor() +49

[TargetInvocationException: Exception has been thrown by the target of an invocation.]
   System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandleInternal& ctor, Boolean& bNeedSecurityCheck) +0
   System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +159
   System.RuntimeType.CreateInstanceDefaultCtor(Boolean publicOnly, Boolean skipCheckThis, Boolean fillCache, StackCrawlMark& stackMark) +256
   System.Activator.CreateInstance(Type type, Boolean nonPublic) +127
   System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes, StackCrawlMark& stackMark) +14259449
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes) +200
   System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture) +28
   System.Web.HttpRuntime.CreateNonPublicInstance(Type type, Object[] args) +83
   System.Web.HttpApplication.BuildIntegratedModuleCollection(List`1 moduleList) +335
   System.Web.HttpApplication.GetModuleCollection(IntPtr appContext) +1262
   System.Web.HttpApplication.RegisterEventSubscriptionsWithIIS(IntPtr appContext, HttpContext context, MethodInfo[] handlers) +133
   System.Web.HttpApplication.InitSpecial(HttpApplicationState state, MethodInfo[] handlers, IntPtr appContext, HttpContext context) +304
   System.Web.HttpApplicationFactory.GetSpecialApplicationInstance(IntPtr appContext, HttpContext context) +404
   System.Web.Hosting.PipelineRuntime.InitializeApplication(IntPtr appContext) +475

[HttpException (0x80004005): Exception has been thrown by the target of an invocation.]
   System.Web.HttpRuntime.FirstRequestInit(HttpContext context) +12968244
   System.Web.HttpRuntime.EnsureFirstRequestInit(HttpContext context) +159
   System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context) +12807949

AD and Exchange are running on Windows 2008r2/SP1. Everything is fully patched.

I just don't know what to do in order to get Exchange working again. Can somebody help us?

Thank you

I need some assistance/guidance with deploying Exchange 2013. The MS documentation and the F5 Deployment guide state that persistence is not needed due to the change in functionality with the CAS servers. Other customers have NOT needed persistence as well.

I have  configured  a Layer 4 and a  Layer 7 (SSL bridging) option. I would just like to know any possible reasons (configuration scenarios) why persistence is required with this particular Exchange 2013 implementation? Looking for clues. Any feedback is appreciated.

Finally, this is a 2007 to 2013 migration.

Thank you,

Hi,

I am planning to deploy an Amazon EC2 instance, which will act as a member of DAG. The other servers are hosted in our Office premises. I just want the amazon EC2 just for the purpose of redundancy. If any one has already done this before, please just outline the approach that you have taken for achieving this.

Exchange 2013 SP1, Windows Server 2012 DC, DAG (two pure mailbox servers), a single mail database hosted by both the servers.

Yesterday I moved my database to another logical volume following the procedure described inhttp://technet.microsoft.com/en-us/library/dd979782(v=exchg.150).aspx . After the DB was moved and mounted and the second copy was re-added, the database itself on the second server changed it state to 'Healthy'. However, its content index remains in the "FailedAndSuspended" state. This is not the first time I encounter this error, but previously I was able to resolve it using different solutions available on the Internet. However, this time I can't resolve it. In particular,

• I've ensured that ContentSubmitters group in AD exists and has the necessary permissions;
• I stopped both the search services and removed the search index directory;
• I reseeded the search catalogue only and even the entire database using the Update-DatabaseCopy commandlet (the "Seeding" status is immediately replaced with the same "FailedAndSuspended" one).

In addition, I can see the following warning with the code 1009 and source MSExchangeFastSearch in the server Application log:

The indexing of mailbox database XXX 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 'XXX' needs to be crawled but is not mounted on the preferred active server. Requesting a reseed. (call stack omitted)

Are there other methods to repair the search index? Of course, I can create another database, move all the mailboxes there and delete the faulty one, but this is kind of too serious. Any ideas?

P.S. Activation preference numbers on the database copies has changed after the second copy was removed and re-added. However, swapping those numbers doesn't help, too.

Evgeniy Lotosh
MSCE: Server infractructire, MCSE: Messaging

Greetings,

We were notified today that one of our databases in an Exchange 2013 cluster is currently in a failed state. We have three servers - two at the primary site and one in the DR site. The database has a mounted and healthy copy on its preferred server, but the secondary copy is now failed with a pretty high CopyQueueLength.

I've done plenty of reseeds with Exchange 2010, and I understand that Exchange 2013 will do an automatic reseed in the event of a failure. However the auto-reseed is generating the following message:

During the course of my investigation, I tried to rename the .edb file to .old and was told that the file is in use by Microsoft.exchange.store.worker.exe. There doesn't seem to be a way to kill this process, as every time I've tried I've been told that access is denied. I'm not even sure it's wise to kill the process anyway (I'm only trying to kill the one with the PID that matches the database).

Attempting to manually reseed the database generates a similar error to the one above. I've failed all the databases over to the other server and restarted the Information Store service as well as the Host Controller service, but so far I can't seem to get this file unlocked. One article I found did mention making sure that Exchange Servers is listed and given Read access to the folder. I did manually set this but I still see no change. I also verified that Symantec Endpoint Protection is set to exclude .edb files, and the automatic Exchange exclusions are preventing it from scanning the Exchange install locations.

I'm curious if anyone has any suggestions that I might have missed so far. This is confusing the daylights out of me and I'd like to be able to get this reseeded. I suspect that even a full server restart won't clear this up, so any help would be great. We're just starting to transition users over from Exchange 2007 to 2013, and I'd prefer to have a method of avoiding this in the future before we're in full production.

Hi,

We encountered a problem yesterday with our Exchange 2013 servers. We have 4 Exchanges 2013 servers (2 CAS + 2 MBX).

We also have a DAG with the 2 MBX servers. When we shutted down our secondary MBX server (where the DB were active), the DB switched correctly on the first MBX server, but users could not send emails anymore, they were stuck into the drafts folder of Outlook.

When we started the secondary MBX, emails were being sent as usual.

In event viewer we had several "transport rules agent" warning, but the agent was running.

We tried to shut down the primary MBX server this morning, and everything worked fine.

So it seems we have a DAG with 2 servers, but only one of the servers can be shutted down...

Any help for this issue ?

Thanks

Hi,

One of my client is activating exchange services from secondary datacenter. Could you expert folks please review this & let me know if you see any issues and help me make this easier to achieve with little to no interruption.

Some background: The activation of secondary datacenter is needed because we’ll be migrating the current primary datacenter to new facility which will then become the new primary datacenter. And to support Email services uptime/SLA, we’ll be activating the services to secondary datacenter meanwhile, post successful datacenter migration we’ll then have to failback the services this new datacenter.

Exchange Environment: We’ve 2 Multirole exchange 2010 SP3 servers at each site. One pair F5 Load balancer (GTM & LTM configuration) at each site. Each site has IronPort for outgoing email. UM gateways are configured in cluster spanning both sites. Each site has its own CAS array. Webmail & autodiscover records are published to public DNS

Here is a plan.

1. Route public      traffic from Primary  site F5 LoadBalancer pair to Secondary      site F5 LoadBalancer pair. (Change webmail/autodiscover host name to      secondary datacenter & Flush the cache on DNS server)
2. Change the      internal DNS server record for CAS Array, Webmail, SMTP Relay, Internal      autodiscover etc to point to secondary datacenter
3. Either rename      the secondary CAS array as Primary CAS array or set the primary CAS array to      secondary site
4. Change all the      exchange Virtual directory external URL as public webmail mail URL and      internal URL will have local Secondary site CAS array followed by      directory type.
5. Configure OWA      redirection on IIS
6. Change Iron      port/HUB server to ensure source transport server is now secondary hub      server and smart host is secondary ironport
7. Replicate relay      connector to secondary hub transport server so applications can relay      emails via these servers
8. UM servers      gateway exists at both sites and SIP trunk is configured so I don’t see      any need for change
9. Move OAB to      secondary exchange server
10. Login to server      in the Secondary datacenter & runStop-DatabaseAvailabilityGroup      -Identity DAG01 -ActiveDirectorySite Primary

• Verify StoppedMailboxServer should list all mailbox servers in the primary datacenter and the StartedMailboxServers should list all mailbox servers in the recovery datacenter
• Verify that the cluster services on all Exchange servers that were accessible in the primary datacenter were cleaned up & Ensure the startup type for Cluster Service is set to disabled

11. Stop the Cluster      service on each DAG member in the Secondary datacenter.
12. Run the restore command from secondary exchange servers as below
13. Restore-DatabaseAvailabilityGroup      –Identity DAG01 -ActiveDirectorySite Secondary
         -AlternateWitnessDirectory:<AWSPath>      -AlternateWitnessServer:<AWSName>

1. Verify that the DAG members are up and the Cluster Group is online

14. Activate/Mount      the databases now
15. Shut      down primary Datacenter exchange servers, & Necessary SAN backend.      Move the hardware to new datacenter. Plug them in and turn them on &     if the exchange server/SAN come backup online properly then login to      primary exchange server & run.
16. Start-DatabaseAvailabilityGroup      –Identity DAG01 -ActiveDirectorySite primary

1. Ensure DAG members are up and the Cluster Group is online

17. Set-DatabaseAvailabilityGroup      –Identity DAG01 -WitnessServer <WSName>
         -AlternateWitnessServer <AWSName>
18. Move active      database copies to primary datacenter.
19. Repeat step 1 to      9 to turn the things back on primary datacenter.

Let me know if this can be further improved or rather simplified.      

Regards, Pushkal MishrA, This posting is provided “AS IS” with no warranties and confers no rights. I request you to test the solution in lab and post successful outcome you should try this on production.

Hi,

I've one DAG with 6 servers.

CAS and MBX are installed on the same servers, running Exchange 2013 SP1 on Windows Server 2012 R2

DAG is configured without a cluster administrative access point.

Our hardware loadbalancers can be configured to do NAT or Direct Server Return (DSR).

The loadbalancer runs within the same subnet as the Exchange servers.

Yesterday I switched from using NAT to DSR. To do that I've added a loopback adapter and gave it the same IP as the load balancers virtual server + Subnet 255.255.255.255

Then I allowed the Exchange server to process the packets.

netsh interface ipv4 set interface "team" weakhostreceive=enabled

netsh interface ipv4 set interface "loopback" weakhostreceive=enabled

netsh interface ipv4 set interface "loopback" weakhostsend=enabled

Everything seemed to work fine and the logs showed client ip addresses instead the load balancer ip address connecting to the server.

After checking the Eventlogs I saw that this broke my DAG-replication.

Cluster network 'Cluster Network 3' is partitioned. Some attached failover cluster nodes cannot communicate with each other over the network. The failover cluster was not able to determine the location of the failure. Run the Validate a Configuration wizard to check your network configuration. If the condition persists, check for hardware or software errors related to the network adapter. Also check for failures in any other network components to which the node is connected such as hubs, switches, or bridges.

Any idea how to fix this?

I like the idea of using DSR and see real client ips or are you all using NAT?

Thank you.

Kind regards,

Carsten

Name                                   : dag1
Servers                                : {ex1, ex2, ex3, ex4, ex5, ex6}
WitnessServer                          : witnesseerver.domain.com
WitnessDirectory                       : C:\Witness\dag.domain.com
AlternateWitnessServer                 :
AlternateWitnessDirectory              :
NetworkCompression                     : InterSubnetOnly
NetworkEncryption                      : InterSubnetOnly
ManualDagNetworkConfiguration          : False
DatacenterActivationMode               : Off
StoppedMailboxServers                  : {}
StartedMailboxServers                  : {}
DatabaseAvailabilityGroupIpv4Addresses : {255.255.255.255}
DatabaseAvailabilityGroupIpAddresses   : {255.255.255.255}
AllowCrossSiteRpcClientAccess          : False
OperationalServers                     :
PrimaryActiveManager                   :
ServersInMaintenance                   :
ServersInDeferredRecovery              :
ThirdPartyReplication                  : Disabled
ReplicationPort                        : 64327
NetworkNames                           : {}
WitnessShareInUse                      :
DatabaseAvailabilityGroupConfiguration :
AutoDagSchemaVersion                   : 1.0
AutoDagDatabaseCopiesPerDatabase       : 1
AutoDagDatabaseCopiesPerVolume         : 1
AutoDagTotalNumberOfDatabases          : 0
AutoDagTotalNumberOfServers            : 0
AutoDagDatabasesRootFolderPath         : C:\ExchangeDB
AutoDagVolumesRootFolderPath           : C:\ExchangeVol
AutoDagAllServersInstalled             : False
AutoDagAutoReseedEnabled               : True
AutoDagDiskReclaimerEnabled            : True
AutoDagBitlockerEnabled                : False
ReplayLagManagerEnabled                : False
MailboxLoadBalanceMaximumEdbFileSize   :
MailboxLoadBalanceRelativeLoadCapacity :
MailboxLoadBalanceOverloadedThreshold  :
MailboxLoadBalanceUnderloadedThreshold :
MailboxLoadBalanceEnabled              : False
AdminDisplayName                       :
ExchangeVersion                        : 0.10 (14.0.100.0)
DistinguishedName                      : CN=dag1,CN=Database Availability Groups,CN=Exchange Administrative Group
                                         (FYDIBOHF23SPDLT),CN=Administrative Groups,CN=Company,CN=Microsoft
                                         Exchange,CN=Services,CN=Configuration,DC=domain,DC=com
Identity                               : dag1
ObjectCategory                         : domain.com/Configuration/Schema/ms-Exch-MDB-Availability-Group
ObjectClass                            : {top, msExchMDBAvailabilityGroup}
OrganizationId                         :
OriginatingServer                      : dc1.domain.com
IsValid                                : True
ObjectState                            : Unchanged

Hi,

While discussing some of the points with folks we just got in to a topic of Exchange DB recovery.

If i am running a Exchange 2007/2010 and if my Disk drive where DB is resided is crashed completely and do not have any backup. Now i am left with only transaction logs and not even have edb file. In this case will i be able to recover my old data using Transaction Log Files ?

I understand that new Blank DB can be created in new Drive if drive is crashed but my worry is for recovering the old mails.

I hope i wont be able to reply my old logs in newly created/black DB since sequence of log file is different.

Kindly share your experience/ thought on above case.

Note: Pls assume that no high availability or backup is in place, this we are thinking as last step of recovery.

Regards:Mahesh

Hi all,

I am trying to recover my lab Exchange 2013 server after removing a component of IIS messed all IIS functions, including all virtual directories.

The server is running on Hyper-V so I have removed and rebuilt the OS disk whilst the Exchange data resides on a separate disk. I've reset the computer account in AD and then run the command:

setup /m:recoverserver /targetdir:"d:\Program Files\Microsoft Exchange\v15" /DoNotStartTransport /IAcceptExchangeServerLicenseTerms

I have now done this a number of times and on each occasion it fails when attempting to start the Microsoft Exchange Transport Submission service. The error in the event log is as follows:

Log Name:      Application
Source:        Application Error
Date:          30/03/2013 20:18:53
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      HV-E2K13
Description:
Faulting application name: MSExchangeSubmission.exe, version: 15.0.516.29, time stamp: 0x506956b8
Faulting module name: Microsoft.Exchange.Net.ni.dll, version: 15.0.516.27, time stamp: 0x5064072e
Exception code: 0xc00000fd
Fault offset: 0x0000000000639d07
Faulting process id: 0x1cc8
Faulting application start time: 0x01ce2d83cbb5568e
Faulting application path: D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe
Faulting module path: C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll
Report Id: 0a1e3a42-9977-11e2-93f1-00155d0a4b05
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-30T20:18:53.000000000Z" />
    <EventRecordID>112812</EventRecordID>
    <Channel>Application</Channel>
    <Computer>HV-E2K13</Computer>
    <Security />
  </System>
  <EventData>
    <Data>MSExchangeSubmission.exe</Data>
    <Data>15.0.516.29</Data>
    <Data>506956b8</Data>
    <Data>Microsoft.Exchange.Net.ni.dll</Data>
    <Data>15.0.516.27</Data>
    <Data>5064072e</Data>
    <Data>c00000fd</Data>
    <Data>0000000000639d07</Data>
    <Data>1cc8</Data>
    <Data>01ce2d83cbb5568e</Data>
    <Data>D:\Program Files\Microsoft Exchange\v15\Bin\MSExchangeSubmission.exe</Data>
    <Data>C:\Windows\assembly\NativeImages_v4.0.30319_64\Microsoft.E91f4adf5#\6f9b1d97c1f0dcb9b1006260c405a5da\Microsoft.Exchange.Net.ni.dll</Data>
    <Data>0a1e3a42-9977-11e2-93f1-00155d0a4b05</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Any thoughts?

Paul

Hi all! I’ve got problem with my Exchange Server (2013). I have an error # JET_errInvalidDatabase -1028. What’s the problem it might be? And how it can be solved? It would be nice if there will be any answer, that could help me. Maybe I should install some tool to recover it? 

Trying to see if anyone is successfully running a Single DAG between two datacenters using Cisco OTV.

Effectively what we are planning:

Single DAG
2 x CAS/MBX servers in each site
Hardware Load Balancing

4 Copies of each DB.  Active DB's which users connect to are assumed to be active in datacenter in which user resides.

All hardware will exist on single "virtual" subnet between two(2) datacenters.

When i move an active database with "Move-ActiveMailboxDatabase -MountDialOverride:None" in my Exchange 2013 CU1 DAG the source servers ContentIndex gets "AutoSuspended"

If i try to "update-mailboxdatabasecopy -catalogonly" i get:
WARNING: Seeding of content index catalog for database 'DB02' failed. Please verify that the Microsoft Search
(Exchange) and the Host Controller service for Exchange services are running and try the operation again. Error: There
was no endpoint listening at
net.tcp://localhost:3863/Management/SeedingAgent-ABF80EC7-D4D5-4D12-93D8-6B13D8996EC712/Single that could accept the
message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more
details..

Restarting services does not help.
Nor did: http://support.microsoft.com/kb/2807668

The only thing making the ContentIndex Healty is rebooting the server...

Any clues?

In my LAB organization  there are two exchange servers 2007 SP3 and 2010 SP3 exchange 2007 is installed on the 

primary domain controller and 2010 installed on the additional domain controller and each is windows server 2008 R2

Data Center Editions 64-bit.

I am facing problem in migrating the mail boxes from from exchange 2007 towards 2010 ,, even i have migrated the 2010 mail boxes toward 2007 successfully

i get the following error message when i am trying to migrate

Error:
Error was found for Ahmad (Ahmad@vmx.com) because: Error occurred in the step:
Preparing mailbox to be moved. Failed to copy basic mailbox information with error:
The Microsoft Exchange Information Store service could not find the specified object., error code: -1056749241

Exchange Management Shell command attempted:
'vmx.com/VMX Company/IT/Ahmad' | move-mailbox -TargetDatabase 'Mahdi2010DB'

Elapsed Time: 00:00:10

i have  tried  to restart the information store service in both exchange servers and even create other mailbox data bases

and no thing come in handy !!!

any one can help ???

Dear All,

I have 2 Sites

1. HQ

I Have One Server MBX,CAS

I have Database name : HQ_DB01 and RpcClientAccessServer is HQSERVER01.domain.local

2. AAIF

I Have One Server MBX,CAS

I have Database name : AAIF_DB02 and RpcClientAccessServer is HQSERVER01.domain.local

I need to Change AAIF_DB02 RpcClientAccessServer to AAIFSERVER02.domain.local

Can you help me to change ?

We have configured DAG between our 2 x Exchange 2013 in an Active-Passive scenario giving us a DR site to failover to.

I have blocked activation on the DR site so that things dont just flip over when they want too. 

We experienced an issue yesterday where our Exchange 2013 production server was rejecting mail stating that it was out of resources. This was a lie because the server had great RAM, CPU and disk utilisation. The only think I did notice though was in the EAC the copy queue lengths were very high and even now they are growing continuously.

When I do a Get-MailboxDatabaseCopyStatus I am seeing the copy queue length and reply queue length all 0. 

When I do a Test-ReplicationHealth I see it fails on DatabaseRedundancy and DatabaseAvalibility. I know it is failing on the DatabaseRedundancy due to the copy queue length and it fails on the DatabaseAvalibility because I have blocked the activation in the DR site. 

So I am confused why does EAC state the copy queue length as being very high but then a Test-MailboxDatabaseCopyStatus shows as 0 for both columns? 

Also I have noticed that data is being replicated between the production and DR site but it is very slow! It is not utilizing the entire bandwidth and seems to be sending in sort bursts. 

How does the replication of log shipping send in a DAG? Will the "Intersite replication SMTP Properties" in Active Directory Sites and Services have any bearing on this? Currently only 1 site is in the link and is set to replicate every 35 minutes.. 

I have a two node (node1 & node2) exchange 2013 DAG with FSW quorum on a 'non' exchange server (server), all within the same site.  All databases are mounted on the first node which is working with database copies on the second node which is 'down'.

A few times I have experienced, one of the DAG node goes 'offline' in failover cluster manager, in the past it has resolved itself, or I have taken various steps to resolve it.  This time however it will not come online again and I cannot find any method to fix this.

Windows event errors include (repeatedly);

1564

1573

C:\Windows\system32>cluster node (from the 'working node')
Listing status for all available nodes:

Node           Node ID Status
-------------- ------- ---------------------
NODE1        1 Up
NODE2        2 Down

C:\Windows\system32>cluster node (from the not working node)
Listing status for all available nodes:

Node           Node ID Status
-------------- ------- ---------------------
NODE1        1 Down
NODE2        2 Joining

The above shows me two different results depending on which exchange node I run it from.. interesting...

My DC and exchange server's time are all in sync.
I can access the FWS, and confirm the share is present, and being updated by the working node. The share has the Trusted Subsystem full control permission on the share and ntfs security.
Internally we do not use a firewall, and can confirm there are not any firewall issues.
I do not have any Antivirus running, so nothing is being blocked or interfered with here.
I can ping all hosts involved from all machines (both nodes, fws, dc, dag dns name, everything).
I have restarted the failed node, and also the working node.

It was all fine until an unexpected host/VM failure and restart.

I figure I can remove all the database copies from the failed node, then evict it from the cluster, and start it again, but if I can just get it joined again properly I would much prefer that.

Andrew Huddleston |  Sydney, Australia

Here is the lab setup

DC Win 2012 DC with FSW
CAS/MBX1 WINDOWS 2012
CAS/MBX2 Windows 2012
MBX3 Windows 2012

All runningSP1 and CU5 - pre-stage CNO is also configured

I can add MBX1 and MBX2 to the DAG but I can't MBX.
I can add (after removing the DAG) MBX3 but I can't MBX2 or MBX1 to the DAG.

What else needs to check , what is going on here?

Where Technology Meets Talent