Sign in
|
Join
|
Help
Search
ExchangeORG.net
Home
RSS
Atom
Comments RSS
Recent Posts
Ericsson authentication problem through ISA 2006
Microsoft Transporter Suite for Lotus Domino Build:08.01.0223
Bulk create mail contacts based on a CSV file
Exchange 2007 PowerShell Scrips
How to change Exchange system messages?
Tags
No tags have been created or used yet.
Navigation
Home
Blogs
Photos
Downloads
Blogs I Read
You Had Me At EHLO
Archives
October 2007 (1)
May 2007 (1)
April 2007 (1)
March 2006 (1)
April 2005 (1)
October 2004 (1)
June 2004 (1)
May 2004 (5)
Error Code Lookup Tool
Error Code Lookup tool can be used to translate errors reported by windows.
Here's a reprint of "Error Code Lookup Tool.doc" included in the Err package:
Error Code Lookup Readme
Determine error values from decimal and hexadecimal error codes in Microsoft Windows® operating systems. The tool can look up one or more values at a time.
Installation
From the Microsoft Web site, download the tool to a specified directory.
Using Error Code Lookup
Usage: err [value] [value]…
where must be of one of the following forms:
Decorated hex (0x54f)
Implicit hex (54f)
Ambiguous (1359)
Exact string (=ERROR_INTERNAL_ERROR)
Substring (:INTERNAL_ERROR)
All values on the command line will be looked up in Exchange’s internal tables and presented to you. If available, informational data associated with the value or values will also be shown (see example below). By default, the tool searches all tables, but you can restrict the output to those tables you deem appropriate by adding “/” to the beginning of the command line.
Example:
> err /winerror.h /ntstatus.h 0
# winerror.h selected.
# ntstatus.h selected.
# for hex 0x0 / decimal 0:
STATUS_WAIT_0 ntstatus.h
ERROR_SUCCESS winerror.h
# The operation completed successfully.
NO_ERROR winerror.h
SEC_E_OK winerror.h
S_OK winerror.h
# 5 matches found for “0”
Err.exe can bee downloaded from:
http://www.microsoft.com/downloads/details.aspx?FamilyId=BE596899-7BB8-4208-B7FC-09E02A13696C&displaylang=en
Posted:
May 11 2004, 03:45 AM
by
michael.lundgren
| with
no comments
Comments
No Comments