Hi,

We have 2 Exchange 2013(mailbox and client access) servers in DAG. And 2 hub transport servers and 2 edge servers. This is a hybrid deployment with Office 365.

This is in one site.

We would like to add one more Exchange server(mailbox and client access and hub transport in one server). This is going to be done in same site. The purpose is to add one more server to DAG. We have enough speed in this site.

Please let me know the steps.

Do I just need to install Windows server 2012, add to domain, then install Exchange 2013 mailbox role and replicate databases? Please let me know the recommendations.

Hello All , 

In my environment i have exchange 2013 with CU15 in all of our exchange servers and all those servers are physical servers and it was equally sized in terms of the hardware resources .When i checked for the events in the following location i could see the below mentioned message .

Log Location : Microsoft - > Exchange -> MailboxdatabaseFailureItems - > operational

Failure Item (Namespace=Store, Tag=HungStoreWorker, Database=CN=testing,CN=Databases,CN=Exchange Administrative Group (XYZABCI45SSSDL),CN=Administrative Groups,CN=Nithya,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=Nithya,DC=com, Instance=Testing)

As far as i understood that this automatic DB failover is initiated by the system , Since the event log (Event ID : 306 ) on the server which is holding the PAM role clearly says that DB failover is initiated by the system and not by an Admin.

Question : Here one thing we need to know is why the system is iniatiating  the DB failover and what is the cause behind that ?Please suggest me the logs that i need to analyze the cause for the DB failover done by the system ?

Please suggest me the steps to find out the cause for the DB failover.

Thanks & Regards S.Nithyanandham

Hello,

I have an Exchange 2013 database which contains mailboxes, and I'm getting this error in the Event logs

Database <databasenamehere> has been offline-repaired (by eseutil.exe) one or more times in the past. However, although this ensures database-level logical consistency and may permit the database to be successfully mounted, Exchange-level logical consistency can no longer be guaranteed. Therefore, all mailboxes should be evacuated from the database and the database should be retired as soon as possible in order to eliminate the potential for unexpected behaviour caused by Exchange-level logical inconsistency.      

This event will continue to be emitted once per hour while the database is mounted as an urgent reminder to evacuate and retire the database as soon as possible.      

Now, my question is, can I simply move the mailboxes to another database via the New-MoveRequest command and that will restore the integrity of the mailboxes, or do I have to go through this complicated import/export process described in the below link:

https://technet.microsoft.com/en-us/library/ee633455(v=exchg.150).aspx

Also, I see that .pst files have a file size limit of 50 gb.  Is there any size limit on New-MoveRequests or migration of mailboxes in general?  For example, one mailbox I want to move is 75 GB.

Thanks for your help.

Hi

Problem: After hardware crash AD, fileserver and Exchange 2013 Hyperv-VM have been restored on new a system. Everthings ok but there are problems with exchange 2013. After some trouble shooting i found that some component states are noted as "inactive". I tried to fix the problem by using 

Set-ServerComponentState $Server -Component ServerWideOffline -State Active -Requester Functional
Set-ServerComponentState $Server -Component Monitoring -State Active -Requester Functional
Set-ServerComponentState $Server -Component RecoveryActionsEnabled -State Active -Requester Functional

Most components have now the status acive but some remain inactive.

Do you have some hints for me?

Thanks

Smifty

Hello Dears,

the exchange server (2013) not working (not sending and receiving email) , connecting and disconnected again , in queue viewer show error 432 4.3.2 mailbox database is offline for mailbox database ,

from outlook side :

connecting and disconnected again and no emails received or sent

from OWA side :

X-ClientId: QFCK - W0T0 - GRGI - ACJJG
X-OWA-Error: Microsoft.Exchange.Data.Storage.MailboxOfflineException
X-OWA-Version: 15.0.1365.7
X-FEServer: XX
X-BEServer: XX
Date: 9/13/2018 9:06:48 AM

can you help me with this problem please ???

Hi,

Getting Event 1040 Category SmtpReceive in Exchange 2013 Mailbox Server (Member of DAG) on every 15 minutes.

The Event Details are given below

"The SMTP availability of the Receive connector Default Mailbox Delivery was low (0 percent) in the last 15minutes."

This is newly installed server. I think, this error start coming after configuring the new Digicert certificate.

Can you please anyone help me out to fix this error?

Thank you,

Muthu 

In our environment, Exchange 2013 Server installed on Additional Domain Controller. I know it is not recommended to install Exchange 2013 Server on Additional Domain Controller but somebody had done it in past.

Recently we faced blue dump on Exchange Server so we want to prepare for disaster recovery in case it happen.

I am aware of Exchange Server disaster recovery process but in this scenario since Exchange Server is installed on Additional Domain Controller, how the disaster recovery process will be?

Hi every one,

we have one exchange 2013 server in our setup, 

Recently we had a operating system failure due to which we did format the whole system and reinstall OS and exchange server 2013.

Emails are working find, however when i reply email to old conversation it says email does not exist. Is is because the exchange server ID has changed. Because when i send by manually adding the email it works fine.

Please do recommend a solution...

Hello all,

if I follow all steps described in 'Managing OAB in Exchange Server 2013' technet blog, it does not wok at it should: https://blogs.technet.microsoft.com/exchange/2013/01/14/managing-oab-in-exchange-server-2013/

There are two changes in how OAB distribution works (in CU03 and CU07).  There is a blog about 'OAB Improvements in Exchange 2013 Cumulative Update 7' here:
https://blogs.technet.microsoft.com/exchange/2014/10/29/oab-improvements-in-exchange-2013-cumulative-update-7/

My question is: Is the concept of OAB distribution same since CU07?

Thanks,

Soheil

Hi

I need to restore Public Folders from backup. For this i am using a recovery database containing the latest backup state. If I am running the New-MailboxRestore cmdlet this is working fine. Status: Completed.
But the target publicfolder is still empty.

New-MailboxRestoreRequest -SourceDatabase RecoveryDB -SourceStoreMailbox PFMailbox76 -TargetMailbox PFMailbox76 -IncludeFolders "Project XXX"

The corresponding Log shows that all the elements which should be transfered are skipped.

Report:
06.11.2018 11:36:02 [XXXEX3] 'XXX.corp/Users/Admin' created request.
06.11.2018 11:36:05 [XXXEX3] The Microsoft Exchange Mailbox Replication 
service 'XXXEX3.XXX.corp' (15.0.1263.5 caps:1FFF) is examining the request.
06.11.2018 11:36:06 [XXXEX3] Connected to target mailbox 
'32fba242-991f-416c-9628-dc14db5cfa16 (Primary)', database 'XXXpf01', Mailbox 
server 'XXXEX3.XXX.ch' Version 15.0 (Build 1263.0).
06.11.2018 11:36:06 [XXXEX3] Sync state for request 
1bcbdf9f-1ee8-4487-8db3-6bfd02df63b0 is null.
06.11.2018 11:36:06 [XXXEX3] Connected to source mailbox 
'RecoveryDB/32fba242-991f-416c-9628-dc14db5cfa16 (Restore)', database 
'RecoveryDB', Mailbox server 'XXXEX3.XXX.ch' Version 15.0 (Build 1263.0).
06.11.2018 11:36:06 [XXXEX3] Request processing started.
06.11.2018 11:36:06 [XXXEX3] Stage: CreatingFolderHierarchy. Percent 
complete: 5.
06.11.2018 11:36:12 [XXXEX3] Merge initialized for mailbox 
'32fba242-991f-416c-9628-dc14db5cfa16 (Primary)': 2 folders total. Estimated 
data size: 753 items, 561.7 MB (588,990,951 bytes).
06.11.2018 11:36:12 [XXXEX3] Stage: CopyingMessages. Percent complete: 10.
06.11.2018 11:36:12 [XXXEX3] Copy progress: 0/753 messages, 0 B (0 
bytes)/561.7 MB (588,990,951 bytes), 0/0 folders completed.
06.11.2018 11:36:12 [XXXEX3] Merging folder '/IPM_SUBTREE/Project XXX' into '/IPM_SUBTREE/Project XXX'.
06.11.2018 11:36:13 [XXXEX3] Copying 0 items, 0 B (0 bytes). Skipping 752 
items, 561.6 MB (588,931,619 bytes).
06.11.2018 11:36:13 [XXXEX3] Stage: CopyingMessages. Percent complete: 99.
06.11.2018 11:36:13 [XXXEX3] Copy progress: 752/753 messages, 561.6 MB 
(588,931,619 bytes)/561.7 MB (588,990,951 bytes), 0/0 folders completed.
06.11.2018 11:36:13 [XXXEX3] Merging folder 
'/NON_IPM_SUBTREE/DUMPSTER_ROOT/Project XXX_cf4389bd-ca35-49fa-b253-0494ca64d458' into '/NON_IPM_SUBTREE/DUMPSTER_ROOT
/DUMPSTER_EXTEND/RESERVED_1/RESERVED_9/dee9923b-9f3d-4d94-8f92-a9b680e3bd64'.
06.11.2018 11:36:13 [XXXEX3] Copying 0 items, 0 B (0 bytes). Skipping 1 
items, 57.94 KB (59,332 bytes).
06.11.2018 11:36:13 [XXXEX3] Source mailbox information:
Regular Items: 35508, 20.78 GB (22,309,902,805 bytes)
Regular Deleted Items: 9, 8.203 MB (8,601,161 bytes)
FAI Items: 4, 40.01 KB (40,975 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
06.11.2018 11:36:13 [XXXEX3] Target mailbox information:
Regular Items: 33247, 19.49 GB (20,924,693,716 bytes)
Regular Deleted Items: 1, 58.95 KB (60,361 bytes)
FAI Items: 4, 16.45 KB (16,843 bytes)
FAI Deleted Items: 0, 0 B (0 bytes)
06.11.2018 11:36:13 [XXXEX3] Copying messages is complete. Copying rules and 
security descriptors.
06.11.2018 11:36:13 [XXXEX3] Verifying mailbox contents...
06.11.2018 11:36:15 [XXXEX3] Mailbox contents verification complete: 2 
folders, 753 items, 561.7 MB (588,990,951 bytes).
06.11.2018 11:36:15 [XXXEX3] Stage: CopyingMessages. Percent complete: 100.
06.11.2018 11:36:15 [XXXEX3] Copy progress: 753/753 messages, 561.7 MB 
(588,990,951 bytes)/561.7 MB (588,990,951 bytes), 0/0 folders completed.
06.11.2018 11:36:15 [XXXEX3] Cleared sync state for request 
32fba242-991f-416c-9628-dc14db5cfa16 due to 'MergeComplete'.
06.11.2018 11:36:15 [XXXEX3] Request is complete.
ObjectState                            : New

[PS] D:\Scripts>Get-PublicFolderStatistics -Identity "\Project XXX"

Name                                     ItemCount                                                 LastModificationTime
----                                     ---------                                                 --------------------
Project XXX					             0                                                          06.11.2018 11:28:27

Hello Guys,

I need some advice to migrate my Exchange Dag to the New Hardware.

that's my current set up.

Base os : Windows server 2012 R2
Exchange Server : EX 2013 CU 13
Both server are Multirole and configured as Dag Member.
Both DAG members are Virtual machines in Hyper V and has two VHD's assign to each Dag member.
one is OS VHD and other one is Data.
OS VHD SIZE : 200 GB
Data VHD SIZE : 2 TB

I am thinking to make the VHD Migration, so shut down the one dag member and migrate the vhd's to new SAN storage and then start the server there. unless there is better approach ? 

please advice.

thank you so much in advance.

DEARS,

i have 2 2016 exchange servers configured in DAG mode, i'm facing the following:

all my databases are mounted on exchange A, and exchange B hold the passive copies, when i rebooted my exchange A server, databases failed over to exchange B. Now exchange B is holding the active copies, i realized when Exchange A is up again, after approximately 1 hour, databases are active again on Exchange A without my intervention.

Even when i manually activate it the databases from A to B, after a while they automatically get activated again on A without my intervention.

Is this behavior normal?

Please advise

thank you

hi guys,

i have a dag environment in which i have one cas server and two mailbox server 2013. While configuring DAG in exchange 2013 i am getting one error as follows"can't find the default database availability group container "Database Availability Groups" in Active Directory". Please give me the solution so that i can proceed.

Hello.

I have weird problem. Content index on mail dbs don't go over crawling and healthy.

I have 2 exchange 2013 CU 12 servers, no DAG.

After restart this servers, on both servers Content index state become Failed.

After searching on Internet I find solution:

Stop the Microsoft Exchange Search and Microsoft Exchange Search Host Controller service.

Browse to where the database files are located on the disk. Along with the database file, you will see a folder with a long string as the name. It will have three sub-folders as well. Delete the main folder along with the sub-folders.

Start the Microsoft Exchange Search and Microsoft Exchange Search Host Controller service.

On first server it solution helped.

But on second did not help.

I stopping services delete index folders and restart server - not helped.

Making Set-MailboxDatabase -IndexEnabled $false on DBs and stopping services delete index folders and restart server, Set-MailboxDatabase -IndexEnabled$true, stopping services delete index folders and restart server - not helped.

What different steps you are know to fix Content index state:  Failed ?

Thank you.

Some background. We have a mixed windows server environment of mostly Windows Server 2012R2 member servers and a handful of 2016 and 2008R2 servers. We are currently migrating our 2008R2 and 2012R2 systems to 2016. Almost all systems are Hyper-V guest VM's (including our Exchange servers) hosted on Windows Server 2016 Hyper-V hosts. Our domain is at a functional level of 2012R2 and is split over two sites, site BC and site DY. The sites are connected via VPN tunnel over the internet. In each site are two domain controllers, both are 2016 in the BC site and one 2016 and one 2012R2 in the DY site. One of those DC's in the BC site carry all the FSMO roles.

Our current project is to replace our existing Exchange 2010SP3RU18 servers running on Windows Server 2008R2. We have 2 in place right now. One in the DY site that has only a couple mailboxes on a single mailbox database and one in the BC site that has an mailbox database with about 80 mailboxes and an archive mailbox database. We have already extended AD and built up two new Exchange 2016CU7 servers on Windows Server 2016. Again, one in the BC site and one in the DY site.

Originally, the plan for the DY Exchange server was to host mailboxes for some other projects, but that never happened. As such, we decided to maintain an Exchange server in the DY site and utilize it for DR by deploying a DAG and replicating our mailboxes for the BC site to the DY site. Instead of doing this on the 2010 servers, we are going to deploy the 2016 servers in this fashion and migrate the mailboxes to them.

On to the problem. As it stands, the Exchange 2016 servers are built with CU7, one in DY (called D-EXCHSRV1), and one in BC (called B-EXCHSRV1), and a DAG called BC-DY-DAG in DAC mode was configured. This DAG has a witness configured in BC and an alternate witness configured in DY. We moved a mailbox or two to a mailbox database configured in the DAG and tested it out. Using Test-ReplicationHealth on both servers reports no errors. Using Get-MailboxDatabaseCopyStatus shows all mailboxes as Healthy and/or Mounted, depending on their current owner. Moving the database from server to server using Move-ActiveMailboxDatabase works as expected. If we leave automatic activation on and shut one of the servers down, the mailboxes mount up on the other server as expected and fail back after the fail back time has passed.

Everything appears to work fine in this setup as configured. However, our plan was to disable automatic activation and only use the DY site server for DR. So we changed the DatabaseCopyAutoActivationPolicy to Blocked on both servers. To verify our solution, we killed power to the BC Exchange server and witness server. We then followed the procedure at https://technet.microsoft.com/en-us/library/dd351049(v=exchg.160).aspx to verify we can bring the database copy online at the DY site in the even of a DR. On the DY site server, we first execute Stop-DatabaseAvailabilityGroup specifying the BC AD site and -ConfigurationOnly parameter. We then stop the cluster service on the DY server and then execute the Restore-DatabaseAvailabilityGroup specifying the DY AD site.

At this point, when running the Restore-DatabaseAvailabilityGroup CmdLet is where things get messed up. The Restore-DatabaseAvailabilityGroup CmdLet reports the following error:

[2018-01-29T16:48:03] Server 'B-EXCHSRV1' was marked as stopped in database availability group 'BC-DY-DAG' but couldn't be removed from the cluster. Error: A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "EvictClusterNodeEx('B-EXCHSRV1.Domain.local') failed with 0x46. Error: The remote server has been paused or is in the process of being started". [Server: D-EXCHSRV1.Domain.local]

Checking the Restore-DatabaseAvailabilityGroup log file in the C:\ExchangeSetupLogs\DagTasks\ folder seems to show that the local cluster service never completely starts up when the cmd attempts to remove the remote Exchange server from the cluster. This log shows the cluster service on the DY server in the "Joining" state, when it probably should be in the "Up" state. Researching this error seems to point to a timing issue, and most recommendations say to rerun the command. But, that makes no difference in our case.

I have ran the Get-ClusterLog command and found the section of the log where the service is started with ForceQuorum and can see that the service never fully starts up. The Log shows that it ends up stopping with the following errors:

00004c50.00003fac::2018/01/29-16:47:33.125 INFO  [VSAM] Node Id for FD info: 92ac05bc-1da2-8bc8-bd73-e800ddb1f70a
00004c50.0000121c::2018/01/29-16:47:33.126 INFO  [VSAM] Node Id for FD info: 364faf35-a476-379f-9e67-bba72d7bd352
00004c50.00003fac::2018/01/29-16:47:33.126 INFO  [VSAM] BuildNetworkTarget: remote endpoint , node id 1, bufsize 744
00004c50.0000121c::2018/01/29-16:47:33.126 INFO  [VSAM] BuildNetworkTarget: remote endpoint \Device\CLUSBFLT\BlockTarget$, node id 2, bufsize 744
00004c50.0000121c::2018/01/29-16:47:33.126 INFO  [VSAM] SetClusterViewWithTarget: nodeid 2, nodeset 0x2
00004c50.00003fac::2018/01/29-16:47:33.126 INFO  [VSAM] SetClusterViewWithTarget: nodeid 1, nodeset 0x2
00004c50.0000121c::2018/01/29-16:47:33.126 ERR   [VSAM] IOCTL_CLUSPORT_GET_UPDATE_MEMBERSHIP_STATE failed: error 87
00004c50.0000121c::2018/01/29-16:47:33.126 INFO  [VSAM] SetClusterViewWithTarget: waiting for completion for node 2
00004c50.00003fac::2018/01/29-16:47:33.126 ERR   [VSAM] IOCTL_CLUSPORT_GET_UPDATE_MEMBERSHIP_STATE failed: error 87
00004c50.00003fac::2018/01/29-16:47:33.126 INFO  [VSAM] SetClusterViewWithTarget: waiting for completion for node 1
00004c50.0000121c::2018/01/29-16:47:34.127 ERR   [VSAM] IOCTL_CLUSPORT_GET_UPDATE_MEMBERSHIP_STATE failed: error 87
00004c50.0000121c::2018/01/29-16:47:34.127 INFO  [VSAM] SetClusterViewWithTarget: waiting for completion for node 2
00004c50.00003fac::2018/01/29-16:47:34.127 ERR   [VSAM] IOCTL_CLUSPORT_GET_UPDATE_MEMBERSHIP_STATE failed: error 87
00004c50.00003fac::2018/01/29-16:47:34.127 INFO  [VSAM] SetClusterViewWithTarget: waiting for completion for node 1
00001270.00001228::2018/01/29-16:47:34.990 WARN  [RHS] Cluster service has terminated. Cluster.Service.Running.Event got signaled.
00002d34.00001180::2018/01/29-16:47:34.990 WARN  [RHS] Cluster service has terminated. Cluster.Service.Running.Event got signaled.
00001270.00001228::2018/01/29-16:47:34.992 INFO  [RHS] Exiting.
00002d34.00001180::2018/01/29-16:47:35.003 INFO  [RHS] Exiting.

I can't find much on the above, but I do know that error 87 is "The parameter is incorrect". Which, is not very helpful in the case. If we try and force the cluster service to start manually with ForceQuorum, it never fully starts up and actually gets stuck in a starting loop where it starts and stops constantly and logs to the event log with the error "The parameter is incorrect".

We have since rebuilt and reconfigured both Exchange 2016 servers in an attempt to resolve this problem and have ended up facing the exact same issue. I have included a link to the logs below, as that may provide some more information that I may be missing here.

https://1drv.ms/f/s!ApEl8Q3xIvLoiDrVH8juRS0TjQHB

Personally, I think this may be a clustering issue, as we can't get the cluster service to start once the other Exchange server and witness are offline. We have configured multi-site SQL servers with AlwaysOn Database Availability groups and have forced fail over and forced quorum to test bringing those online without issue. So, I am a bit surprised this is doing this. This is our first experience with a failover cluster without an administrative access point, but using the PowerShell CmdLets to check cluster, node and resource health before the attempted fail over shows everything in a good state. I'm not sure what else to look at. Any help with this would be greatly appreciated.

hi , 

we are trying to add node to exchnage dag 2013 and the below error is showing 

A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: An error occurred while attempting a cluster operation. Error: Cluster API failed: "AddClusterNode() (MaxPercentage=100) failed with 0x5b4. Error: This operation returned because the timeout period expired". [Server: mx02.xx.com]

we have added  the exchange server both node to Exchange Trusted Subsystem  any idea if there is another issue could cause the problem 

no firewall as well between and disabled 

One of our staff accidentally deleted four AD accounts.

That deleted the mailboxes in Exchange Server 2013.

Two of the mailboxes (the most recently added) were still there as disconnected mailboxes but the other two were not.

We don't have a backup of the individual mailboxes, but do have a backup of the DB the mailboxes reside in.

The goal is to recover the two missing mailboxes.

All four users have been restored to the AD.

The two disconnected mailboxes were reconnected.

Is there another location where the other mailboxes might be?

If not, can they be retrieved another way?

We have the DB's so if there's a way to mount the DB (without taking down the main one they exist in) and extract the box, then please explain how.

Right now we're open to suggestions as these two that are missing are of course the most critical of the four.

Alert from Microsoft Forum

Hi guys i was wondering, In the event of a datacentre failover where DAC was not enabled and thus Split Brain occurred when the sites were back online. How would you go about fixing a situation like this?

Thanks.