AionDS Messages and Codes Guide

AionDS Messages and Codes Guide AionDS Messages and Codes Guide

arti.vub.ac.be
from arti.vub.ac.be More from this publisher
29.06.2013 Views

Fatal system errors Fatal system errors .........................................................................................................................................................................................................˝.......................................... Overview 7-4 AionDS Messages and Codes This section documents the fatal system errors and, where possible, offers suggested responses. Fatal system errors are formatted as follows: where system: Internal Error error, subcode system name of the AionDS system that detected the fatal system error error fatal system error subcode related subcode that can assist the PLATINUM Technical Support for AionDS and Development staff in diagnosing the problem .........................................................................................................................................................................................................˝.......................................... Example Here is an example of a fatal system error: AionDS/OS2: Internal Error 23600,101 The fatal system errors are listed below in numerical order. .........................................................................................................................................................................................................˝.......................................... 100 to 199 An internal error was detected in the character string processing package. .........................................................................................................................................................................................................˝.......................................... 1000 to 1099 An internal error was detected by the display management system. .........................................................................................................................................................................................................˝.......................................... 1300 to 1399 An internal error was detected while executing a KDL statement. .........................................................................................................................................................................................................˝.......................................... 1600 to 1699 An inconsistency was detected in the knowledge base.

Fatal system errors ............................................................................................................................................................................. 1601 If the fatal error is 1601, AionDS displays the following message at edit-time: Severe Error -- Attempt to Continue? Answer YES and immediately export the knowledge base. You should be able to import the knowledge base and continue without having lost any of your changes. If you cannot continue, do not export the knowledge base again. Contact PLATINUM Technical Support for AionDS. At runtime, the 1601 error causes AionDS to terminate execution of the knowledge base because it is corrupted. In this case, you should restart AionDS and attempt to export and import the knowledge base before you continue. If you cannot continue, do not export the knowledge base again. Contact PLATINUM Technical Support for AionDS. ............................................................................................................................................................................. 1605 If the error number is 1605, you can export the knowledge base and import it again. ............................................................................................................................................................................. Other 1600 errors If the error number is not 1601 or 1605, you should import the knowledge base and resume work from that point. If you do not have a recent export file, you can attempt to load the knowledge base without error checking. For more information: See your Installation and Operation Guide for information about using command line switches to modify startup options. During the knowledge base development cycle, you should periodically export the knowledge base. For more information: See the AionDS User’s Guide or User’s Guide (Character-Based) for more information about the AUTO-EXPORT profile option. AionDS Fatal System Errors 7-5

Fatal system errors<br />

.............................................................................................................................................................................<br />

1601<br />

If the fatal error is 1601, <strong>AionDS</strong> displays the following message at edit-time:<br />

Severe Error -- Attempt to Continue?<br />

Answer YES <strong>and</strong> immediately export the knowledge base. You should be able<br />

to import the knowledge base <strong>and</strong> continue without having lost any of your<br />

changes. If you cannot continue, do not export the knowledge base again.<br />

Contact PLATINUM Technical Support for <strong>AionDS</strong>.<br />

At runtime, the 1601 error causes <strong>AionDS</strong> to terminate execution of the<br />

knowledge base because it is corrupted. In this case, you should restart<br />

<strong>AionDS</strong> <strong>and</strong> attempt to export <strong>and</strong> import the knowledge base before you<br />

continue. If you cannot continue, do not export the knowledge base again.<br />

Contact PLATINUM Technical Support for <strong>AionDS</strong>.<br />

.............................................................................................................................................................................<br />

1605<br />

If the error number is 1605, you can export the knowledge base <strong>and</strong> import it<br />

again.<br />

.............................................................................................................................................................................<br />

Other 1600 errors<br />

If the error number is not 1601 or 1605, you should import the knowledge<br />

base <strong>and</strong> resume work from that point. If you do not have a recent export<br />

file, you can attempt to load the knowledge base without error checking.<br />

For more information: See your Installation <strong>and</strong> Operation <strong>Guide</strong> for<br />

information about using comm<strong>and</strong> line switches to modify startup options.<br />

During the knowledge base development cycle, you should periodically export<br />

the knowledge base.<br />

For more information: See the <strong>AionDS</strong> User’s <strong>Guide</strong> or User’s <strong>Guide</strong><br />

(Character-Based) for more information about the AUTO-EXPORT profile<br />

option.<br />

<strong>AionDS</strong> Fatal System Errors 7-5

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!