http://www.arabitpro.com

Hi team,

I'm having the below error message on my event log. At the same time, when i run the Get-MailboxDatabaseCopyStatus command, the Status is in healthy state, but the ContentIndexing status isFailed. I have 10 databases and the above case is for all databases.

In addition, the following is also show;

MSExchangeFastSearch Event ID 1009

The indexing of mailbox database XXX-DB02 encountered an unexpected exception. Error details: Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: The component operation has failed. ---> Microsoft.Exchange.Search.Core.Abstraction.OperationFailedException: Failed to read notifications, MDB: 7d5e3487-8ce6-4945-a0cd-63a1bf44b3e8. ---> Microsoft.Mapi.MapiExceptionNetworkError: MapiExceptionNetworkError: Unable to read the last event. (hr=0x80040115, ec=-2147221227)
Diagnostic context:
    Lid: 55272  
    Lid: 34792   StoreEc: 0x6BE     
    Lid: 51176   StoreEc: 0x80040115
    Lid: 40680   StoreEc: 0x80040115
    Lid: 43980  
    Lid: 16354   StoreEc: 0x80040115
    Lid: 38985   StoreEc: 0x80040115
    Lid: 20098  
    Lid: 20585   StoreEc: 0x80040115
   at Microsoft.Mapi.MapiExceptionHelper.InternalThrowIfErrorOrWarning(String message, Int32 hresult, Boolean allowWarnings, Int32 ec, DiagnosticContext diagCtx, Exception innerException)
   at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, IExInterface iUnknown, Exception innerException)
   at Microsoft.Mapi.MapiEventManager.ReadLastEvent(Boolean includeSid)
   at Microsoft.Exchange.Search.Mdb.MapiUtil.<>c__DisplayClass1`1.<TranslateMapiExceptionsWithReturnValue>b__0()
   at Microsoft.Exchange.Search.Mdb.MapiUtil.TranslateMapiExceptions(IDiagnosticsSession tracer, LocalizedString errorString, Action mapiCall)
   --- End of inner exception stack trace ---
   at Microsoft.Exchange.Search.Mdb.MapiUtil.TranslateMapiExceptions(IDiagnosticsSession tracer, LocalizedString errorString, Action mapiCall)
   at Microsoft.Exchange.Search.Mdb.MapiUtil.TranslateMapiExceptionsWithReturnValue[TReturnValue](IDiagnosticsSession tracer, LocalizedString errorString, Func`1 mapiCall)
   at Microsoft.Exchange.Search.Mdb.NotificationsEventSource.ReadLastEvent()
   at Microsoft.Exchange.Search.Mdb.NotificationsEventSource.GetNetworkLatency(Int32 samples)
   at Microsoft.Exchange.Search.Engine.SearchFeedingController.CalculateNumberOfFeederSessions()
   at Microsoft.Exchange.Search.Engine.SearchFeedingController.InitializeFastFeederAndWatermarkStorage()
   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)

In addition, I'm seeing this;

Get-MailboxDatabaseCopyStatus -Server servername| fl identity, ContentIndexErrorMessage

Erorr ID 2136 MSExchangeRepl

Unable to communicate with the Microsoft Exchange Information Store service to coordinate log truncation for database 'DB10\DRSERVER' due to an RPC communication failure. Error: 3355379671
Extended error: Failed to open a log truncation context to source server 'hoserver.domain.com'. Hresult: 0xc7ff07d7. Error: Failed to open a log truncation context because the Microsoft Exchange Information Store service is not running.

Exchange Environment

Head Office - 2 Std (Version 15.0 ‎Build 1236.3)‎
DR Site - 1 Std (Version 15.0 ‎Build 1236.3)

Can you please guide me.

Thank you.

Regards,

Jude

Hi Team, 

I am new to Exchange Server 2013 and Would like to know the detailed Procedure to setup High Availability or DR site for Exchange 2013. This would be our site -B

Current setup in Main Site- A 

1. Single Forest , Single Domain in Windows 2012

2. 2x CAS servers and 2 X Mailbox Servers 

Appreciate Your support to setup the High Availability replication from the start.

Regards

Ahmed123 

iahmed123

Hello,

We are using Exchange 2013 cu21 , we have 2 cas servers (1pr/1dr) and 3 mailbox servers (2pr/1dr). Today i tried to update one of the mailbox server on production. When the update finished, i restarted the vm. I run test-replicationhealth on this server and i get the following output:

Server          Check                      Result     Error
------          -----                      ------     -----
PREXC1          ClusterService             Passed
PREXC1          ReplayService              Passed
PREXC1          ActiveManager              Passed
PREXC1          TasksRpcListener           Passed
PREXC1          TcpListener                Passed
PREXC1          ServerLocatorService       Passed
PREXC1          DagMembersUp               Passed
PREXC1          MonitoringService          Passed
PREXC1          ClusterNetwork             Passed
PREXC1          QuorumGroup                Passed
PREXC1          DatabaseRedundancy         Passed
PREXC1          DatabaseAvailability       Passed
PREXC1          DBCopySuspended            Passed
PREXC1          DBCopyFailed               *FAILED*   Continuous Replication for database 'Mailbox DB01\PREXC1' is i...
PREXC1          DBInitializing             Passed
PREXC1          DBDisconnected             Passed
PREXC1          DBLogCopyKeepingUp         Passed
PREXC1          DBLogReplayKeepingUp       Passed

Then i tried a get-MailboxDatabaseCopyStatus... here is the output:

Name                                          Status          CopyQueue ReplayQueue LastInspectedLogTime   ContentIndex
                                                              Length    Length                            State
----                                          ------          --------- ----------- --------------------   ------------
Mailbox DB01\PREXC1                           Failed          2808      0           3/11/2019 9:18:33 AM   Healthy

The CopyQueue Length is increasing, i checked that by re-running the MailboxDatabaseCopyStatus after 20mins.

What i have to do to have a healthy database again? If i restart the vm it will change anything or not?

Thank you

Hi Folks,

We want to do DR test for Exchange Server 2013, Basically we want to run the mailbox and client access services from DR Exchange.

HQ Site:

Two Domain Controllers, Two Exchange Servers ( CAS and MBX role )

DR Site:

One Domain Controller, One Exchange Server ( CAS and MBX role )

DAG is configured and its working fine, Test replication output is passed for all tests.

We are having Public IP for MX and Internet at DR site, So that we can do inbound and outbound email tests from DR site.

I need some more information or document step by step to test and make it successful.

Thanks

Hi Everyone,

A client of mine is using a shared exchange 2013 in a 2 node dag environment 
one of the servers is damaged and needs to be replaced but unfortunately that specific server doesn't have a backup

can some one please help me with what are the proper steps needs to be done so i can replace the damaged server?

I have 2 different exchange 2013 servers which i load between them by haproxy... i have a public ip address and i have a problem that is i cant redirect smtp,imap and pop3 ports to the servers at the same time
this is my haproxy.cfg config file which is not working until i remove on server it works for only one like 192.168.100.23 and the other not working 192.168.100.21

 global
log 127.0.0.1 syslog
chroot /var/lib/haproxy
stats socket /run/haproxy/admin.sock mode 660 level admin
stats timeout 30s
user haproxy
group haproxy
daemon

# Default SSL material locations
#ca-base /etc/ssl/certs
#crt-base /etc/ssl/private

# Default ciphers to use on SSL-enabled listening sockets.
# For more information, see ciphers(1SSL). This list is from:
#  https://hynek.me/articles/hardening-your-web-servers-ssl-ciphers/
# An alternative list with additional directives can be obtained from
#  https://mozilla.github.io/server-side-tls/ssl-config-generator/?server=haproxy
#ssl-default-bind-ciphers ECDH+AESGCM:DH+AESGCM:ECDH+AES256:DH+AES256:ECDH+AES128:DH+AES:RSA+AESGCM:RSA+AES:!aNULL:!MD5:!DSS
tune.ssl.default-dh-param 4096
ssl-default-bind-options no-sslv3 no-tls-tickets
ssl-default-bind-ciphers EECDH+AESGCM:EDH+AESGCM:AES256+EECDH:AES256+EDH
defaults
log global
mode    http
option  httplog
option  dontlognull
    timeout connect 5000
    timeout client  50000
    timeout server  50000
errorfile 400 /etc/haproxy/errors/400.http
errorfile 403 /etc/haproxy/errors/403.http
errorfile 408 /etc/haproxy/errors/408.http
errorfile 500 /etc/haproxy/errors/500.http
errorfile 502 /etc/haproxy/errors/502.http
errorfile 503 /etc/haproxy/errors/503.http
errorfile 504 /etc/haproxy/errors/504.http
listen stats
bind *:9090
mode  http
maxconn  10
stats  enable
stats  hide-version
stats  realm Haproxy\ Statistics
stats  uri /
stats  auth admin:admin
frontend haproxy_in
bind *:80
#bind *:443 ssl crt /etc/haproxy/certs/server.com.pem crt /etc/haproxy     /certs/server1.com.pem
mode http
# Define Path For LetsEncrypt.........................
acl is_letsencrypt path_beg -i /.well-known/acme-challenge/
use_backend letsencrypt if is_letsencrypt
# Define hosts........................................
acl is_metro hdr_dom(host) -i server.com
acl is_lib hdr_dom(host) -i server1.com
# Direct hosts to backend..............................
use_backend metro if is_metro
use_backend sindyan if is_sindyan
default_backend metro
# Redirect port 80 t0 443 except lets encrypt............
redirect scheme https code 301 if !{ ssl_fc } !is_letsencrypt
 backend letsencrypt
server letsencrypt 127.0.0.1:8888
 backend metro
balance roundrobin
mode http
server vm1 192.168.100.21:80/owa check
backend sindyan
balance roundrobin
mode http
server vm3 192.168.100.23:80/owa check
frontend SMTP
bind *:25
mode tcp
default_backend smtp
 backend smtp
balance roundrobin
mode tcp
server vm3 192.168.100.21:25 check
    server vm4 192.168.100.23:25 check
 frontend SMTP_Secure
  bind *:587
mode tcp
# Define hosts........................................
default_backend smtps
    backend smtps
balance roundrobin
mode tcp
server vm3 192.168.100.21:587check
    server vm4 192.168.100.23:587 check
 frontend SMTP_S
bind *:465
mode tcp
 default_backend ss
 backend ss
balance roundrobin
mode tcp
server vm7 192.168.100.21:465 check
    server vm8 192.168.100.23:465 check
frontend pop3_S
bind *:995
mode tcp
 default_backend pops
backend pops
balance roundrobin
mode tcp
server vm9 192.168.100.21:995  check
server vm10 192.168.100.23:995 check
frontend pop3
bind *:110
mode tcp
 default_backend pop
  backend pop
balance roundrobin
mode tcp
server vm11 192.168.100.21:110 check
server vm12 192.168.100.23:110 check
 frontend IMAP
bind *:143
mode tcp
default_backend IMAP
 backend IMAP
balance roundrobin
mode tcp
server vm13 192.168.100.21:143 check
server vm14 192.168.100.23:143 check
 frontend IMAPS
bind *:993
mode tcp
default_backend IMAPS
 backend IMAPS
balance roundrobin
mode tcp
server vm15 192.168.100.21:993 check
server vm16 192.168.100.23:993 check
so please help me to make all tcp ports serves both  servers at 
the same time without roundroben method i need them directly routed for 
each exchange server
thanks  

repair white point خدمة فورا لجهزة ثلاجة وايت بوينت (01093055835 دار السلام  01223179993 )

الارقام الساخنه للاتصال ب خدمة عملاء اجهزة توشيبا المنزلية || ثلاجه,غساله,غسالات,ثلاجات ,غساله اطباق,غسالات ‏اطباق,ديب فريزر ,فريزر ,مجفف, دراير , لاندرى ,ايس ميكر ,ثلاجات نبيذ,ثلاجة نوفرست,ثلاجة,غسالة,غسالة اطباق,غسالة ‏ملابس

‏ || 01129347771  || 01207619993 || 01223179993   ||  ||  ||    || 01129347771  || 01207619993 || 01223179993   ||  || 01129347771  || 01207619993 || 01223179993 ‏

صيانة توشيبا المعادى |||| صيانة توشيبا محافظة الاسكندرية |||| مركز خدمة توشيبا التجمع الخامس |||| افضل اصلاح توشيبا عين شمس |||| خدمة اصلاح ‏توشيبا مصر الجديدة |||| تصليح توشيبا مدينة نصر |||| توكيل توشيبا الزمالك |||| اصلاح توشيبا شبرا |||| اسرع صيانة ‏توشيبا حدائق المعادى |||| صيانة كلفينيتور محافظة الاسكندرية |||| اماكن تصليح توشيبا حدائق الهرم |||| شركة صيانة توشيبا الزيتون |||| شركة توكيل توشيبا ‏روكسى |||| احدث صيانة توشيبا العباسية |||| توكيل توشيبا العمرانية |||| اول مركز توكيل توشيبا الجيزة |||| اماكن تصليح ‏توشيبا المريوطية |||| متميزون صيانة توشيبا غمره |||| ارشادات توكيل توشيبا كورنيش النيل |||| موقع صيانة توشيبا ‏‏|||| دليل توكيل توشيبا المقطم |||| خدمة اصلاح توشيبا الهرم |||| المركز الرئيسى توشيبا الازهر |||| مراكز متخصصة ‏توشيبا جسر السويس |||| احسن استجابة توشيبا غمره |||| مبتكرون صيانة توشيبا القطامية |||| متطورين صيانة توشيبا ‏الضاهر |||| فروع توكيل توشيبا 6 اكتوبر |||| محترفون صيانة توشيبا شبرا الساحل |||| اخيرا توكيل توشيبا امبابه |||| احسن ‏تقنية توشيبا القاهرة الجديدة |||| صيانة توشيبا الدقى |||| الوكيل توشيبا فيصل |||| اضمن اصلاح توشيبا الشيخ زايد‎‎

توشيبا المعادى, توشيبا المنيل , توشيبا وادى حوف , توشيبا حلوان , توشيبا 15 مايو , توشيبا القطامية , ‏‏ توشيبا المقطم , توشيبا التجمع ,  توشيبا التجمع الاول , توشيبا التجمع الخامس ,  توشيبا القاهرة الجديدة , ‏توشيبا مدينة نصر ,  توشيبا الرحاب , توشيبا عمارات العبور , توشيبا شيراتون مصر الجديدة , توشيبا ‏توشيبا مدينتى ,   توشيبا الشروق , توشيبا العبور, توشيباالنزهه ,  توشيبا النزهه الجديده , توشيبا مصر ‏الجديدة , توشيبا الكوربه ,  توشيبا العباسية ,  توشيبا الزيتون , توشيبا جسر السويس ,  توشيبا عين شمس , ‏توشيبا المطرية , توشيبا القبه ,  توشيبا حدائق القبه , توشيبا الدمرداش , توشيبا الضاهر,  توشيبا  ‏رمسيس, توشيبا وسط البلد , توشيبا شبرا مصر , توشيبا جاردن سيتى ,  توشيبا بولاق ابو العلا , توشيبا ‏الزمالك ,  توشيبا الكيت كات ,  توشيبا العجوزه , توشيبا الدقى ,  توشيبا التحرير ,  توشيبا السيدة زينب , ‏توشيبا القصر العينى ,  توشيبا الدمرداش , توشيبا المهندسين , توشيبا بين السرايات, توشيبا الجيزة , ‏توشيبا ميدان الجيزة ,  توشيبا 6 اكتور ,  توشيبا السادس من اكتوبر ,  توشيبا الشيخ زايد , توشيبا  بفلى هيلز ‏‏,توشيبا نبو جيزة ,‏‎‎توشيبا الهرم ,توشيبا فيصل , توشيبا المريوطية ,توشيبا حدائق الهرم ,توشيبا ‏العمرانية,توشيبا الطالبية , توشيبا المرج ,توشيبا القرية الذكية ,الكترو ستار هضبة الهرم , توشيبا الاهرام ‏‏,توشيبا ابو الهول,توشيبا المنيب

‎  repair toshiba                                    ‎ثلاجات توشيبا )‏‎  )      repairing toshiba     ‎

service toshiba                                        ‎‏( غسالات توشيبا )‏‎    center toshiba      ‎

malfunction toshiba                                 ‎‏( ارقام صيانة توشيبا )‏‎  maintenance toshiba      ‎

agent toshiba                                        ‎‏(غساله توشيبا )‏‎     agents toshiba                                                                                            ‎

authorization toshiba                              ‎‏( غساله اطباق توشيبا )‏‎  workshops toshiba      ‎

customer service toshiba                    ‎‏( غسالات ملابس )‏‎     engineers toshiba      ‎

specialists toshiba                                  ‎‏( ديب فريزر )‏‎  Technical support toshiba      ‎

support reform toshiba                     ‎‏( لاندرى )‏‎    support repair toshiba               ‎

agent toshiba                                ‎‏( ايس ميكر )‏

toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      ‎toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      ‎toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      ‎toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      toshiba     toshiba      ‎toshiba     toshiba      toshiba      toshiba      toshiba      toshiba     toshiba      toshiba     ‎

الادارة فى انتظار اتصالاتكم : _ 01129347771  || 01207619993 || 01223179993  ‏

I have multiple exchange 2013 Servers in DAG both in DC and DR site. In many of these servers my exchange replication service is terminating unexpectedly multiple times in a day with below error .

Event id 4399

The Microsoft Exchange Replication service is terminating without collecting a Watson dump. Error The Microsoft Exchange Replication service is using too much memory (4100.6171875 MiB) and will be terminated without collecting a Watson dump. This exceeds the maximum expected value of 4096 MiB. To take a dump along with the Watson report, set registry key 'SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters\EnableWatsonDumpOnTooMuchMemory' to 1. Default can be overridden by setting registry key RegKeyBase=SOFTWARE\Microsoft\ExchangeServer\v15\Replay\Parameters;RegValues=MaximumProcessPrivateMemoryMB,MemoryLimitBaseInMB,MemoryLimitPerDBInMB;EffectiveLimit=Min(MaximumProcessPrivateMemoryMB,MemoryLimitBaseInMB+nCopies*MemoryLimitPerDBInMB)

I searched for this error and got to know that its a known issue in exchange and the followed below article to apply the workaround 

https://support.microsoft.com/en-us/help/2892330/msexchangerepl-exe-process-terminates-when-you-try-to-replay-more-than

Even after applying the workaround, though the frequency has reduced by half but still the service is getting terminated with same error, just that now the error is saying that "This exceeds the maximum expected value of 6240 MiB"

prior to applying workaround the event id used to show limit as 4096.

I have applied below registry settings as per the tech net article.

Problem: Exchange logs are not flushing after backup exec runs full backup.

The backup in backup exec 2010 R3 Is successful. It is also set to do full backup/flush logs

The logs fill up to around 50,000 files or more. How do you fix this?

ENV: exchange 2010 SP2 Rollup 4 Dag.

I see the following in the logs on database server when backup exec is complete.

Information Store (2972) Mailbox Database Faculty: The backup procedure has been successfully completed.

Information Store (2972) There were 75299 log file(s) not found in the log range (D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database Faculty\E030003BA9C.log - D:\Program Files\Microsoft\Exchange Server\V14\Mailbox\Mailbox Database Faculty\E030004EA5F.log) that we attempted to truncate.

Just discussing ....  I am not finding much information on the internet regarding CAS 2013 NLB High availability in DR
scenario so planned to discuss and get some ideas/guidance 

Site-A

Domain Controllers x2
3 CAS servers with hardware LB
3 mbx servers in DAG1
FSWitness Server
SAN Wildcard Certificate
Exernal URL: webmail.domain.com/owa
Internal URL: autodiscover.domain.com

Site-B  (DR) with Stretched DAG
Domain Controllers x3
3 CAS Servers with wNLB
2 mbx server in the same DAG1  (Stretched)
Alt FSWitness server
External URL: webmail.domain.com/owa
Internal URL: autodiscoverDR.domain.com

Question:

When Site-A goes down ..... 
I understand the other steps which need to be taken but my question is 

in DR Site, do I point my internal URLs to the mbx servers using the same
commands to set the virtual directories as usual and point them to the new mbx servers dbs?

And when the primary site comes back up follow the same steps to revert back?  I am bit unclear on this part?

Thank you

We are running an Exchange 2010 SP3 UR27 environment on Windows Server 2008 R2. I am aware that support for Exchange 2010 is ending soon, and we are planning to migrate to a newer platform before then. I am seeing issues with database files being in use by another process, when failing over to other Exchange Mailbox Servers which subsequently causes a crash of the Information Store.

We are running a DAG on 6 physical servers, with 4 copies of each database. The system is running fine on a daily basis, but when failing over databases to other servers, problems starts to occur. The Event Viewer reports:

mxexchangerepl (6860) An attempt to open the file "C:\ExchangeStorage\DiskX\DBX\DBX.edb" for read only access failed with system error 32 (0x00000020): "The process cannot access the file becaise it is being used by another process.". The open file operation will fail with error -1032 (0xfffffbf8).

There is no antivirus on the server or similar security software that scans files.

There aren't any connections to shares, other than other Exchange Database Servers in the DAG.

All databases have Circular Logging enabled and running daily backups through DPM, where we see problems with backups hanging.

Receive-Side Scaling State (RSS) and Chimney Offload State are both disabled.

Does anybody have any ideas what else could cause such issues?

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 All,

I'm facing issue during installation Exchange Server 2013 Cumulative Update 22 on secondary Exchange server. For information,my organization have deploy DAG environment and both server MAIL01 and MAIL02 is running on Exchange server 2013. Yesterday I've successful install CU22 on MAIL01, and today I'm tried to do that on MAIL02. During installation CU22 on MAIL02, the installation was stop due to below error:

Exchange Server component Mailbox role: Transport service failed.

Error: Error:

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

       if (get-service MSExchangeServiceHost* | where {$_.name -eq "MSExchangeServiceHost"})

       {

           restart-service MSExchangeServiceHost

       }

       " was run: "Microsoft.PowerShell.Commands.ServiceCommandException: Service 'Microsoft Exchange Service Host (MSExchangeServiceHost)' cannot be started due to the following error: Cannot start service MSExchangeServiceHost on computer '.'. ---> System.InvalidOperationException: Cannot start service MSExchangeServiceHost on computer '.'. ---> System.ComponentModel.Win32Exception: The dependency service or group failed to start

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

  at System.ServiceProcess.ServiceController.Start(String[] args)

  at Microsoft.PowerShell.Commands.ServiceOperationBaseCommand.DoStartService(ServiceController serviceController)

  --- End of inner exception stack trace ---".

  I'm tried to figure out by google any info but not luck to solve this case. Also I notice all Exchange services on MAIL02 not running and cannot start even startup is automatic. I've tried to reboot the MAIL02 few times and re-install CU22 but installation Setup not prompt.

For time being, I'm only active the MAIL01 as primary and database mailbox copies on MAIL02 still remain suspended.

Appreciate if you could assist on this issue.

Best regards, Matt Fauzy

We had two Exchange Server 2013 Enterprise servers in our organization.

Both servers were on the same CU with that exact same updates.

Server A crashed and won't be recovered.

We need to mount DB's from server A to server B.

In ECP on B it shows the list of DBs and mailboxes that were on A, but of course they cannot be accessed.

We have the DB's from A and they show a clean shutdown state.

How do we restore a DB to a different Exchange server when the ECP on that server can't contact server A (because it keeps trying)??

This is obviously critical so any help would be appreciated.

Alert from Microsoft Forum

Dear Team,

I have rebuilt my failed CAS02 server from trash and run setup/recovery and installed the valid certificate for OWA/RPC.

CAS01 and CAS02 were in Windows NLB. CAS01 is working fine. Before I add back CAS02 to NLB, I want to make sure all roles and services are up and running on this CAS02 server.  When I run Exchange Management Shell (as Admin) I am getting errors..

ERROR:

VERBOSE: Connecting to CAS02.Company.local 

[cas02.company.local] Connecting to remote server failed with the following error message : The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more information, see the about_Remote_Troubleshooting Help topic. 

    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [], PSRemotingTransportException

    + FullyQualifiedErrorId : PSSessionOpenFailed

VERBOSE: Connecting to CAS01.company.local

Kindly guide me the steps (or article) to add local roles on this CAS02 server

(excuse me as I know Exchange 2010 is nearing support expiry)

Thanks and Regards,