Article ID: 316279 - View products that this article applies to.
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:
(http://support.microsoft.com/kb/256986/EN-US/ )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 ConverterTo use Error Converter to convert an 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]
Collapse this tableExpand this table
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:
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]]
Collapse this tableExpand this table
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:
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:
Using Information Store ViewerTo use Information Store Viewer to view a message store:
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:
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 0x3001001eThe following output is displayed:
Property tag 0x3001001e = PR_DISPLAY_NAME PROP_TYPE 0x1e = PT_STRING8
Additional InformationFor 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:
(http://support.microsoft.com/kb/272603/EN-US/ )XGEN: List of Tools Included with the Exchange 2000 Server Resource Kit