Fatal Error

Fatal Error on POS

If you get a fatal error box and it has the text:

"The <file name> file has suffered fatal error" and <filename> is any of the

following, it is referring to the actual file name shown in parentheses after the

comma in the following list:

"Bad Check", (badck)

         "Cashier", (cash)

         "Cashier Reconciliation", (crec)

         "Current Sale Items", (possale)

         "Customer", (cust)

         "Department", (dept)

         "Discount", (msdisc)

         "Cashier EOD", (scecsh)

         "Fuel EOD", (scegas)

         "Hourly EOD", (scehrp)

         "Salesperson EOD", (scesal)

         "Sales Tax EOD", (scetax)

         "Terminal EOD", (scetrm)

         "General Message", (gmsg)

         "Tender Media EOD", (scxmedia)

         "Mix-match", (mmt)

         "Paid In/Out EOD", (piolog)

         "PLU", (plu)

         "Salesperson", (salep)

         "Register Parameter", (sparam.dat)

         "Stock", (stock)

         "Scales Tare", (mtare)

         "Sales Tax Breakpoint", (taxb)

         "Sales Tax Rate", (taxr)

         "Department EOD", (edpt)

         "Tender Media", (mstend)

         "Temporary Mix-match", (wmmt)

         "Truck Fleet Cash Advance", (scetfcsh)

         "Department Totals EOD", (edpttot)  

 

 

To remove the fatal error message, the corresponding file should be moved to the Program Files directory.

If additional text "iserrno: #X" appears where X is a number, it means that the

named file is an isam database and has three files with the prefixes (".dat", ".idx",

".lck") associated with the names. All three files will need to be moved to the Program Files directory.

The following is a list of "fatal errors" and their underlying causes.

"Cannot allocate memory for Button (button caption)"

Issed from PosButton::PosButton. This error occurs if, at startup, the constructor for the entitled button is unable to allocate memory for the data structure containing the button defintion data as read from default.kbd. This error indicates a serious hardware problem.

"Cannot create udccmd mutex"

Issued from host_udccmd. This routine sends command request packets to the LSC. The first time it is invoked, a mutex is created to regulate calls to this command from different threads. This error occurs if the creation of this mutex fails, and usually indicates a memory error.

"Cannot Copy System Log"

Issued from do_suspend. This error occurs when the program cannot copy the temporary electronic journal log file to the suspended electronic journal log name, and usually indicates a permissions problem or a hard disk drive error.

"Cannot Copy System MMT"

Issued from do_suspend. This error occurs when the program cannot copy the temporary mix-match data file to the suspended mix-match data file, and usually indicates a a permissions problem or a hard disk drive error.

"Cannot Copy System Receipt"

Issued from do_suspend. This error occurs when the program cannot copy the active receipt file to the suspended receipt file name, and usually indicates a permissions problem or a hard disk drive error.

"Cannot Copy System Sale"

Issued from do_suspend. This error occurs when the program cannot copy the active sale items file to the suspended sale items file name, and usually indicates a permissions problem or a hard disk drive error.

"Cannot Copy System WMMT"

See "Cannot Copy System MMT"

"EJRL: could not close file."

Issued from log_sys_err. This error occurs when the operating system cannot close the local electronic journal file, and usually indicates a hard disk drive problem.

EJRL: could not open file.

Issued from log_sys_err. This error occurs when the program cannot open the local electronic journal file, and usually indicates a permissions problem or hard disk drive problem.

EJRL: could not seek file position.

Issued from log_sys_err. This error occurs when the program cannot move the file pointer to a specified position within the file, and usually indicates a possible corruption of the file or a hard disk drive error.

"EJRL: could not tell file position."

Issued from log_sys_err. This error occurs when the program cannot query the file pointer as to its current position within the electronic journal file, and usually indicates a hard disk drive error.

"EJRL: could not write to file."

Issued from log_sys_err. This error occurs when the program cannot write data to the file, and usually indicates a hard disk drive error.

"Error reading default.kbd"

Issued from CMainFrame::OnCreateClient. This error occurs if, at startup, the program is unable to read all the data from the default keyboard definition file. This error indicates that the file has been corrupted or possibly a hard disk drive error exists.

"Illegal auth port (port number)"

Issued from set_up_port. This error occurs if, at startup, the port number passed to set_up_port falls outside a sane range (port < 0 || port > 34).

"System BP Receipt File Copy Failed"

See "Cannot Copy System Receipt".

"The (filename) file has suffered fatal error build error"

Issued from a file driver initialization routine (names vary according to the file driver). This error occurs when the file open fails and the driver routine attempts to create the database in an empty condition, and usually indicates a permissions error or a hard disk drive error.

The (filename) file has suffered fatal error "Cannot allocate record structure"

Issued from a file driver open routine (names vary according to the file driver). This error occurs when the program is unable to allocate memory for the file's record structure, and usually indicates a hardware memory error.

The (filename) file has suffered fatal error Cannot create mutex"

Issued from a file driver initialization routine (names vary according to the file driver). The first time it is invoked, a mutex is created to regulate calls to this command from different threads. This error occurs if the creation of this mutex fails, and usually indicates a memory error.

The (filename) file has suffered fatal error Cannot get mutex"

Issued from a main file driver routine (names vary according to the file driver). This error occurs when a basic I/O call is made to the file driver and the routine's attempt to obtain ownership of the mutex times out (rendering the program unable to perform file I/O for that file).

The (filename) file has suffered fatal error Cannot read record"

Issued from a file driver read routine (names vary according to the file driver). This error occurs when the driver attempts to read a record from the file fails, and usually indicates a permissions problem, an internal ISAM error, a corrupted file, or a hard disk drive error.

The (filename) file has suffered fatal error Cannot release mutex"

Issued from a main file driver routine (names vary according to the file driver). This error occurs when a basic I/O call is made to the file driver successfully obtains owenership of the mutex, performs its desired I/O, and then the routine's attempt to release the mutex times out (rendering the program

unable to perform any further file I/O for that file).

The (filename) file has suffered fatal error Cannot re-open file"

Issued from a file open routine (names vary according to the file driver). This error occurs when a file reopen routine fails, and usually indicates a permissions problem, or a hard disk drive error.

The (filename) file has suffered fatal error Cannot write record"

Issued from a file driver write routine (names vary according to the file driver). This error occurs when the program is unable to write a record into the file, and usually indicates a permissions problem or hard disk drive error.

The (filename) file has suffered fatal error Key creation Failure"

Issued from a file driver insert routine (names vary according to the file driver). This error occurs when the file driver is unable to create an index key for the named file's index. Sources of this error can vary from an internal ISAM library error to a permissions problem or a hard disk drive error.

The (filename) file has suffered fatal error Record Insertion Failure"

Issued from a file driver insert routine (names vary according to the file driver). This error occurs when the file driver is unable to insert a new record into the file, and usually indicates a corrupted index file.

The (filename) file has suffered fatal error Unable to open file"

Issued from a file driver open routine (names vary according to the file driver). This error occurs when the program been unable to both open or create the named file, and usually indicates a permissions problem or hard disk drive error.

"Unable to create EFS reefer semaphore"

Issued from setup_semaphores. This routine creates semaphore objects listened for by the get_key routine. This error occurs if, at startup, creation of the entitled semaphore fails, and usually indicates a serious memory hardware problem.

"Unable to create scanner mailbox"

Issued from StartScannerThread: This error occurs if, at startup, the program is unable to create a Mailbox object for use with the bar code scanner interface. This error indicates a serious memory hardware problem.

"Unable to create scanner message"

Issued from StartScannerThread: This error occurs if, at startup, the program is unable to create a Message object for use with the bar code scanner interface. This error indicates a serious memory hardware problem.

"Unable to create scanner semaphore."

Issued from StartScannerThread: This error occurs if, at startup, the program is unable to create a Semaphore object for use with the bar code scanner interface. This error indicates a serious memory hardware problem.

"Unable to initialize auth port (port number)"

Issued from set_up_port. This error occurs if, at startup, the program could not initialize the entitled port. See "Unable to initialize port (port number)" for more detail.

"Unable to initialize port (port number)"

Issued from InitPort. This error occurs if, at startup, the program is unable to initialize the entitled serial port. This could indicate a setup problem wherein a port that does not exist on the computer has been designated for use. If the designated port does exist, then there is a hardware issue.

"Unable to open default.kbd for reading."

Issued from CMainFrame::OnCreateClient. This error occurs if, at startup, the program is unable to open the default keyboard definition file. This error indicates that the operating system would not provide a valid file handle. This error indicates a possible hard disk drive issue.

"Unable to release credit card transaction resumption semaphore."

Issued from ProcessSuspendedSales. This error occurs if, when a credit card authorization request reply arrives from the CCL, the program is unable to release the entitled semaphore and effectively renders the POS unable to take network tenders. This error usually indicates a serious memory hardware problem.

"wait_comm: could not create mutex!"

Issued from waitComm. This routine waits for reply messages from the LSC. The first time it is invoked, a mutex is created to regulate calls to this command from different threads. This error occurs if the creation of this mutex fails, and usually indicates a memory error.

"We did not finish loading graphics"

Issued from CMainFrame::OnCreateClient. This error occurs if, at startup, the program is unable to load basic fuel dispenser graphic images into memory for use in rendering fuel dispenser button images. This error indicates a serious hardware issue.

If any of these messages are seen, run chkdsk /f twice with reboots.

0 Comments

Add your comment

E-Mail me when someone replies to this comment