Hi.

I have been restoring the entire Windows after a bigger problem in the past. However, there were data for Exchange server at a completely different disk which was not affected.

But now I can not load up OWA and when you look in the ECP so says the following under databases "Content index state: Failed"

I have tried to repair it but without any success.

The operation couldn't be performed because object '0747478411\MAIL-SERVER01' couldn't be found on 'server'.
    + CategoryInfo          : NotSpecified: (:) [Update-MailboxDatabaseCopy], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : DD4CF704,Microsoft.Exchange.Management.SystemConfigurationTasks.UpdateDatabaseCopy

    + PSComputerName        : mail-server01

Update-MailboxDatabaseCopy "0747478411\MAIL-SERVER01" -CatalogOnly

All i have in owa now is

I have seen similar posts about this issue but none of which that I have seen address this issue on the Win Server 2012 DC/Exchange 2013 RTM platforms.

I am attempting to get my backup software to perform an appropriate backup of my Exchange 2013 server. I am currently using Symantec Backup Exec 2015 (Version 14.2).

Each back up I run consistently fails as soon as it attempts to back up my Exchange Mailbox Database files. The errors for BE 14.2 is also consistent over the 30 backups that I have ran and failed to complete.

"V-79-57344-65233 - Snapshot Technology: Initialization failure on: "\\[Server_Name.local]\Microsoft Information Store\Mailbox Database 0936435715". Snapshot technology used: Microsoft Volume Shadow Copy Service (VSS).
 
Snapshot technology error (0xE000FED1): A failure occurred querying the Writer status. See the job log for details about the error.
 
Check the Windows Event Viewer for details.

Writer Name: Exchange Server, Writer ID: {76FE1AC4-15F7-4BCD-987E-8E1ACB462FB7}, Last error: The VSS Writer failed, but the operation can be retried (0x800423f3), State: Stable (1)."

I have worked extensively with Symantec's tech support and we have moved to the issue being with the server itself and not Backup Exec, especially since all of my other servers are backing up properly. After reading up on Writers I logged in to our mail server and ran a Admin CMD and ran the command VSSADMIN LIST WRITERS.

The all of my writers except the following showed as stable.

Writer name: 'Microsoft Exchange Writer'
   Writer Id: {76fe1ac4-15f7-4bcd-987e-8e1acb462fb7}
   Writer Instance Id: {55b98a96-98f3-48e1-b2e8-4b94dc769ef0}
   State: [7] Failed
   Last error: Retryable error

Symantec informs me that with this writer being unstable, all of my backups will continue to fail and that they cannot assist me any more unless this issue is resolved.

At the current time our ability to apply the Cumulative updates and service packs to Exchange 2013 is not possible. We don't have any one on hand that has enough knowledge in Exchange to do this work and we are a bit stuck.

Any help with a hotfix that has been released or some kind of work around would be amazing. I just wish I had the knowledge to figure this out on my own, but after 9 days of trying to fix this and being told by Symantec that it is a Windows/Exchange problem.

How can users send email messages if the Exchange Server goes offline?

Is there a system that can be setup in case of server failure?

Thanks in advance. 

Hi All ,

In my environment we have a setup like below.

Production site -  Active site - All the mailbox users are connected to this site 

2 mailbox servers site 

DR site - Passive site 

1 Mailbox server 

Scenario : All the three mailbox servers are in DAG .Let assume i have an cluster resources is online on the mailbox server in the DR site because of that mailbox server on the DR site is having the PAM role .So on such case i facing the WAN outage between the production site and DR site .

Question : 

While i face the above scenario i will be having majority of nodes in production site.At the same time i would like to know which server in the production site will hold the PAM role after WAN outage ? Or else cluster resources will go offline on the node at DR site and also will it make the mounted databases on the production servers to dismounted state ?

Thanks & Regards S.Nithyanandham

    My computer system administrator is remoted by another network Administrator, so its to to access my own system,, I used my own computer as a host user only,, my IP address and mac address is unavailable, im chatting to Microsoft help desk and they to trying to access my computer via internet it uppear in computer her network problem, I explore all option using general Pc setting i use another computer to downlad the program via external and install to my pc nothing happen, my c:drive is 0bytes,, i try to expand or manage but nothing hapenn,

Hi,

I have 2 2013 Exchange servers in a DAG configuration. The passive member (I'll refer to it as EX02) is experiencing an issue where the Cluster Service crashes almost immediately after it is started. I've experienced this with this particular DAG before and ultimately ended up rebuilding the entire DAG from scratch to fix the issue, however it seems to have returned and now need a root cause analysis and fix. I've attached 4 Event Logs that have allowed me to drill down to the problem component but am at a loss on how to proceed next.  Initially, when checking the cluster using Failover Cluster Manager, the EX02 node goes back and forth between "Joining" and "Down". This is a result of the Cluster Service constantly crashing and restarting since it is set to auto restart after an unexpected termination.  

Looking at the 1146 Event ID, I saw this points to the Resource Hosting Subsystem as part of the issue and that this process experienced an issue with a .dll it's using.  I then discovered this was the KERNELBASE.dll via the various other log entries I've included below. I haven't been able to find anyone else that's ran into this particular scenario and am not sure what needs to be done to correct this behavior. If anyone has any insight to this issue, it would be greatly appreciated. If any additional information is needed from me, please let me know as well. 

 Log Name:      System
Source:        Microsoft-Windows-FailoverClustering
Date:          3/3/2015 2:34:59 PM
Event ID:      1146
Task Category: Resource Control Manager
Level:         Critical
Keywords:      
User:          SYSTEM
Computer:      ****-EX02.****.com
Description:
The cluster Resource Hosting Subsystem (RHS) process was terminated and will be restarted. This is typically 
associated with cluster health detection and recovery of a resource. Refer to the System event log to determine which 
resource and resource DLL is causing the issue.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-FailoverClustering" Guid="{BAF908EA-3421-4CA9-9B84-6689B8C6F85F}" />
    <EventID>1146</EventID>
    <Version>0</Version>
    <Level>1</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-03T20:34:59.261068900Z" />
    <EventRecordID>286364</EventRecordID>
    <Correlation />
    <Execution ProcessID="4716" ThreadID="4996" />
    <Channel>System</Channel>
    <Computer>****-EX02.****.com</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <EventData>
    <Data Name="NodeName">****-EX02</Data>
  </EventData>
</Event>     

Log Name:      Application
Source:        Application Error
Date:          3/3/2015 2:36:13 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ****-EX02.****.com
Description:
Faulting application name: clussvc.exe, version: 6.3.9600.17396, time stamp: 0x5434db7b
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17415, time stamp: 0x54505737
Exception code: 0x80000003
Fault offset: 0x00000000000de002
Faulting process id: 0x31c8
Faulting application start time: 0x01d055f1a860f6f2
Faulting application path: C:\Windows\Cluster\clussvc.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: ee64313c-c1e4-11e4-80da-005056010d14
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="2015-03-03T20:36:13.000000000Z" />
    <EventRecordID>264219</EventRecordID>
    <Channel>Application</Channel>
    <Computer>****-EX02.****.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>clussvc.exe</Data>
    <Data>6.3.9600.17396</Data>
    <Data>5434db7b</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.3.9600.17415</Data>
    <Data>54505737</Data>
    <Data>80000003</Data>
    <Data>00000000000de002</Data>
    <Data>31c8</Data>
    <Data>01d055f1a860f6f2</Data>
    <Data>C:\Windows\Cluster\clussvc.exe</Data>
    <Data>C:\Windows\system32\KERNELBASE.dll</Data>
    <Data>ee64313c-c1e4-11e4-80da-005056010d14</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Windows Error Reporting
Date:          3/3/2015 2:36:14 PM
Event ID:      1001
Task Category: None
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      ****-EX02.****.com
Description:
Fault bucket , type 0
Event Name: APPCRASH
Response: Not available
Cab Id: 0

Problem signature:
P1: clussvc.exe
P2: 6.3.9600.17396
P3: 5434db7b
P4: KERNELBASE.dll
P5: 6.3.9600.17415
P6: 54505737
P7: 80000003
P8: 00000000000de002
P9: 
P10: 

Attached files:

These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_clussvc.exe_fcdf2bbcddca922c916880dbb49ce3cd5175efef_f6feed2
e_3a22d925

Analysis symbol: 
Rechecking for solution: 0
Report Id: ee64313c-c1e4-11e4-80da-005056010d14
Report Status: 4100
Hashed bucket: 
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Windows Error Reporting" />
    <EventID Qualifiers="0">1001</EventID>
    <Level>4</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-03-03T20:36:14.000000000Z" />
    <EventRecordID>264220</EventRecordID>
    <Channel>Application</Channel>
    <Computer>****-EX02.****.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>APPCRASH</Data>
    <Data>Not available</Data>
    <Data>0</Data>
    <Data>clussvc.exe</Data>
    <Data>6.3.9600.17396</Data>
    <Data>5434db7b</Data>
    <Data>KERNELBASE.dll</Data>
    <Data>6.3.9600.17415</Data>
    <Data>54505737</Data>
    <Data>80000003</Data>
    <Data>00000000000de002</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>C:\ProgramData\Microsoft\Windows\WER\ReportQueue\AppCrash_clussvc.exe_fcdf2bbcddca922c916880dbb49ce3cd5175e
fef_f6feed2e_3a22d925</Data>
    <Data>
    </Data>
    <Data>0</Data>
    <Data>ee64313c-c1e4-11e4-80da-005056010d14</Data>
    <Data>4100</Data>
    <Data>
    </Data>
  </EventData>
</Event>

Version=1
EventType=APPCRASH
EventTime=130698881964369580
ReportType=2
Consent=1
ReportIdentifier=0d8e824c-c1e4-11e4-80da-005056010d14
IntegratorReportIdentifier=0d8e824b-c1e4-11e4-80da-005056010d14
NsAppName=clussvc.exe
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=clussvc.exe
Sig[1].Name=Application Version
Sig[1].Value=6.3.9600.17396
Sig[2].Name=Application Timestamp
Sig[2].Value=5434db7b
Sig[3].Name=Fault Module Name
Sig[3].Value=KERNELBASE.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.3.9600.17415
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=54505737
Sig[6].Name=Exception Code
Sig[6].Value=80000003
Sig[7].Name=Exception Offset
Sig[7].Value=00000000000de002
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.3.9600.2.0.0.272.7
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=a80b
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=a80b5d7481362c8eeb76a77903fa82d6
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=a1f8
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=a1f83374660c205ca4489043b9691b2f
UI[2]=C:\Windows\Cluster\clussvc.exe
UI[5]=Check online for a solution (recommended)
UI[6]=Check for a solution later (recommended)
UI[7]=Close
UI[8]=Microsoft Failover Cluster Service stopped working and was closed
UI[9]=A problem caused the application to stop working correctly. Windows will notify you if a solution is available.
UI[10]=&Close
LoadedModule[0]=C:\Windows\Cluster\clussvc.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\KERNEL32.DLL
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\msvcrt.dll
LoadedModule[5]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[6]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[7]=C:\Windows\SYSTEM32\CLUSAPI.dll
LoadedModule[8]=C:\Windows\system32\CRYPT32.dll
LoadedModule[9]=C:\Windows\SYSTEM32\dhcpcsvc.DLL
LoadedModule[10]=C:\Windows\SYSTEM32\IPHLPAPI.DLL
LoadedModule[11]=C:\Windows\SYSTEM32\NTDSAPI.dll
LoadedModule[12]=C:\Windows\system32\ole32.dll
LoadedModule[13]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[14]=C:\Windows\SYSTEM32\RESUTILS.dll
LoadedModule[15]=C:\Windows\system32\RPCRT4.dll
LoadedModule[16]=C:\Windows\SYSTEM32\SspiCli.dll
LoadedModule[17]=C:\Windows\SYSTEM32\sscore.dll
LoadedModule[18]=C:\Windows\system32\USER32.dll
LoadedModule[19]=C:\Windows\SYSTEM32\VSSAPI.DLL
LoadedModule[20]=C:\Windows\SYSTEM32\wevtapi.dll
LoadedModule[21]=C:\Windows\system32\WS2_32.dll
LoadedModule[22]=C:\Windows\system32\NSI.dll
LoadedModule[23]=C:\Windows\SYSTEM32\WINNSI.DLL
LoadedModule[24]=C:\Windows\SYSTEM32\FirewallAPI.dll
LoadedModule[25]=C:\Windows\SYSTEM32\bcrypt.dll
LoadedModule[26]=C:\Windows\SYSTEM32\NETAPI32.dll
LoadedModule[27]=C:\Windows\SYSTEM32\FLTLIB.DLL
LoadedModule[28]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[29]=C:\Windows\SYSTEM32\DEVOBJ.dll
LoadedModule[30]=C:\Windows\SYSTEM32\fwpuclnt.dll
LoadedModule[31]=C:\Windows\SYSTEM32\VirtDisk.dll
LoadedModule[32]=C:\Windows\SYSTEM32\clfsw32.dll
LoadedModule[33]=C:\Windows\SYSTEM32\DSPARSE.dll
LoadedModule[34]=C:\Windows\SYSTEM32\cryptdll.dll
LoadedModule[35]=C:\Windows\system32\MSASN1.dll
LoadedModule[36]=C:\Windows\SYSTEM32\combase.dll
LoadedModule[37]=C:\Windows\system32\GDI32.dll
LoadedModule[38]=C:\Windows\SYSTEM32\VssTrace.DLL
LoadedModule[39]=C:\Windows\SYSTEM32\DSROLE.dll
LoadedModule[40]=C:\Windows\SYSTEM32\bcd.dll
LoadedModule[41]=C:\Windows\SYSTEM32\netutils.dll
LoadedModule[42]=C:\Windows\SYSTEM32\srvcli.dll
LoadedModule[43]=C:\Windows\SYSTEM32\wkscli.dll
LoadedModule[44]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[45]=C:\Windows\SYSTEM32\DPAPI.DLL
LoadedModule[46]=C:\Windows\SYSTEM32\CRYPTBASE.dll
LoadedModule[47]=C:\Windows\SYSTEM32\SAMCLI.DLL
LoadedModule[48]=C:\Windows\SYSTEM32\bcryptPrimitives.dll
LoadedModule[49]=C:\Windows\SYSTEM32\sscoreext.dll
LoadedModule[50]=C:\Windows\SYSTEM32\mi.dll
LoadedModule[51]=C:\Windows\SYSTEM32\miutils.dll
LoadedModule[52]=C:\Windows\system32\wmidcom.dll
LoadedModule[53]=C:\Windows\SYSTEM32\kernel.appcore.dll
LoadedModule[54]=C:\Windows\SYSTEM32\ntmarta.dll
LoadedModule[55]=C:\Windows\SYSTEM32\dhcpcsvc6.DLL
LoadedModule[56]=C:\Windows\SYSTEM32\clbcatq.dll
LoadedModule[57]=C:\Windows\system32\wbem\wbemprox.dll
LoadedModule[58]=C:\Windows\SYSTEM32\wbemcomn.dll
LoadedModule[59]=C:\Windows\SYSTEM32\CRYPTSP.dll
LoadedModule[60]=C:\Windows\system32\rsaenh.dll
LoadedModule[61]=C:\Windows\system32\wbem\wbemsvc.dll
LoadedModule[62]=C:\Windows\system32\wbem\fastprox.dll
LoadedModule[63]=C:\Windows\SYSTEM32\pcwum.dll
LoadedModule[64]=C:\Windows\system32\mswsock.dll
LoadedModule[65]=C:\Windows\system32\WINTRUST.dll
LoadedModule[66]=C:\Windows\SYSTEM32\logoncli.dll
LoadedModule[67]=C:\Windows\SYSTEM32\DNSAPI.dll
LoadedModule[68]=C:\Windows\System32\rasadhlp.dll
LoadedModule[69]=C:\Windows\system32\kerberos.DLL
LoadedModule[70]=C:\Windows\SYSTEM32\SAMLIB.dll
LoadedModule[71]=C:\Windows\system32\es.dll
LoadedModule[72]=C:\Windows\system32\PROPSYS.dll
LoadedModule[73]=C:\Windows\SYSTEM32\profapi.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Microsoft Failover Cluster Service
AppPath=C:\Windows\Cluster\clussvc.exe
NsPartner=windows
NsGroup=windows8
ApplicationIdentity=78F1110F74732BD871C9A3C553A667E4

Dear all,

I have an exchange server 2010 sp2 with 2 databases, about 200GB each database. For both databases circular lodging is enabled. Recently I have configured DAG with another server at DR site. The problem is that the one database is fine but the other database logs are growing extremely fast and the disk get full. I have enable circular loging for both databases. does anyone have any idea why this may happen?

Regards

Pantos

hi all,

we are strongly thinking to create a third site in azure and move the witness in for our DAG

We have 2 datacenters = 2 geographic sites = 2 AD sites/ Exchange 2010  migration exchange 2013 soon.

After reading this article several questions spring to mind :

question 1 - MS put a DC in azure :

>Should we create a new ad site ????

> can we configure this dc in azure to be in ad site of Datacenter 1 or Datacenter 2.

> why should we put a dc in azure

question 2  - which networks ports should we open betwen Datacenter and azure ? ldap, DNS and  ???

Regards,



Hi Exchange Expert,

We have in premises exchange server running 2010 SP1. Our Exchange Infra is as below. all of the servers below are in the form of Hyper V VM. so, there are 2 physical server and each of them hosting AD, Transport, and Mailbox.

1. 2x Server 2008 R2 AD for redundancy (for instance: Ad01, Ad02)

2. 2x Exchange Transport Server for redundancy (for instance: Tr01, Tr02)

3. 2x Exchange Mailbox Server for redundancy (for instance: mb01, mb02)

For transport server, we actually implement a cluster using the network load balancing manager, so it could load balance. the name of the cluster is Trcluster, which has two members inside, Tr01 and Tr02.

We have also implement DAG for the the database, mb01 and mb02. so mb01 has the copy of mb02 in the server and vice versa. Beside, we also include 2 members at the remote site servers. this remote site servers also has the transport cluster of RemoteTrCluster, with the members: RemoteTr01, RemoteTr02.

However, now one of the physical server containing the Ad02, Tr02, and Mb02 is down. One thing that we don't understand is how come the exchange transport is not able to failover since we have cluster here. it is failed to run. The database is able to failover, but the transport is not running using the Trcluster. So what we do is to failover the database to remote exchange server and then the exchange transport is able to run using the RemoteTrCluster.

Please give any advise of what is going on in our Exchange infra.

Thanks.

Regards,

For my setup, I have an external hosting service providing us an internet website and external DNS. We have two internet access providers each providing there own static IPs into our Watchguard firewall for failover internet access. When the primary internet access is up, everything works great. When we fail over to the backup internet connection, remote clients can no longer get email from outlook, cell phones etc. I assume this is because my autodiscover DNS entry is pointing to the primary internet access's IP address. Since I have a 2nd MX record setup for the backup IP and the watchguard, the exchange server stays alive, sending and receiving email, and any clients directly connected or VPN connected to our LAN work fine.

Right now, I have a single CAS server, with all the roles except the database/storage and a second server with the database/storage role.

How can I fix this so remote, non-vpn client can have their Outlook or devices get email when we fail over? I know I could DNS round robin, but that isn't the right way to fix this. Besides, my internet pipes are not of equal size.

I am researching options at our disposal and the what could be best practice.

One option would be having SMTP routing between three CAS servers (2 in CA and 1 in AZ). Would this be just adding all three to the same CAS? Is there a possible issue having the third CAS server in another datacenter from the first two?

Another thought is routing SMTP traffic between the two CAS servers in CA and using the AZ server as a failover. If CA comes back online how would that impact AZ? What about a split brain scenario and how to avoid/prevent? 

Finally would it be best to leverage a third-party appliance to do this? I believe this can be handled out of the box.

Thoughts and ideas are welcome.

Thank you,

- Gymmbo

Hi dear Exchange community members !

I'm working on a 2 DAG active/active scenarios where 2 DAG are stretched between 2 datacenters, using one namespace for both datacenters. DNS Round Robin is used to provide load balancing and availability.

I understood that if the datacenter link fail, every active mailbox remain active on each datacenter (reason to use 2 DAGs with each having active database on different datacenter)

However, if the link fail, what is the behaviour of the Outlook or OWA client ?
If the client connect to the dc where the active mbx is, no problem, client get access to his mbx.
However, if the client connect to the dc and the mbx is in the other dc (which is not available because link between the dc failed), what happens ? The CAS is unable to proxy to the MBX server right ?

Thank you for your help!

Wish you a nice day !

We have a smaller pipe that replicates to remote sites.

Is there a maximum number for Copy Queue before database start to go into failed state?   

In one of our 2 servers in a DAG, we keep getting the warning message:

Event 22004 ShadowRedundancy:
The periodic heartbeat to primary server server.domain.local failed.

However everything seems to work just fine (incl. failover). I haven't found any other logs that indicate problems.
Can some one please point me in the right direction what the issue could be or if it's a known bug?

I have a two-node DAG with FSW that is configured for co-existence with a single Exchange 2007 Server that has mailbox, hub, and CAS roles installed.  Each Exchange 2013 mailbox server has the CAS role installed. The Exchange 2013 servers are in the same AD site but on different subnets.

When both mailbox servers are up and running I can log into the EAC on either server and administer the environment.  If I shut down either DAG member and try to log into the EAC on the remaining node, I am presented with the EAC logon screen and asked for credentials.  When I enter my credentials and press enter it just seems to hang forever at a blank screen.

If I open the Exchange Management Shell on the remaining member and do a get-DatabaseAvailabilityGroup -Status | Fl I can see the DAG is up and the mailbox database is mounted.

I haven't had time to test connectivity to mailboxes with Outlook or via OWA but I plan to do that.

Any suggestions would be very much appreciated.

Jerome

Hello,

I have configured WNLB between 2 exchange 2013 client rule servers. LB is working for all needed rules except of remote connectivity to Exchange Management shell. When typing real server name instead of LB VIP, everything is working properly. WNLB has only DNS record. No AD account and Kerberos configured.

here is the command and error:

[PS] C:\Windows\system32>New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUrihttp://vipname.domainname/PowerShell/

New-PSSession : [vipname.domainname] Connecting to remote server vipname.domainname failed with the following error
message : WinRM cannot process the request. The following error occurred while using Kerberos authentication: Cannot
find the computer usmail.comverse.com. Verify that the computer exists on the network and that the name provided is
spelled correctly. For more information, see the about_Remote_Troubleshooting Help topic.
At line:1 char:1
+ New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://vipname.domainname ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OpenError: (System.Manageme....RemoteRunspace:RemoteRunspace) [New-PSSession], PSRemotin
   gTransportException
    + FullyQualifiedErrorId : NetworkPathNotFound,PSSessionOpenFailed

Dear all,

I have a question

Let's say I have two servers in DAG environment and all databases are collected on both servers if something happens with the 1st server and it's no longer available I understand that the 2nd one will be responsible for sending/receiving e-mails

How it will affect on clients Outlook? Do they need to restart Outlook or it will be connected automatically?

Thank you in advance

Hello,

I am wondering if it is ok to do a vmotion of an active Exchange 2013 host.  Just the the guest from one esxi server host to another esxi server host, not the storage.  Or do I need to shut down the guest first and then move it and bring it back up.

I found documentation but it talks about DAGs,

Esxi 5.1

Exchange 2013 on Win 2012 standard

Thanks!!

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 

Just recently we had an incident in which a couple of switches were rebooted unintentionally which caused a backup process (Veeam) that utilizes VM snapshots (on VMware) to go haywire. I thought that it was just the backup process that was corrupted but then suddenly, I started getting errors every 5 minutes after the last snapshot was removed that primarily log event ID 233 but also 234, 228, and 530. Below are what they state:

228: At '5/15/2015 11:42:26 AM', the copy of database 'DB' on this server encountered an error that couldn't be automatically repaired without running as a passive copy and failover was attempted. The error returned was "There is only one copy of this mailbox database (DB). Automatic recovery is not available.". For more information about the failure, consult the Event log on the server for "ExchangeStoreDb" events.

233: At '5/15/2015 11:46:03 AM', database copy 'DB' on this server encountered an error. For more information, consult the Event log for "ExchangeStoreDb" or "MSExchangeRepl" events.

234: At '5/15/2015 11:42:26 AM', the copy of database 'DB' on this server encountered a serious I/O error that may have affected all copies of the database. For information about the failure, consult the Event log on the server for "ExchangeStoreDb" or "MSExchangeRepl" events. All data should be immediately moved out of this database into a new database.

530: Information Store (3468) DB: The database page read from the file "F:\DB\Database\DB.edb" at offset 238081900544 (0x000000376ec98000) (database page 7265682 (0x6EDD92)) for 32768 (0x00008000) bytes failed verification due to a lost flush detection timestamp mismatch. The read operation will fail with error -1119 (0xfffffba1).  If this condition persists, restore the database from a previous backup.  This problem is likely due to faulty hardware. Please contact your hardware vendor for further assistance diagnosing the problem.

So I figured, well, I can just create a new database and migrate the mailboxes over but many of them fail to migrate. For those mailboxes, I've tried to run the PowerShell command to repair them (New-MailboxRepairRequest) but that fails too with the following error:

10049: Online integrity check for request 0ab17d2b-bd15-4161-b4df-0dfcfd16c4d6 failed with error -1119.

The export to PST file fails as well and users report that archiving through Outlook fails once it reaches a corrupted folder.

I thought this was only happening for one of the databases so we figured we'd migrate as many as we could to a new drive and then announce data loss for the rest. Right now, we're copying the last good backup of the edb and the log files to the drive to mount in the old one's place in hopes that we can get away from the errors. Unfortunately, due to drive constraints, we were forced to enable circular logging on this database but we're okay with the one-two days of data loss for that particular database. The disturbing part is that once we dismounted the corrupted database, we started receiving the same errors for two other databases... Fortunately, at least those aren't nearly as big and they do not have circular logging enabled so we might be able to do a full restore assuming that the log files are not corrupted. However, I am worried that there is a bigger problem such as drive failure.

I am wondering if anyone can offer some advice for this scenario and I wanted to make sure that I am going down the right path of simply running restore process for each DB that gets this error until we can move everything to new storage. I am on Exchange 2010 SP1 and we have been working hard over the last few months to get our environment ready for 2013 (we purchased new storage for that deployment). Sorry for the lengthy post and please let me know if you need any further info for me.

Thank you in advance for your time!