Eric pointed out at tool on the Microsoft download site that helps identify errors:


Download details: Exchange Server Error Code Look-up Tool:
http://www.microsoft.com/downloads/details.aspx?FamilyId=BE596899-7BB8-4208-B7FC-09E02A13696C&displaylang=en


USAGE: err {value} [value] [value] …
 where must be of one of the following forms:
   1. decorated hex (0x54f)
   2. implicit hex  (54f)
   3. ambiguous     (1359)
   4. exact string  (=ERROR_INTERNAL_ERROR)
   5. substring     (:INTERNAL_ERROR)


All values on the command line will be looked up in our internal
tables and presented to you.  If available, informational data
associated with the value(s) will also be shown (see below).
All tables are searched by default, but you can restrict the
output to those tables you deem appropriate by adding
“/” to the beginning of the commandline.


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”


  Last compiled on Mar 31 2003 14:39:19.
Interesting….


when putting in the code on this tool I get:



<click here for the larger view>


Not quite as good as GUItroubleshooting as Eventid.net, Eric, but definintely a keeper  🙂

 

Comments are closed.