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.

Exchange 2010 SP2 UR4 mailbox move issue

Exchange 2010 SP2 UR4 mailbox move to another DB on the same server with newly created databases gives warning/error:

The Microsoft Exchange Mailbox Replication service completed request <mailbox> with warnings.
Warning: Failed to clean up the source mailbox after the move.
Error details: MapiExceptionUnexpectedMailboxState: Unable to delete mailbox. (hr=0x80004005, ec=2634)

The mailbox has been moved and can be accessed. I think this is a bug which MS should solve.

See also http://social.technet.microsoft.com/Forums/da-DK/exchange2010/thread/6043b74f-a41e-4674-b2b1-08c3b1a3afbd

Exchange 2010 SAN Certificate Mismatched Address

Obtained an Exchange 2010 SAN Certificate from a Windows 2008 R2 Enterprise Root CA in a test environment.

When accessing OWA with IE I got a warning:

Mismatched Address

The security certificate presented by this website was issued for a different website's address

Cause: the Common Name of the certificate should also be part of the Subject Alternative Name field.

SAN Cert example:

CN: webmail.contoso.com

Subject Alternative Name field:
webmail.contoso.com
autodiscover.contoso.com

Exchange Server 2013 Preview

Exchange Server 2013 Preview is available now!

Exchange 2010 SP2 OWA Dutch translation issue part 2

Update: MS released the newest version of the Exchange 2010 language pack on 5/22/2012 which solves the issues as described in this blog. See Exchange 2010 Service Pack 2 Language Pack Available for Download.


In a previous blog I wrote about an Exchange 2010 SP2 OWA Dutch translation issue.


This issue is described in The word "Globale Adreslijst" in Dutch is displayed unexpectedly in breadcrumb and navigation pane in OWA in an Exchange Server 2010 SP2 environment.

Solution: install Exchange 2010 SP2 Language Pack Bundle on Exchange 2010 CAS Servers.

Important:

• Exchange 2010 SP2 Language Pack Bundle is ONLY for people with the Dutch OWA problem. No one else should install it.
• This Language Pack Bundle is only intended for Exchange 2010 CAS role to solve the OWA Dutch translation issue. So, install this Language Pack Bundle only on Exchange 2010 CAS or Multi-Role Servers. Don't install this LPB on Exchange 2010 Mailbox or HUB Transport Servers.
• If you have already installed this Language Pack Bundle on Exchange 2010 Mailbox Servers or Multi-Role Servers it will probably generate errors in Application Log (Active Directory entry for mailbox <name> contains an invalid locale for attribute MsExchUserCulture: nl-NL,en-US). Microsoft is working on a fix for this. Summary, if you have:
• CAS Server: installing LPB and no error events
• CAS/HUB Server: installing LPB and no error events
• CAS/HUB/MBX Server: installing LPB and error events (MS will provide a fix)
• MBX Server: installing LPB and error events (MS will provide a fix)

Remarks:

• All Exchange services will be stopped and disabled during installation of Exchange 2010 SP2 Language Pack Bundle. For DAG members follow directions in Installing Update Rollups on Database Availability Group Members.
• Installation takes about 20-30 minutes per server.
• See also What's new with Exchange 2010 languages support?

Install Exchange 2010 SP2 Language Pack Bundle:

1.       Download Exchange 2010 SP2 Language Pack Bundle
2.       Run LanguagePackBundle.exe

What do we see: the wrong translation ‘Globale adreslijst’ has been replaced with ‘E-mail’.

However, this translation is different from the original translation. With Exchange 2010 RTM/SP1 the OWA Dutch interface shows ‘Berichten’ instead of ‘E-mail’. I’ve asked Microsoft about this and for some reason they chose ‘E-mail’ instead of ‘Berichten’ as the original translation.

Forefront Protection 2010 for Exchange Hotfix Rollup 4 and Kaspersky scan engine update errors

After installing FPE 2010 Hotfix Rollup 4 Kaspersky scan engine was not updating.
Event Viewer errors:

Event Type:        Error

Event Source:    GetEngineFiles
Event Category: Engine Error
Event ID:             6012
Description:
Microsoft Forefront Protection encountered an error while performing a scan engine update.
   Scan Engine: Kaspersky
   Error Code: 0x80004005
   Error Detail: Description: An error occurred while loading the scan engine.

Event Type:        Error

Event Source:    GetEngineFiles
Event Category: Engine Error
Event ID:             6019
Description:
Microsoft Forefront Protection encountered an error while performing a scan engine update.
   Scan Engine: Kaspersky
   Error Detail: An error occurred while testing the scan engine.
 
FPE Console:

Solution:

If running FPE on Windows 2003:

1.       Windows Explorer: turn on ‘Show hidden files and folders’

2.       C:\Documents and Settings\All Users\Application Data
            Rename ‘Kaspersky SDK’ (for example: rename Kaspersky SDK to Kaspersky SDK OLD)
3.       Update FPE engines

If running FPE on Windows 2008:

1.       Windows Explorer: turn on ‘Show hidden files, folders, and drives’
2.       C:\ProgramData\
           Rename ‘Kaspersky SDK’ (for example: rename Kaspersky SDK to Kaspersky SDK OLD)
3.       Update FPE engines