Outlook 2010 shows the same display name for different archives

There is an archive name issue with Outlook 2010 where the delegate archive shows the name of the primary mailbox owner:

Solution:

Exchange 2010 SP3 UR2 + Outlook 2010 SP1 or SP2 with Outlook 2010 hotfix package august 2013 (http://support.microsoft.com/kb/2817574/en-us) is required to solve the archive name issue:

1.       Install Outlook 2010 hotfix package

2.       Start Outlook 2010

3.       Outlook 2010 Autodiscover updates Outlook configuration but Outlook still shows the same display name for different archives

4.       Restart Outlook 2010 client

5.       Outlook 2010 shows correct archive names:

Note: this is also an issue with Outlook 2010 and Exchange 2013 CU2 with the same solution. I have not yet been able to test this with Outlook 2013 and Exchange 2013.

Martijn

 

Exchange 2013 CU2 Error: Windows Failover Clustering isn't installed

I installed two Mailbox Servers and created a DAG. No problems adding first server to DAG.

 

However, got an error while adding second server to DAG:

 

A server-side database availability group administrative operation failed. Error The operation failed. CreateCluster errors may result from incorrectly configured static addresses. Error: Windows Failover Clustering isn't installed on 'ex2013-server'

I got this error from both EAC and EMS. Actually, Windows Failover Clustering should be automatically installed when adding a DAG member.

Solution:

1. Windows PowerShell: install-windowsfeature failover-clustering
2. Add second DAG member again

Microsoft Exchange Health Manager service does not start automatically

I installed two new Exchange 2013 servers (1x CAS & 1x MBX) with latest CU2 (build 15.0.712.24).

Issue: Microsoft Exchange Health Manager service does not start automatically after reboot.

Event Viewer System log:

Event ID:      7000
Level:         Error
Description:
The Microsoft Exchange Health Manager service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Event ID:      7009
Level:         Error
Description:
A timeout was reached (30000 milliseconds) while waiting for the Microsoft Exchange Health Manager service to connect.

No problem manually starting Microsoft Exchange Health Manager service. When you set the service to ‘Automatic (Delayed Start)’ it starts fine after each reboot.

I've posted comments at http://blogs.technet.com/b/exchange/archive/2013/07/29/now-available-updated-release-of-exchange-2013-rtm-cu2.aspx

http://howexchangeworks.com/2013/08/exchange-health-manager-service-wont-start-automatically-after-installing-2013-cu2-v2.html#comment-3391 describes that recreating Health mailboxes may solve this problem. Recreating the Health mailboxes doesn’t fix the problem. Service has not been started after reboot. However, after some time (10-15 minutes) the service starts automatically.

So, this still seems to be an issue because the Exchange Health Manager service has not been started automatically after a reboot (only after 10-15 minutes).

Exchange 2013 Management Shell: The WinRM client cannot process the request because the server name cannot be resolved

After installing Exchange 2013 CU2 on a server it was not possible to start Exchange 2013 Management Shell.

Cause: someone configured a proxy with no exceptions

netsh winhttp show proxy:

Proxy Server(s): proxy.contoso.local:8080
Bypass List: (none)

 

Solution:

netsh winhttp set proxy proxy-server="http=proxy.contoso.local:8080" bypass-list="*.contoso.local,<local>"

Note: Use "<local>" to bypass all short name hosts.

 

Exchange 2010 Database Copy Failed with high Copy Queue Length and no log files

I recently noticed the following after creating an Exchange 2010 (SP2) Database Copy (Exchange DAG across two datacenters and two AD Sites):

·         DB Copy Status: Failed. Error: The required log file <nr> for <DB> is missing on the active copy

·         High Copy Queue Length
·         DB Copy (.edb file) was created but no log files

Solution:

1.       Remove passive DB Copy
2.       Delete DB & log files from disk
3.       Force AD replication between AD Sites
4.       Dismount active database
5.       Delete all E0*.log files
6.       Mount database
7.       Create DB Copy

 

STOP: c00002e2 Directory Services could not start

After a hardware problem (storage) in my virtual lab environment my Windows 2008 R2 Domain Controller VM did not start. When booting the VM I got a BSOD with a STOP error:

STOP: c00002e2 Directory Services could not start because of the following error: a device attached to the system is not functioning.

Error status: 0xc0000001.

Please shutdown this system and reboot into Directory Services Restore Mode, check the event log for more detailed information.

This was my only Domain Controller and no backup so I had to solve this problem.

Troubleshooting steps:

1.    Boot into Directory Services Restore Mode (F8)

2.    NTDSUTIL:

·         activate instance NTDS

·         files

·         Error: Could not initialize the Jet engine: Jet Error -501. Failed to open DIT for AD DS/LDS instance NTDS. Error -2147418113

·         quit

3.    ESENTUTL /g C:\Windows\NTDS\ntds.dit

·         ESENTUTL result: successful (no DB corruption)

4.    ESENTUTL /p C:\Windows\NTDS\ntds.dit

·         ESENTUTL result: successful (no DB corruption)

5.    Event log:

·         Error 1003: Active Directory Domain Services could not be initialized. The directory service cannot recover from this error. Restore the local directory service from backup media. Error value: -501 JET_errLogFileCorrupt, Log file is corrupt

·         Error 465: NTDS (2156) Corruption was detected during soft recovery in logfile C:\Windows\NTDS\edb.log. The failing checksum record is located at position END. Data not matching the log-file fill pattern first appeared in sector 6697 (0x00001A29). This logfile has been damaged and is unusable.

·         Error 454: NTDS (2256) Database recovery/restore failed with unexpected error -501.

6.    Rename edb.log to edb.log.old and restart system

·         Result: same STOP error

Solution to this problem: rename all *.log files in C:\Windows\NTDS folder and restart system.