- Article Type: General
- Product: Aleph
- Product Version: 20, 21, 22, 23
You see a message like this in a server, ue, or job log:
Execution error : file '/exlibris/a18_1/aleph/exe/pc_xxx_yyyyy.gnt'
error code: 114, pc=0, call=65, seg=0
114 Attempt to access item beyond bounds of memory (Signal 11)
115 Unexpected signal
A ".gnt" error is a program error. The name of the program precedes the ".gnt". In this example, it's "xxxx_yyyy"..
When you see such an error, you should do an Exact search in the CRM database like this:
Over 30 specific errors, with resolutions, are included in the CRM Knowledge Base.
In some cases these represent bugs and a correction (rep_change) has been issued for them.
In other cases there may be a particular type of data or table value which is known to cause the error.
If you don't find anything in the CRM database, then look in the log for other error messages, immediately preceding the Execution error. Sometimes such messages can give a clue as to the cause of the Execution error.
If you don't see an immediately preceding error message, you should try the function in USM to see if you get the error there too.
If no Article is found with the specific program,...
* if the error code is 114 (Attempt to access item beyond bounds of memory) consult the article " Error Code 114 Attempt To Access Item Beyond Bounds Of Memory (Signal 11) "
* if the error code is 115 (Unexpected signal), consider whether the server or daemon where the error occurs may have been shut down, for instance, by an Aleph or system shutdown.
If this doesn't help contact Ex Libris Support.
- Article last edited: 2/25/2015