Both clients and servers may log errors in the system. Servers running in the background usually do not display messages on the screen in the case of an incident. Therefore, if you encounter a problem, it is important to check the log.
The log displays the Error Codes and a short explanation.
On Windows, D3 errors are logged in the Windows Event Log. Use the Event Viewer, Application log. For the FSI, there is a configuration setting that enables or disables the logging of Interpret As Command (IAC) event messages. See D3 Connects for more information on the Log IAC Event Messages option.
All errors, incidents, and information messages are encoded in a string composed of various numeric fields. Normally, the string is translated into a readable form in a language selected by the current user locale, and both forms are stored in the error log.
It is important to understand the internal format for error codes because, in some extreme cases, the system will not be able to convert an error code into a readable form.
Exception classes
Errors or incidents are grouped in classes of errors, and each class is divided into exceptions. The exception code is a unique decimal number, starting at 1025.
| Class | Description |
|---|---|
| D3_RPC | Remote Procedure Call Exceptions. Exceptions of this class indicate network, Name Service or Windows Service Control Manager errors. |
| D3_FSI | File System Interface Errors. |
| D3_ VME | Virtual Machine Environment errors. These include the class Pick virtual errors. |
Error codes are listed in the Messages file in the DM database. The item-IDs are formatted by prefixing the left-justified decimal exception code with the string NE (for example, NE2320).