SCDPM 2010 Protecting Exchange Server 2003 SP2 – Selecting the correct ESEUTIL

We’ve recently commissioned a server running the new Microsoft System Center Data Protection Manager 2010 to provide continuous data protection for business critical servers, including Hyper-V hosts and their guests.

At the moment, there’s still an old 32-bit Windows Server 2003 SP2 server running Exchange Server 2003 SP2.

After reading the documentation on Technet I determined that we needed a copy of the 32-bit ESEUTIL from Exchange 2003 on the SCDPM server.

Specifically, it says:

The eseutil.exe and ese.dll versions that are installed on the most recent release of Exchange Server must be the same versions that are installed on the DPM server. In addition, you must update eseutil.exe and ese.dll on the DPM server if they are updated on a computer running Exchange Server after applying an upgrade or an update.

The versions of the Exchange Server Database Utilities (eseutil.exe) and ese.dll that are installed on the computer running the most recent edition of Exchange Server must be the same versions that are installed on the DPM server.

You use the Microsoft Exchange Server 2007 management tools to maintain up-to-date copies of eseutil.exe and ese.dll. Exchange Server 2007 is a native 64-bit application that includes 64-bit management tools. You can use the management tools to remotely administer your Exchange Server environment. If the remote computer is running a 32-bit operating system, you must download the Microsoft Exchange Server 2007 32-bit management tools (http://go.microsoft.com/fwlink/?LinkId=112325). The management tools are supported by all update methods such as Microsoft Update and Microsoft Systems Management Server (SMS).

From this I inferred that

  • The computer running the most recent version of Exchange is running 2003 SP2, so that’s the correct version of ESEUTIL.EXE and ESE.DLL to use.
  • The 32-bit versions are the correct ones.

I can categorically state now that the docs are wrong – if the DPM server is x64 (and DPM2010 is only x64), then the ESEUTIL.EXE and ESE.DLL must also be x64.

Anyway, this is what the symptoms look like…

The problem is with the First Storage Group in Exchange. This is the error in DPM2010 administrator console:

Affected area:  First Storage Group

Occurred since: 20/05/2010 10:02:11

Description:    The replica of Storage group First Storage Group on tsp-svr-01.stokes.msi is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

     Data consistency verification check failed for LOGS of Storage group First Storage Group on tsp-svr-01.stokes.msi. (ID 30146 Details: Unknown error (0xfffffc01) (0xFFFFFC01))

     More information

Recommended action:  Either the database files are corrupt or the proper versions of the Eseutil.exe and Ese.dll files are missing.

If you have recently upgraded your Exchange server, copy them from that server to the DPM server.Contact your Exchange server administrator, and then verify the issue. You can recover the last known good backup to address the corrupted state.

     Synchronize with consistency check.

     Run a synchronization job with consistency check…

Resolution:     To dismiss the alert, click below

     Inactivate alert

I had copied the ESE.DLL and ESEUTIL.EXE 32-bit files directly from the protected Exchange server’s Exchsrvr\bin folder to C:\Program Files\Microsoft DPM\DPM\bin on the DPM2010 computer.

DPM was finding and starting the ESEUTIL, as the application event log shows the following:

Log Name:      Application
Source:        ESE
Date:          20/05/2010 10:01:51
Event ID:      100
Task Category: General
Level:         Information
Keywords:      Classic
User:          N/A
Computer:      TSP-DPM-01.whatever
Description:

eseutil (2576) The database engine 6.05.7638.0002 started.

Followed by numerous errors such as this:

Log Name:      Application
Source:        ESE
Date:          20/05/2010 10:01:51
Event ID:      489
Task Category: General
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      TSP-DPM-01.whatever
Description:

eseutil (2576) An attempt to open the file "C:\Windows\system32\Volume{167a68cd-62b8-11df-b24a-0026b98c66d4}\cf0d079c-a3b3-4eb7-885c-6e98e257b802\Logs\Logs\E001FEFF.log" for read only access failed with system error 3 (0x00000003): "The system cannot find the path specified. ".  The open file operation will fail with error -1023 (0xfffffc01).

Each error quotes a different exchange log file name, but in the same (non-existent) folder.

Looking at it more closely, I think reason that the 32-bit ESEUTIL.EXE failed is because DPM mounts the volume containing the log files in a folder inside the System32 directory, and on an x64 machine, 32-bit processes will have the SysWOW64 folder mapped as System32, so they won’t see the mounted volumes as they’re mounted in the real System32, not SysWOW64…

One more thing – Initially I had difficulty deleting the 32-bit copy of ESE.DLL from the DPM\Bin folder – it said the file was in use by DHCHP Client, and when I stopped that service it said the file was in use by Event Log. Both of these must have been untrue, as it’s a 32-bit DLL and won’t load into a 64-bit process, but I did notice that the DPM\Bin folder is appended to the system Path. I got around this by removing DPM\Bin from the Path, rebooting the DPM server, deleting the ESE.DLL and then re-adding DPM\Bin folder to the Path. That wasted an hour.

After the reboot & successful delete, I put the Exchange Server 2007 SP1 x64 ESEUTIL.EXE and ESE.DLL in a separate folder and created hard links to them in the DPM\Bin folder.

Next, we ran the  “Perform consistency check…” on First Storage Group and we now have a Green Tick – Yay!

Advertisements
This entry was posted in Uncategorized. Bookmark the permalink.

7 Responses to SCDPM 2010 Protecting Exchange Server 2003 SP2 – Selecting the correct ESEUTIL

  1. IT Juggler says:

    Thank you, thank you, thank you! I’ve been pulling my hair out–not that I have that much left–all day trying to find info on this. Your description fit my case exactly and so did your solution.

    I did not have any trouble deleting the 32-bit ese.dll and eseutil.exe files from dpm\bin. Also, I had an Exchange 2010 iso handy, so I copied the 64-bit versions from it and placved them directly in dpm\bin, rather than placing them elsewhere and creating hard links. I figured if Exch 07 would work then Exch 10 might too.

    Thanks again.

    • alasdaircs says:

      Yeah – basically, use the same bitness as the DPM (64-bit), and the lastest version you can get, but at all times ensure the version on DPM >= highest version on protected server.

  2. Scott Miller says:

    This article described the exact pronlem I was seeing and the solution was spot on. I was able to download the Exchange 2007 64bit installer and extract the eseutil.exe and ese.dll without having to install it. I placed those files on the DPM server and re-ran my backup job and presto, the backup finished without error. Thank you for posting this.

  3. happy user says:

    A great time saver, thanks for the info. Likewise I used exchange 2010 tools

  4. Excellent advice… My Storage group is Green, and I am happy!!

    Thanks again!

  5. JC says:

    Kick-ass troubleshooting man! Fixed it for me!
    Thank you!

  6. NorbyTheGeek says:

    Thanks for this. DPM 2012 has the same problem, and using the Exchange 2007 64-bit files extracted from the installer worked perfectly.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s