The command-line tool, CSError.exe, helps troubleshoot event log errors that do not display any descriptive text. The tool attempts to map the error code to a description of the error. When possible, it prints the cause of the error and recommends a resolution. You can download this tool and other Microsoft Lync Server 2010 Resource Kit tools from the Download Center.
Author: Sankaran Narayan
Publication date: December 2010
Product version: Microsoft Lync Server 2010
Microsoft Lync Server 2010 communications software reports information, warnings, and errors in the event log. These events can contain error codes (for example, 0x80070054). Lync Server 2010 log files also contain these error codes. The Error String Display tool (CSError.exe) helps map these error codes to an error message that administrators can read, and, when possible, provides a recommended resolution. You can download this tool and other Microsoft Lync Server 2010 Resource Kit tools from the Download Center.
The following are the command-line options for the tool:
- CSError.exe “errorcode”
- CSError.exe /? Displays Help
If the error code is successfully mapped, the tool outputs the error description and possible resolution. If the error code cannot be mapped, it reports an error. These two cases are described further in the examples later in this article.
CSError.exe helps troubleshoot Lync Server errors by mapping error codes to descriptive messages.
Install the Lync Server 2010 Resource Kit tools from here. CSError.exe runs on all Lync Server roles.
Example 1: CSError.exe 0x80070054
0x80070054 -> (System) Storage to process this request is not available.
Example 2: CSError.exe 0x1000000
0x81000000 -> None matched.
Example 3: cserror 0xC3E9381E
0xC3E9381E -> (SIPPROXY_E_TLS_INCOMING_BAD_CERTIFICATE)
CSError.exe helps troubleshoot event log errors by mapping error codes to their description and resolution.
Lync Server Resources
- Lync Server 2010 documentation in the TechNet Library
- NextHop blog
- Lync Server and Communications Server resources
We Want to Hear from You
Keywords: error code, log files, error message, CSError.exe, administrator, troubleshoot, event log