Oracle Network Products Troubleshooting Guide

Library

Product

Contents

Index

Network Manager Error Messages

NMC Error Messages (NMC-00001 to 11000)
NMO Error Messages (NMO-01001 to 01300)
NMR Error Messages (NMR-00001 to 00500)

This chapter includes the error messages for the Oracle Network Manager. It contains error messages from three files.

NMC messages are messages generated by the Oracle Network Manager that appear in response to user input to the tool. Only those messages that notify you of errors which require you to take actions that are not a logical continuation of your use of the tool are included in this chapter.

NMO messages are messages from the network object layer. These messages appear only when unusual errors at the underlying object layer occur.

NMR messages are messages from the object storage (ROS file) level of the Network Manager. Most of these are internal errors not normally visible to the user.

NMC Error Messages (NMC-00001 to 11000)

NMC-00005 Failed to save document

Cause: A File.Save or File.SaveAs failed. If more information is available, it will appear under this error.

Action: Make sure that the file exists and is both readable and writable by the application.
NMC-00010 Resource file cannot be opened

Cause: NetMan's resource file was not located or could not be opened.

Action: Consult the documentation for your platform to determine the proper location for this file, then be sure it has been installed there.
NMC-00011 Failed to initialize windowing system

Cause: Network Manager failed to initialize the windowing system.

Action: Make sure the Oracle Toolkit 2 product has been installed properly. If the error persists contact Worldwide Customer Support.
NMC-00012 The connection to the windowing system was refused

Cause: Network Manager failed to initialize the windowing system because it was refused a connection to it.

Action: Make sure your DISPLAY environment variable is set properly and that you have permission to run on the machine it points to.
NMC-00014 Unable to allocate memory

Cause: The application has run out of memory

Action: Add more memory or run fewer processes.
NMC-00015 Fatal error in property sheet; suggest you save immediately

Cause: Cause: An error was raised while processing a property sheet. If more information is available, it will appear under this error.

Action: Perform File.Save or File.SaveAs immediately, then exit the program.
NMC-00016 Unable to find prototype file file

Cause: Net Manager's prototype file was not located or could not be opened.

Action: Consult the documentation for your platform to determine the proper location for this file, then be sure it has been installed there.
NMC-00028 Resource file is invalid; version version is required

Cause: The resource file found was not the current version.

Action: Consult the documentation for your platform to determine the proper location for this file, then be sure the correct version has been installed there.
NMC-00031 Unable to locate online help file

Cause: The nmc help file was not found.

Action: Consult the documentation for your platform to determine the proper location for this file, then be sure the correct version has been installed there.
NMC-00032 Not enough memory to write to clipboard

Cause: On a Cut or Copy operation, there was insufficient memory.

Action: Add more memory or run fewer processes.
NMC-00033 Clipboard is empty

Cause: On a Paste, there was nothing on the clipboard.

Action: none
NMC-03750 Cannot export Oracle Names data

Cause: Export to Names has failed. This error is followed by detailed error information, if any.

Action: Restart Net Manager, after checking that the database schema is properly installed, and the database is online.
NMC-03751 ROS table tablename has not been installed

Cause: The application attempted to load a document and could not find a required system table inside that document. If the document is stored in a database, this error can also occur when the document database has not yet been installed.

Action: If the document is stored on a database, make sure the database schema has been properly installed, using the nmcbild.sql installation script.
NMC-03752 Illegal Region delegation configuration

Cause: The relationship among your regions is unacceptable.

Action: Contact Worldwide Customer Support for further information.
NMC-03901 Could not access directory directory_name

Cause: Directory could not be accessed. If more information is available, it will appear under this error.

Action: Make sure that directory exists and is writable.
NMC-03902 Error while writing file filename

Cause: Error while writing to the file. If more information is available, it will appear under this error.

Action: Make sure that the file can be created and written to in the appropriate export directory.
NMC-03903 Error while removing directory directory_name

Cause: A old export directory could not be removed. If more information is available, it will appear under this error.

Action: Make sure that directory exists and is removable.
NMC-03904 Error while creating directory directory_name

Cause: An export directory could not be created. If more information is available, it will appear under this error.

Action: Make sure that the directory is able to be created where specified.
NMC-03905 Error while spawning a new process

Cause: fork() failed while removing a previous export directory. If more information is available, it will appear under this error.

Action: Free memory to allow fork() to succeed. Alternatively, clear space for the export directory manually.
NMC-03906 Error while removing a directory

Cause: execl("/bin/rm",...) failed. If more information is available, it will appear under this error.

Action: Follow OS-dependent procedures to allow execl("/bin/rm",...) to succeed. Alternatively, clear space for the export directory manually.
NMC-03907 Node node_name not found

Cause: Node not found in exported network or not fully-qualified.

Action: Supply a correct and fully domain-qualified Node name.
NMC-03908 Client Profile profile not found

Cause: Client Profile not found in exported network or not fully-qualified.

Action: Supply a correct and fully domain-qualified Client Profile name.
NMC-03910 Database database is not defined in this network

Cause: The network being exported is stored on a database not defined within it; as a result, names.ora cannot be correctly exported.

Action: Store the network definition on a database defined within the network before exporting.
NMC-03952 Could not open V1 connect-string file filename

Cause: File could not be opened. If more information is available, it will appear under this error.

Action: Make sure the file exists and is readable.
NMC-03953 File filename is not correctly formatted

Cause: At least one line from the file is not correctly formatted for V1 import.

Action: Make sure that the file is, in fact, a V1 connect string file; if so, make sure that all lines are in correct import format ("<alias> = <V1-connect-string>" or "<alias> <V1-connect-string>"), are blank, or are commented (begin with a '#').
NMC-03954 File filename includes no valid V1 connect-strings

Cause: File is empty (or, perhaps, has only blank and commented lines).

Action: Import a file with some valid connect-strings.
NMC-03976 A value must be supplied for parameter parameter

Cause: A necessary parameter was not supplied to the program, either at the command line or at the parameter window.

Action: Supply a value for the parameter.
NMC-03978 Could not find current directory

Cause: Could not get name of current working directory. If more information is available, it will appear under this error.

Action:
NMC-03979 Could not open filename for output

Cause: Couldn't open file for writing. If more information is available, it will appear under this error.

Action: Make sure that the file is in a directory that exists and is writable.
NMC-03980 Error writing to filename

Cause: Couldn't write to the file. If more information is available, it will appear under this error.

Action: Make sure that the file exists and is writable.
NMC-03981 Only one of node and client_profile can be specified

Cause: Both node and client_profile are specified as parameters to netfetch.

Action: Supply a value for only one of these parameters.
NMC-03982 Network network_name is invalid and cannot be exported

Cause: Specified network is invalid and cannot be exported.

Action: Open network with Net Manager and correct the invalid objects.
NMC-04000 A value for CONNECT must be supplied

Cause: The database connect information has not been supplied.

Action: Restart the program with the parameter in the form username/password@connect
NMC-04001 A value for DEST_DIR must be supplied

Cause: The destination directory has not been supplied.

Action: Restart the program with the destination directory parameter.
NMC-04002 A value for NETWORK must be supplied

Cause: The network name has not been supplied.

Action: Restart the program with the network name.
NMC-04500 Network conversion has failed

Cause: A problem was found during conversion; see the rest of the message for more details.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMC-10002 failed to start event loop

Cause: The user interface was unable to start up.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMC-10003 failed to shutdown event loop

Cause: The user interface was unable to shut down properly.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMC-10006 failed to destroy all windows

Cause: The user interface was unable to shut down properly.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10007 failed to quit the window system

Cause: The user interface was unable to start up.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10013 failed to shutdown the application

Cause: The user interface was unable to shutdown properly.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10017 unable to process the dependencies for this change

Cause: During computation of the results of a user change, the program exceeded its maximum storage.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10018 unable to record invalid status for object object

Cause: An object was invalidated, but Net Manager was unable to record its status properly.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10019 error reloading window, arguments [argument, argument]

Cause: A window could not be reloaded from the resource manager.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10020 error loading window, arguments [argument, argument]

Cause: A window could not be reloaded from the resource manager.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10022 error using internal cache, arguments [argument, argument]

Cause: Internal error; tried to reference an entry at first argument; second argument is maximum number.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10023 error rereading class class

Cause: Could not reread a class that is already displayed.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10025 error running status window

Cause: An error was returned from Toolkit for the status window.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10032 create help session error, argument argument

Cause: Help session create routine has returned an error

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10033 show help screen error, argument argument

Cause: Help session show routine has returned an error.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10034 resource file error; can't find node in object object

Cause: Resource file has become corrupted since installation.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support. Then reinstall the resource file.
NMC-10035 resource file error; can't read analysis portion

Cause: Resource file has become corrupted since installation.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support. Then reinstall the resource file.
NMC-10036 resource file's analysis portion has incorrect version: version

Cause: Unable to locate the specified menu in the resource file.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support. Then reinstall the resource file.
NMC-10044 resource manager returned error_number on startup

Cause: An error occurred on startup of Resource Manager.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10045 failed to load window window from resource file

Cause: Unable to locate the specified window in the resource file.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10046 error starting the windowing system, arguments number

Cause: An error was encountered trying to start the windowing system.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMC-10047 can't initialize the clipboard

Cause: On startup, the clipboard could not be started.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMC-10048 incomplete data on clipboard

Cause: Clipboard data was corrupted.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMC-10049 failure in writing to clipboard

Cause: Unable to write data to the clipboard.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMC-10050 version mismatch in clipboard formats

Cause: Unable to read data from the clipboard.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMC-10051 unable to load resource resource from resource file

Cause: Unable to load a resource from the resource file.

Action: Not normally visible to the user. Contact Worldwide Customer Support.
NMC-10060 Control of newly created object is not allowed

Cause: User tried to control an invalid object.

Action: Save and validate object.
NMC-10061 Control of invalid object is not allowed.

Cause: User tried to control an invalid object.

Action: Validate object.
NMC-10062 Server Manager is not installed

Cause: Server Manager is not installed on this machine.

Action: Install Server Manager.
NMC-10063 Failed to start Server Manager

Cause: Failed to start Server Manager.

Action: Check permissions on Server Manager executable. If the error persists, contact Worldwide Customer Support.
NMC-10065 Failed to fork new process for Server Mnaager

Cause: Network Manager failed to fork a new process for Server Manager.

Action: Check that thre are enough system resources to allow additional processes to be created.
NMC-10080 Failed to construct the pathname of analysis.ora

Cause: Network Manager failed to create the full pathname of the analysis.ora.

Action: Check to see ORACLR_HOME is set. If the error persists, contact Worldwide Customer Support.
NMC-10081 Failed to open analysis.ora

Cause: Network Manager failed to open analysis.ora.

Action: Check the permissions on the file. Contact Worldwide Customer Support.
NMC-10082 Failed to read the number of classes from analysis.ora

Cause: Network Manager failed to read the number of classes from analysis.ora.

Action: Contact Worldwide Customer Support.
NMC-10082 Failed to read class details from analysis.ora.

Cause: Network Manager failed to read the class details from analysis.ora.

Action: Contact Worldwide Customer Support.

NMO Error Messages (NMO-01001 to 01300)

NMO-01001 out of memory

Cause: The application has run out of memory.

Action: Add more memory or run fewer processes.
NMO-01002 ROS table table has not been installed or is inaccessible

Cause: The application could not find a required ROS table. This error typically occurs when the document database has not yet been installed, or when the user does not have access privileges to the tables in the document database.

Action: If the document is stored in a database, make sure the database tables have been properly installed, and access privileges properly granted. If the document is stored in a file, then this error should not occur. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01003 error initializing ROS

Cause: The application was unable to initialize ROS during startup. If more information is available, it will appear under this error.

Action: Not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01004 error opening ROS file filename

Cause: An error occurred while trying to open a document file The error almost always occurs when the file either does not exist, or cannot be read and written by the application. If more information is available, it will appear under this error.

Action: Make sure that file exists and is both readable and writable by the application.
NMO-01005 error opening ROS database using user ID userid

Cause: An error occurred while trying to connect to a document database. The error can occur when the ROS database tables have not been installed on the database, or if the database is currently unavailable, or if SQL*Net connectivity between the application and the database has been interrupted.

Action: Make sure that the ROS database tables have been correctly installed on your database, that the database is running and that there is SQL*Net connectivity between the application and the RDBMS.
NMO-01006 cannot save an unnamed file

Cause: The application attempted to save a document with no name.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.
NMO-01007 lock for document document has been stolen by name

Cause: While you were working on a document, someone else requested that your lock on the document be broken and then took over the document. You may no longer save the document under its current name.

Action: If you want to save the document, you must now do so under a new name.
NMO-01008 document name length of length exceeds maximum of length

Cause: The maximum length of a document name was exceeded.

Action: Choose a shorter document name and retry the failing operation.
NMO-01009 document document has been locked by user name

Cause: The document has been locked by another user, and may not be edited by anyone else until it has been unlocked.

Action: An internal error not normally visible to the user. Normally, a locked document is detected by the application, which then asks the user what action to take. Wait until the document is no longer being worked on, and contact Worldwide Customer Support.
NMO-01010 document document already exists

Cause: You attempted to create a new document with the same name as that of an already existing document.

Action: An internal error not normally visible to the user. Normally, an existing document is detected by the application, which then asks the user what action to take. Save the document under another name, and contact Worldwide Customer Support.
NMO-01011 document has been corrupted

Cause: The application detected a corrupted document.

Action: Make sure the document has not been accidentally corrupted. If the document appears correct, the error is internal and you should contact Worldwide Customer Support.
NMO-01012 document document has version version_number but version_number is required

Cause: The document being opened is the wrong version and the application cannot interpret it.

Action: Run the document conversion utility supplied with this product. The utility will upgrade old documents to a version which can be understood by the application.
NMO-01013 document document not found

Cause: An attempt was made to open a nonexistent document.

Action: Use the document list function to get a list of available documents.
NMO-01014 database user ID length of size exceeds maximum of size

Cause: The maximum length of a database user ID was exceeded.

Action: Choose a shorter user ID and retry the failing operation.
NMO-01015 file name length of size exceeds maximum of size

Cause: The maximum length of a file name was exceeded.

Action: Choose a shorter file name and retry the failing operation.
NMO-01016 cannot modify a read-only document

Cause: You attempted to modify a document which has been opened for reading only.

Action: An internal error not normally visible to the user. Contact Worldwide Customer Support.
NMO-01017 cannot delete or rename the current document

Cause: You attempted to delete or rename the document that you are currently working on.

Action: Either close the current document, save it under another name, or open a new document and then delete or rename the old document.
NMO-01018 error loading meta data

Cause: The application failed to load document meta data while opening a new document. The error can occur if the document being opened has been corrupted in some way, but is usually an internal error.

Action: Be sure the document has not been accidentally corrupted. If the document appears correct, the error is internal and you should contact Worldwide Customer Support.
NMO-01019 error locking or unlocking document document

Cause: The application encountered an error while trying to lock or unlock a document. The error typically occurs when the document database has become unavailable, either because the database has shut down, or because SQL*Net connectivity between the database and the application has been interrupted.

Action: The error generally appears above a more specific error which will tell you the exact nature of the problem. Make sure the database is running and that you have SQL*Net connectivity to it.
NMO-01020 ORACLE error error

Cause: The application encountered an ORACLE error while trying to access the document database. The error typically occurs when the document database has become unavailable, either because the database has shut down, or because SQL*Net connectivity between the database and the application has been interrupted.

Action: Make sure the database is running and that you have SQL*Net connectivity to it.
NMO-01021 error initializing document context

Cause: The application could not create a new document context.

Action: The error appears above a more specific error which will tell you the exact nature of the problem.
NMO-01022 error copying document document from filename to database

Cause: The application encountered an error while trying to copy a document from a file to the document database. The error typically occurs when the document database has become unavailable, either because the database has shut down, or because SQL*Net connectivity between the database and the application has been interrupted.

Action: The error generally appears above a more specific error which will tell you the exact nature of the problem. Make sure the database is running and that you have SQL*Net connectivity to it.
NMO-01023 error copying document document from database to filename

Cause: The application encountered an error while trying to copy a document from the document database to a file. The error can occur when the document database has become unavailable, either because the database has shut down, or because SQL*Net connectivity between the database and the application has been interrupted. It can also occur if the file system has run out of space, or the file is not writable by the application.

Action: Make sure the database is running and that you have SQL*Net connectivity to it. Also make sure that there is disk space available, and that the application has permission to write the file.
NMO-01024 cannot rename a document onto itself

Cause: You attempted to rename a document its current name.

Action: You are not allowed to rename a document to its current name. Choose a different name and retry the operation.
NMO-01025 error creating new ROS file filename

Cause: The application failed to create a new ROS file by copying the current document to the new file. The error can occur if the new file is not writeable by the application, or if the file system runs out of space.

Action: Make sure the application has permission to write the new file, and that there is sufficient disk space available.
NMO-01026 unable to generate temporary ROS file in directory directory

Cause: The application was unable to generate a temporary file name in the specified directory. The error usually occurs either because there are too many old temporary files in the directory, or because the application lacks write permission in the directory, or because the file system is out of space.

Action: Remove old unused temporary files, make sure the file system has disk space, and that the application has permission to write files in the temporary file directory.
NMO-01027 error from ROS data store

Cause: the application encountered an error while accessing the ROS data store. If the current document is stored in a database, the error can occur when the document database has become unavailable, either because the database has shut down, or because SQL*Net connectivity between the database and the application has been interrupted. If the document is stored in a file, the error can occur if the file system has run out of space. The error generally appears above a more specific error which will tell you the exact nature of the problem.

Action: If your document is stored in a database, make sure the database is running and that you have SQL*Net connectivity to it. If the document is stored in a file, make sure that the application has permission to write the file.
NMO-01028 document document is owned by name

Cause: You attempted to create a new document with the same name as a document that is owned by someone else.

Action: Choose a different name. You may not overwrite someone else's document.
NMO-01029 document conversion failed

Cause: Internal error while conversion was taking place.

Action: Notify customer support and examine displayed error stack.
NMO-01030 must specify both old name and new name

Cause: One of the fields (either old name or new name) was empty.

Action: Specify a name in each of those fields.
NMO-01251 cannot open document, database context not initialized

Cause: The application attempted to operate on a document without first connecting to the document database.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01252 invalid class ID id

Cause: The application detected an invalid object class ID.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01253 invalid attribute ID id

Cause: The application detected an invalid object attribute ID.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01254 attribute name name not found

Cause: The application detected an invalid object attribute name.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01255 class ID id must be a CONCRETE class

Cause: The application detected use of an invalid object class ID.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01256 attribute ID id is read-only

Cause: The application detected an attempt to modify a read-only class attribute.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01257 type mismatch when setting attribute with ID id

Cause: The application detected an attempt to set an attribute to a val of the wrong type.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01258 invalid instance ID id

Cause: The application detected an invalid object instance ID.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01259 instance with ID id not found

Cause: The application attempted to issue an operation restricted to documents stored in a database, and the current document is stored in a file.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01261 instance ID id , attribute attribute length of size exceeds maximum of size

Cause: An internal size limit was exceeded.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01262 number of savepoints exceeds maximum of number

Cause: The internal savepoint limit was exceeded.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMO-01263 unable to record invalid status for object object

Cause: An object was invalidated but Network Manager was unable to record its status properly.

Action: An internal error not normally visible to the user. Save the document using the SAVE AS command, and contact Worldwide Customer Support.

NMR Error Messages (NMR-00001 to 00500)

NMR-00001 generic operation failure

Cause: A ROS operation failed.

Action: The error generally appears below a more general error which will tell you where the problem is occurring. See the action text for that error.
NMR-00100 unexpected end of file

Cause: A ROS file operation detected an end-of-file when it was not expecting one, probably because the file has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00101 object not found

Cause: A ROS fetch operation failed to find any objects.

Action: The error generally appears below a more general error which will tell you where the problem is occurring. See the action text for that error.
NMR-00102 object unexpectedly found

Cause: A ROS operation found an object when it was not expecting to.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00103 value too big

Cause: A ROS operation received an incorrect value.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00104 invalid value

Cause: A ROS operation received an invalid value. expecting one, probably because the file has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00105 invalid data store

Cause: A ROS operation detected an invalid data store, probably because the data store has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00106 invalid object type

Cause: A ROS operation received a value with an invalid type.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00107 unexpected NULL value

Cause: A ROS operation received an unexpected empty value.

Action: n internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00108 undefined or invalid table name

Cause: A ROS operation was performed on an invalid table.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00109 invalid argument

Cause: A ROS operation received an invalid argument.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00200 ROS file error

Cause: A ROS file operation detected an error.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00201 unique key violation

Cause: A ROS file operation detected a unique key constraint violation.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00205 page split occurred

Cause: A ROS file operation detected a page split.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00207 cannot close, commit is pending

Cause: The ROS user attempted to close a data store with a commit pending.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00210 error creating file

Cause: The ROS file store create operation failed.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00211 file version error

Cause: ROS detected a file store with an incorrect version.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00212 file already open read-only

Cause: A ROS file operation received an error.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00213 file already open read-write

Cause: A ROS database operation received an error.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.
NMR-00301 disk space exhausted

Cause: The application has run out of memory.

Action: Add more memory or run fewer processes.
NMR-00402 memory allocation failed

Cause: The application has run out of memory.

Action: Add more memory or run fewer processes.
NMR-00403 memory free failed

Cause: The application's memory heap has become corrupted.

Action: An internal error not normally visible to the user. For further details, turn on tracing and re-execute the failing operation. If the error persists, contact Worldwide Customer Support.

Prev Next

Library

Product

Contents

Index