Installation guide

Dialogic
®
System Release 6.1 CompactPCI for Windows
®
Release Update 57
1.16 Troubleshooting Information for RTF Logs
To assist in troubleshooting, a table showing runtime and firmware errors that may appear
in Dialogic
®
Runtime Trace Facility (RTF) logs is now available. You can get a description
of errors and the suggested action to resolve the error. To access the table, use this link:
• Error Code Table
For runtime errors, the table provides the following information:
Internal error value
The error code detected internally by the library. In some of the libraries, more than
one internal error is mapped to an end user error. When contacting support about
failures, this information will be helpful to the support engineer because it provides
more specific information about why the error was generated. This number may
appear in the RTF log (with the end user error value).
Note: Sometimes the internal error value and end user error value are listed in the
same trace entry. Sometimes the internal error value may appear as a
separate entry.
End user error
The name of the constant that is documented in the library API reference.
End user error value
The numeric value of the constant that is documented in the library API reference.
This is the value that will appear in the RTF log, which you can then search for in the
table.
Description of the error
A textual description of the error.
Action to be taken
The suggested action to resolve the error.
For firmware errors, the table provides the following information:
Resource
The firmware entity in which the error occurred. A resource is technically called a DM3
resource and is a software entity that provides a service to other DM3 resources. You
can use the resource information to better narrow down what activity was occurring
when the error occurred.
Loc hex
The value that will appear in the RTF log (for example, 0x80000C), which you can
then search for in the table.
Error class
A classification of the firmware error in broad categories. You can use this column to
understand the type of action to take for a particular type of error. For example, if an
error is classified as a memory error, action can be taken that is specific to this type of
error (such as a pool configuration change).