The following is Tip #18 from "25 Exchange 2003 Tips in 25 minutes." This content is excerpted from Scott Schnoll's...
book, "Microsoft Exchange Server 2003 Distilled," brought to you by © (2004) Pearson Education, Inc. Publishing as Addison-Wesley Professional. Return to the main page for more tips on this topic.
- Hexadecimal (e.g., 0x31c or 31c)
- Numeric (e.g., 1723)
- String (e.g., UNKNOWN_FAILURE or INTERNAL_ UNKNOWN_FAILURE)
Many of these same error messages can also be translated using the
NET HELPMSG command found in Windows, as well as the Visual C++ Error Lookup tool that ships with Visual Studio; however, you may still find ERR.EXE to be useful. For more information on using ERR.EXE, see the Read Me file included with this tool.
Get more "25 Exchange 2003 Tips in 25 minutes." Return to the main page.
About the author: Scott Schnoll, an Expert on SearchExchange.com, is an MCT, MCSA and a long-time Microsoft Most Valuable Professional (MVP).
In addition to writing "Microsoft Exchange Server 2003 Distilled," he is a co-author of the upcoming "Exchange 2003 Resource Kit from Microsoft Press" and lead author for "Exchange 2000 Server: The Complete Reference."
Scott has written numerous articles for Exchange & Outlook Magazine, and is a regular speaker at Microsoft conferences, including MEC and TechEd, as well as industry conferences such as Comdex and MCP TechMentor, where he covers topics such as Exchange, clustering, Internet Information Services and security.