13.0 CX Messages

The following messages include messages from the CX.EXE.

CX-X-120: Control characters are not allowed in the command line.

Source: CX.EXE
Explanation: Control character input is not allowed as a CX parameter. The key stroke sequences <Ctrl>+<C> and <Ctrl>+<Break> will abort the CX command.
Action: Retry the command without using control characters in parameters.

CX-X-215: The context you are trying to change to is invalid. Your current context will be left unchanged.

Source: CX.EXE
Explanation: After getting a context handle, CX encountered an error when it tried to set the desired context. CX has terminated.
Action: Make sure that you are using a valid context; then try again.

CX-X-220: An error occurred during CX’s attempt to create the context.

Source: CX.EXE
Explanation: CX could not create a context handle. CX has terminated.
Possible Cause: The library call NWCreateContext () failed because of insufficient memory at the server.
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide, then try again. If the problem persists, contact a Novell® support provider.

CX-X-230: An error occurred during CX’s attempt to get the object name.

Source: CX.EXE
Explanation: CX could not get general information about a directory object. CX has terminated.
Action: Try again. Make sure to specify a valid object. If the problem persists, contact a Novell support provider.

CX-X-240: The context you want to change to does not exist. You tried to change to: name. Your context will be left unchanged as: name.

Source: CX.EXE
Explanation: The context that was specified must exist in the eDirectory™ database before a user can use it. The context did not exist, so CX has terminated.
Action: Make sure to specify a valid context.

CX-X-242: The specified context does not exist.

Source: CX.EXE
Explanation: The context that was specified must exist in the eDirectory database before a user can use it. The context did not exist, so CX has terminated.
Action: Make sure to specify a valid context.

CX-X-244: The current context is invalid: context name.

Source: CX.EXE
Explanation: eDirectory allows the user to set a default context in the NET.CFG file (NAME CONTEXT=).
Possible Cause: The context specified during login did not match the context specified in NET.CFG.
Action: Specify a valid context by typing CX /R, or by typing CX... with the number of periods needed to remove all containers in the current context.
Possible Cause: The context was once valid, but it has since been removed from the Directory tree.
Action: Determine whether the context is still in the Directory tree and if it is valid by typing CX /T at the DOS prompt.

For example, if CX showed the user’s context to be ou=test.o=abc, then you would type CX..., which removes all containers and leaves you at the root.

CX-X-246: An error occurred in CX’s attempt to list the subordinate objects. Error code: code.

Source: CX.EXE
Action: Try the operation again. Also, make sure that no associated problems have occurred such as the network going down, a connection being lost, or previous errors having occurred and been ignored. If the problem persists, contact a Novell support provider. For information about a specific error code, search the Error Codes online documentation.

CX-X-260: An internal system error occurred during CX’s attempt to canonicalize the context: (context name).

Source: CX.EXE
Possible Cause: CX attempted to change the context of a given object, but it was unable to find the object in the given context, or it was unable to create the path in the Directory tree.
Possible Cause: This error can also occur if an error has occurred in the program. CX has terminated.
Action: Try again. If the problem persists, contact a Novell support provider.

CX-X-300: An error occurred during CX’s attempt to get the VLM shell context.

Source: CX.EXE
Explanation: The VLM shell contains the workstation’s default context designation. CX could not get this context and has terminated.
Action: Make sure the user has a valid context designated in the NET.CFG file at the workstation.

CX-X-810: This utility cannot allocate sufficient memory for the Directory Services buffer.

Source: CX.EXE
Action: Increase the memory available to the server. See Freeing Server Memory Temporarily in the NW 6.5 SP8: Server Operating SystemAdministration Guide.

CX-X-826: The VLMs are not loaded.

Source: CX.EXE
Explanation: The user tried to run CX from a client workstation using a NetWare® shell file (for example NETX.EXE). CX requires the client workstation to be using Virtual Loadable Module™ (VLM™) programs.
Action: Unload the NetWare shell file from the workstation and run VLM.EXE. Then retry CX.

CX-X-900: An internal application error has occurred. Error code: code

Source: CX.EXE
Action: Resolve the error, then try the task again. For information about a specific error code, search the the Error Codes online documentation.

CX-X-903: The command line syntax is invalid.

Source: CX.EXE
Action: See message 903: The command line syntax is invalid..

CX-X-906: The Unicode files cannot be found.

Source: CX.EXE
Action: See message 906: The Unicode files cannot be found..

CX-X-917: This utility was unable to set the context.

Source: CX.EXE
Action: See message 917: This utility was unable to set the context..

CX-X-920: This utility was unable to allocate number bytes of memory.

Source: CX.EXE
Action: See message 920: This utility was unable to allocate number bytes of memory..

CX-X-970: The attempt to open the Unicode table files failed.

Source: CX.EXE
Action: See message 970: The attempt to open the Unicode table files failed..

CX-X-971: The workstation does not have enough memory to load the Unicode* table files.

Source: CX.EXE
Action: See message 971: The workstation does not have enough memory to load the Unicode table files..

CX-X-972: Access to the Unicode table files was denied.

Source: CX.EXE
Action: See message 972: Access to the Unicode table files was denied..

CX-X-973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number

Source: CX.EXE
Action: See message 973: The Unicode table files cannot be found in the NLS directory or in the search path. Code page: number Country: number ..

CX-X-974: The Unicode table files are corrupt.

Source: CX.EXE
Action: See message 974: The Unicode table files are corrupt..

CX-X-975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file.

Source: CX.EXE
Action: See message 975: The Unicode table files cannot be opened because there are already too many open files. Close some files or modify your CONFIG.SYS file..

CX-X-998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance.

Source: CX.EXE
Action: See message 998: The message file found (utility_name.MSG) is an incorrect version. The correct version is number. See your network supervisor for assistance..

CX-X-999: The message file for this utility cannot be found.

Source: CX.EXE
Action: See message 999: The message file for this utility cannot be found..