You are currently offline, waiting for your internet to reconnect

XGEN: Tools That Are Included with the Exchange 2000 Server CD-ROM

This article was previously published under Q316279
This article has been archived. It is offered "as is" and will no longer be updated.
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
This article contains information about the support tools on the Exchange 2000 Server CD-ROM. Some of these tools are intended for use only under the direction of Microsoft Product Support Services (PSS). The tools that are described in this article are located in the Support\Utils folder under the subfolder for your platform.


Error Converter (Error.exe)

The Error Converter tool (Error.exe) is a file that converts most information store, Messaging Application Programming Interface (MAPI), directory, and database error codes to error message strings. For example, the error string for the error code 0x8004010f is MAPI_E_NOT_FOUND. This tool is most useful when you are troubleshooting problems with Microsoft Product Support Services (PSS). If you use this tool, you should have knowledge of Messaging Application Programming Interface (MAPI). This tool does not require Exchange 2000 Server to run.

Using Error Converter

To use Error Converter to convert an error code:
  1. At the command prompt, switch to the Support\Utils\platform folder on the Exchange 2000 Server CD-ROM.
  2. Type the following command (where error_code is the decimal or hexadecimal error code):
    error error_code
Error Converter displays the error string for the specified error code.

You must begin hexadecimal error codes with 0x or the error code is interpreted as a decimal error code.

Esefile (Esefile.exe)

The Esefile tool is a database file utility that can calculate a checksum for .edb files and copy files (greater than 192 gigabyte [GB]).

The Esefile tool usage syntax is:
esefile [/C source destination] [/X file] [/S file] [/D file pgno]
/CCopies source to destination
/SEse.dll format checksum
/XEdb.dll format checksum
/DDump a page from a file

The Mailbox Merge Program (Exmerge.exe)

An Exchange administrator can use the Exchange Mailbox Merge program (ExMerge.exe) to extract data from mailboxes on an Exchange computer, and then merge that data into mailboxes on another Exchange computer.

This program copies data from the source server to personal folder files (.pst files), and then merges the data in the personal folders into mailboxes on the destination server.

Because of this program's ability to merge data to and from an Exchange computer, this program is a valuable tool with a variety of uses, especially during disaster recovery. This program can also replace existing data instead of merging new data, if the administrator specifies that it do so.

This program requires that the following files be installed on the local computer:
  • Exmerge.exe
  • Exmerge.ini
  • Dapi.dll
  • Emsabp32.dll
  • Emsmdb32.dll
  • Emsui32.dll
  • Emsuix32.dll
  • Exchmem.dll
  • Libxds.dll
  • Mapi32.dll

The File Version Utility (Filever.exe)

This command-line utility examines the version resource structure of a file or a folder of files on either a local or remote computer and displays information on the versions of executable files, such as .exe files and dynamic-link libraries (DLLs).

You can use the File Version utility to determine the exact binary build of an installed component. Typically, the file date and time of executable files are modified to make the files easy to identify as part of a major release; however, fixes and service packs do not always follow this convention.

You can track the origin of a fix by identifying the actual version information, which might be useful if support personnel requested that you identify fixes that are installed on your computers.

NOTE: The File Version utility might not work against localized binaries.

The File Version utility usage syntax is:
filever [/s] [/v] [/e] [/x] [/b] [/a] [/d] [[drive:][path][filename]]
/sDisplays files in the specified folder and all of the subfolders
/vLists verbose version information if it is available
/eLists executable files only
/xDisplays the short names that are generated for non-8.3 file names
/bUses bare format (no dir listing)
/aSpecifies that file attributes not be displayed
/dSpecifies that file date and time not be displayed

GUID Generator (Guidgen.exe)

You can use the GUID Generator component to generate globally unique identifiers (GUIDs) that you can use to identify your Microsoft ActiveX classes, objects, and interfaces. The GUID is copied to the Clipboard in one of four different formats for insertion into your application's source code.

The GUID Generator component calls the CoCreateGuid application programming interface (API) function to generate a new GUID so that you can copy it to the Clipboard in one of four formats:
  • Defined in an IMPLEMENT_OLECREATE macro, which allows instances of a CCmdTarget-derived class to be created by automation clients, for example:
    // {CA761230-ED42-11CE-BACD-00AA0057B223}IMPLEMENT_OLECREATE(<<class>>, <<external_name>>, 0xca761230, 0xed42, 0x11ce, 0xba, 0xcd, 0x0, 0xaa, 0x0, 0x57, 0xb2, 0x23);						
  • Defined using the DEFINE_GUID macro, which is commonly used in non-Microsoft Foundation Classes (MFC) programming, for example:
    // {CA761231-ED42-11CE-BACD-00AA0057B223}DEFINE_GUID(<<name>>, 0xca761231, 0xed42, 0x11ce, 0xba, 0xcd, 0x0, 0xaa, 0x0, 0x57, 0xb2, 0x23);						
  • Declared as a statically allocated structure, for example:
    // {CA761232-ED42-11CE-BACD-00AA0057B223}static const GUID <<name>> = { 0xca761232, 0xed42, 0x11ce, { 0xba, 0xcd, 0x0, 0xaa, 0x0, 0x57, 0xb2, 0x23 } };						
  • Specified in a form that is suitable for registry entries or registry editor scripts, for example:

The Mailbox Reconnect Tool (Mbconn.exe)

You can use the Mailbox Reconnect tool to connect users in Exchange 2000 to their orphaned mailboxes. This tool is especially helpful when you are replacing or adding an Exchange computer. For additional information, see the Mailbox Reconnect Help (Mbconn.chm).

Information Store Viewer (Mdbvue32.exe)

You can use Information Store Viewer (Mdbvue32.exe) to view or set details about a user's message storage files, which consist of the private information store, the personal folder file (.pst file), and the offline folder file (.ost file). Information Store Viewer shows the properties that are available for each message, how you can use the properties, and the format that the properties appear in. For example, you can use Information Store Viewer to determine why a message can be saved but not sent.

This tool requires the following files:
  • Propvu32.dll
  • Statvu32.dll
  • Tblvu32.dll
  • Xvport.dll
This tool is useful when you are troubleshooting issues with PSS. If you use this tool, you should have knowledge of MAPI.

Using Information Store Viewer

To use Information Store Viewer to view a message store:
  1. Run Mdbvu32.exe in the Support\Utils\platform folder on the Exchange 2000 Server CD-ROM.
  2. In the MAPILogonEx(MAPI_LOGON_UI) dialog box, click Mapi_New_Session, and then click OK.
  3. Click the user profile for the information stores that you want to view.
  4. On the MDB menu, click OpenMessageStore.
  5. In the Select Message Store dialog box, click the information store that you want to view, and then click Open. The profile can contain a public information store, a private information store, and personal folders.
  6. On the MDB menu, click either Open Root Folder or Open IPM Subtree.

    NOTE: The Open IPM Subtree command is not available for gateways.

The Exchange Trace Utility (Regtrace.exe)

Trace information about a computer that is running Exchange 2000 Server is very useful for troubleshooting purposes. This section provides a procedure to follow when you are attempting to trace information that is associated with the transport components of Exchange 2000.

To activate the tracing feature, on the server on which Exchange 2000 is installed:
  1. At a command prompt, type regtrace. The Trace Settings window is displayed.
  2. Click the Trace tab, and then make sure that all of the check boxes are selected.
  3. Click the Output tab, make sure that the File check box is selected, and then provide a path to a location that is large enough for the output file (the output file can be extremely large).
  4. Click the Threading tab, and then make sure that the Write traces on a background thread check box is not selected.
  5. Add the Modules registry value; to do so, you need to edit the registry.

    WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    To add the Modules registry value:
    1. Start Registry Editor (Regedt32.exe).
    2. Locate and click the following key in the registry:
    3. On the Edit menu, click Add Value, and then add the following registry value:
      Value name: Modules
      Data type: REG_MULTI_SZ
      Value data:
      The new entry appears in the registry as:
      Modules:REG_MULTI_SZ:SMTP AQ CAT EXSINK StoreDrv Routing RESVC
    4. Quit Registry Editor.
  6. Use the Component Services Microsoft Management Console (MMC) snap-in to stop the Microsoft Internet Information Services Administrator service. This requires that several dependent services be stopped.
  7. Start the Internet Information Services Administrator service again, and then start all of the dependent services that you stopped in step 6 again.
  8. Send messages through the Exchange 2000 system.
The trace file is available at the location that you specified on the Output tab of Trace Settings window in step 3. The default location for the file is C:\Trace.atf.

The Winroute Tool (Winroute.exe)

The Winroute tool connects to the link state port (TCP 691) on an Exchange 2000 server and extracts the link state information for an organization. The information is a series of GUIDs (connectors and bridgehead servers), which Winroute matches to objects in Active Directory, and then presents in version that you can read. The upper half of the window displays the interpreted data and the lower half of the window displays the raw information from the link state port.

MAPI Property Tag Identifier (Ptag.exe)

MAPI Property Tag Identifier translates a MAPI property tag ID to a property tag name and type. MAPI Property Tag Identifier is built with the store. For best results, use a current build of MAPI Property Tag Identifier.

You can use MAPI Property Tag Identifier to identify a MAPI property tag ID, which is very useful when you are debugging Exchange 2000 because the functions that process properties usually read properties in an array. Because of this, you might not know which property is being worked on. With MAPI Property Tag Identifier, when you see property tag IDs, you can determine which property is being processed.

To use MAPI Property Tag Identifier, at a command prompt, type:
D:\tools>ptag 0x3001001e
The following output is displayed:
Property tag 0x3001001e = PR_DISPLAY_NAME PROP_TYPE 0x1e = PT_STRING8

Additional Information

For additional information about the tools that are included in the Exchange 2000 Resource Kit, click the article number below to view the article in the Microsoft Knowledge Base:
272603 XGEN: List of Tools Included with the Exchange 2000 Server Resource Kit
smallbiz sbs IIS

Article ID: 316279 - Last Review: 02/28/2014 04:31:53 - Revision: 2.5

Microsoft Exchange 2000 Server Standard Edition, Microsoft Small Business Server 2000 Standard Edition

  • kbnosurvey kbarchive kbhowto KB316279