3.1 DirXML Error Code List

These are the DirXML Error Codes included in this section:

-286 FFFFFEE2 PREEMPT COMM

Source: DirXML
Explanation: This error is used internally on the NetWare® platform as a last resort to close the communications link between the DirXML engine’s native and Java code. This error is not normally returned.
Action: See Reporting Error Code Problems to Novell.

-287 FFFFFEE1 CLOSE COMM

Source: DirXML
Explanation: This error is used internally on the NetWare platform to close the communications link between the DirXML engine’s native and Java code. This error is not normally returned.
Action: See Reporting Error Code Problems to Novell.

-288 FFFFFEE0 OPEN COMM

Source: DirXML
Explanation: This error is returned on the NetWare platform if the communications link between the DirXML engine’s native and Java code cannot be established.
Action: See Reporting Error Code Problems to Novell.

-289 FFFFFEDF ALREADY EXISTS

Source: DirXML
Explanation: This error is used internally on the Win32 platform to indicate that a synchronization semaphore in the engine has already been created. This error is not normally returned.
Action: See Reporting Error Code Problems to Novell.

-290 FFFFFEDE INVALID COUNT

Source: DirXML
Explanation: This error is used internally on all platforms to indicate a request to create a synchronization semaphore with a maximum count value greater than 1. This error is not normally returned.
Action: See Reporting Error Code Problems to Novell.

-291 FFFFFEDD TIMEOUT

Source: DirXML
Explanation: This error is used internally to indicate that a Timed Wait semaphore was not obtained within the timeout period. This error is not normally returned.
Action: See Reporting Error Code Problems to Novell.

-292 FFFFFEDC FATAL

Source: DirXML
Explanation: This error is returned if the DirXML interface cannot be initialized, or if an unhandled exception is encountered.
Action: See Reporting Error Code Problems to Novell.

-293 FFFFFEDB MEMORY ERR

Source: DirXML
Explanation: This error is returned if a memory allocation request fails.
Action: See Reporting Error Code Problems to Novell.

-294 FFFFFEDA VRDRIVER INTERFACE MISMATCH

Source: DirXML
Explanation: This error is returned during driver initialization if the DirXML engine’s Java component does not support the required interfaces.
Action: See Reporting Error Code Problems to Novell.

-295 FFFFFED9 VRDRIVER CREATE FAIL

Source: DirXML
Explanation: This error is returned during initialization if the VRDriver class does not support the “init” method.
Action: See Reporting Error Code Problems to Novell.

-296 FFFFFED8 VRDRIVER MISSING

Source: DirXML
Explanation: This error is returned during initialization if the VRDriver class cannot be found.
Action: See Reporting Error Code Problems to Novell.

-297 FFFFFED7 JVM CREATE FAIL

Source: DirXML
Explanation: This error indicates that either a System, Timeout, or Create error occurred during initialization of the Java Virtual Machine (JVM).
Action: See Reporting Error Code Problems to Novell.

-298 FFFFFED6 JVM INIT FAIL

Source: DirXML
Explanation: This error indicates that the JVM could not be initialized after loading.
Action: See Reporting Error Code Problems to Novell.

-299 FFFFFED5 JRE LOAD FAIL

Source: DirXML
Explanation: This error indicates that the loading of the JVM by the DirXML engine failed.
Action: See Reporting Error Code Problems to Novell.

-300 FFFFFED4 NO JRE

Source: DirXML
Explanation: This error is not used.
Action: See Reporting Error Code Problems to Novell.