Exchange Archives - Page 4 of 4

04May 2011 by Ceyhun Kirmizitas 0 Comments

Exchange 2010 EWS Proxy Event ID 16: No Applicable Client Access Servers

Applies to: Exchange Server 2010 Historical: This article covers the Exchange Server 2010 Client Access Server (CAS) proxy architecture. Exchange 2013 and later use a different Client Access / proxy model, so this specific troubleshooting flow should not be applied to current Exchange Server releases. In a multi-site Exchange 2010 environment, an Internet-facing Client Access Server could proxy Exchange Web Services (EWS) requests to a Client Access Server in the Active Directory site that hosted the mailbox. If Exchange could not identify a suitable Client Access Server in the destination site, the Application log could contain MSExchange Web Services Event ID 16 with a message similar to: Client Access server failed to proxy Exchange Web Services to Active Directory site because there are no applicable Client Access servers in the…

14Oct 2010 by Ceyhun Kirmizitas 0 Comments

How to Block Automatic Database Activation on an Exchange DAG Member

Exchange, Exchange Server SE / 2019 / 2016, High Availability

Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 In an Exchange Database Availability Group (DAG), you can prevent a Mailbox server from being selected for automatic database activation. This is useful when a DAG member should keep passive database copies but should not automatically host an active copy after a failure. The original version of this article described this as “manual failover.” A more accurate description is blocking automatic database activation on a DAG member. In This Article 1. Block Automatic Database Activation 2. What Blocked Does and Does Not Do 3. Allow Automatic Activation Again 4. Maintenance Mode Is Different 5. Key Takeaways 1. Block Automatic Database Activation To prevent database copies on a specific DAG member from being automatically activated, set the server-level…

09Sep 2010 by Ceyhun Kirmizitas 0 Comments

How to Install Exchange Server Updates on DAG Members

Exchange, Exchange Server SE / 2019 / 2016, High Availability, Migration & Upgrade

Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 Exchange Server updates on a Database Availability Group (DAG) should be installed one member at a time. The main goal is to move active databases away from the server, prevent them from activating back during maintenance, install the update, and then return the server to production. The original version of this article was written for Exchange 2010 SP1 and used the term Update Rollup. Current Exchange Server servicing uses Cumulative Updates (CU), Security Updates (SU), and when required Hotfix Updates (HU). The DAG maintenance principle is still the same. In This Article 1. Before You Start 2. Put the DAG Member in Maintenance Mode 3. Install the Exchange Update 4. Return the Server to Production 5. Update…

07May 2009 by Ceyhun Kirmizitas 0 Comments

Fix “No Site Name Is Available for This Machine” on Exchange Server

Active Directory, Exchange, Exchange Server SE / 2019 / 2016, Identity

Applies to: Exchange Server SE / 2019 / 2016 / 2013 / 2010 | Active Directory Domain Services When the Microsoft Exchange POP3 service cannot determine the Active Directory site for the server, it can fail with the following error: No site name is available for this machine. This is Windows error ERROR_NO_SITENAME (1919 / 0x77F). In most cases, the Exchange server IP subnet is missing from Active Directory Sites and Services or is mapped to the wrong AD site. In This Article 1. Check the Detected AD Site 2. Verify the Subnet in Active Directory Sites and Services 3. Correct the Subnet-to-Site Mapping 4. Validate the Fix 5. About the SiteName Registry Value 6. Key Takeaways 1. Check the Detected AD Site Run nltest /dsgetsite on the Exchange server.…

22Oct 2007 by Ceyhun Kirmizitas 0 Comments

How to Configure Local Continuous Replication (LCR) in Exchange Server 2007

Archive / Legacy Topics, Exchange, High Availability

Applies to: Exchange Server 2007 Historical: Local Continuous Replication (LCR) was an Exchange Server 2007 high-availability feature. It was removed in Exchange Server 2010 and replaced by the Database Availability Group (DAG) and mailbox database copy model. LCR creates a second copy of an Exchange 2007 storage group on the same Mailbox server. Transaction logs are copied and replayed into the replica database, providing a local recovery copy if the active database or storage fails. In This Article 1. What LCR Does 2. Configure Local Continuous Replication 3. Important Storage Considerations 4. What Replaced LCR 5. Key Takeaways 1. What LCR Does LCR is a single-server replication technology. It is enabled per storage group and uses Exchange log shipping to maintain a passive local copy of the databases in that…

Category: Exchange