Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Yesterday two new developers came into my office and wanted to know what some weird Win32 error code mapped to. I tried to get them to turn their heads as I looked it up because I didn't want them to know how easy this was.
I just used err.exe, which lets you specify a Win32 error on the command prompt and returns what the error code is. It's available at:
Unfortunately now no one will be impressed when I can tell them their hard to find error code is in the future :(.
[Author: John Spaith]
Comments
- Anonymous
July 29, 2005
I think you can do something similiar with:
net helpmsg <number> - Anonymous
July 29, 2005
From cmd.exe:
net helpmsg <errorcode> - Anonymous
August 01, 2005
How does it compare with 'net helpmsg'.
For example:
C:TemperrErr>net helpmsg 10035
A non-blocking socket operation could not be completed immediately.
Your suggestion:
C:TemperrErr>err 10035
# for decimal 10035 / hex 0x2733 :
SQL_10035_severity_16 sql_err
# No value was given for one or more of the required
# parameters.
WSAEWOULDBLOCK winerror.h
# A non-blocking socket operation could not be completed
# immediately.
WSAEWOULDBLOCK winsock2.h
# 3 matches found for "10035" - Anonymous
April 11, 2007
Thank you, it was useful, I was totally fed up with having to hunt for the error constant name. This saves me from using magic numbers even when I have to hurry with coding.