Text |
Natural program error: Infinite recursion. |
Explanation |
The typical program in which this error occurs is a dialog containing the statement CLOSE DIALOG *DIALOG-ID for the CLOSE event. |
Action |
Check for recursive calls. |
Text |
Error while unlocking the object. |
Explanation |
Either your network software contains an error or Natural detected an internal error while unlocking a locked object. |
Action |
Check your environment. |
Text |
Error during lock of object. |
Explanation |
Either your networking software has an error or Natural detected an internal error while locking an object. |
Action |
Check your environment. |
Text |
Error closing file. |
Explanation |
Natural tried to close a file it has opened, but an error was returned by the operating system. |
Action |
Check your environment. If you cannot find the cause of the problem, contact Software AG support. |
Text |
Attempt to modify a read-only system file. |
Explanation |
Natural tried to open a file in the system file emulation for writing, but this system file was declared as read-only in the global config file. |
Action |
Either do not attempt to modify the system file or remove the read only flag from NATCONV.CFG |
Text |
Internal error in the system file emulation. |
Explanation |
Natural encountered an internal error in the system file emulation. |
Action |
Contact Software AG support. |
Text |
Dialog called from non-gui environment. |
Explanation |
A gui environment is created when a dialog is started at level 1.
Dialogs may then be called.
A non-gui environment is active when:
- a PROGRAM is started at level 1 or
- Natural executes as server.
It is not possible to call a dialog in a non-gui environment. |
Action |
Check your program and remove the calls to dialogs or start the program via a dialog. |
Text |
Failed to send object descriptor to repository. |
Explanation |
During a Natural / repository synchronize operation, Natural was not able to send a Natural object description to the repository. |
Action |
Check your environment |
Text |
Repository error: failed to delete library. |
Explanation |
The Natural repository was called by the Natural system file driver to delete a whole library and returned an error code. |
Action |
Check your environment. |
Text |
Repository error: failed to rename library. |
Explanation |
The Natural repository was called by the Natural system file driver to rename a library and returned an error code. |
Action |
Check your environment. |
Text |
Repository error: failed to save object. |
Explanation |
The Natural repository was called by the Natural system file driver to save an object and returned an error code. |
Action |
Check your environment. |
Text |
Repository error: failed to lock object. |
Explanation |
The Natural repository was called by the Natural system file driver to lock an object and returned an error code. |
Action |
Check your environment. |
Text |
Repository error: failed to unlock object. |
Explanation |
The Natural repository was called by the Natural system file driver to unlock an object and returned an error code. |
Action |
Check your environment. |
Text |
Object saved successfully. Repository information may be faulty. |
Explanation |
The Natural object was saved and/or cataloged successfully, but the object information stored in the Natural repository may be incorrect as a repository operation failed. |
Action |
Retry the operation. If the error reoccurs, contact your system administrator or Software AG support. |
Text |
Cannot insert global or application-independent variables. |
Explanation |
This error can have two causes: a) out of memory b) table overflow Either the operating system is not configured correctly or there is not enough space on the disc for the system swapfile. All descriptions of application-independent variables are collected in a table of limited size. The table can overflow if an extremely large number of application-independent variables is created. The same situation applies to context variables. Check the configuration settings of the operating system and correct them if neccessary. Then check the available disk space for your system swapfile. Check the number of application-independent and context variables. |
Action |
Contact your system administrator. |