This error is usually caused by two or more terminals editing the same record at the same time. This can happen when warnings are overridden or if functions in the Night Audit are performed while users are still logged in and editing records. Call support for assistance.

23

Record not found.

24

Disk full for relative or indexed file. (write)

The hard drive containing the Execu/Tech software database is full. Contact your IT immediately!

Permanent error. This is an error not otherwise described in this table.

If the error contains "FILE ERROR: 3000" and "Check your network connection" then view this page for additional information. File Error: 3000

This error, and the error below, are often associated with Point of Sale printing. $windows will sometimes be seen in the error because we use this internal designation for the Windows print spooler. This is usually caused by a failure of your print spooler, changing printer names or removal of printers. The software is looking for a specific printer and Windows can't find it. Try rebooting. If rebooting doesn't fix the problem, contact your IT to troubleshoot.

If this is Point of Sale, try reselecting the printer using this guide: POS Printer Setup

It can also be caused by hard drive or network failure if the error is related to a file. Try rebooting. If the errors occur often, please have an IT professional look at your entire system, including the server, clients, network infrastructure, etc.

30, xx

Permanent error. This is any error not otherwise described.

​

The secondary code value is set to the host system's status value that caused the error. See your operating system user manual for an explanation.
The list of secondary code values for Microsoft Windows can be found here. Note that the secondary code is the number AFTER "30."
System Error Codes

These errors can be caused by hard drive or network failure if the error is related to a file. Try rebooting. If the errors occur often, please have an IT professional look at your entire system, including the server, clients, network infrastructure, etc.

34

Disk full for sequential file or sort file. (write, sort)

The hard drive containing the Execu/Tech software database is full. Contact your IT immediately!

The requested operation is not supported by the host operating system. For example, a deferred file system initialization failed, or a READ PREVIOUS verb was executed and the host file system does not have the ability to process files in reverse order. (any)

If you are using AcuXML, this error results when the program tries to open a file EXTEND or I-O. With AcuXML, programs are able to open files INPUT or OUTPUT only.

There are no entries left in one of the lock tables. The secondary error code indicates which table is full:

01 - operating system lock table  02 - internal global lock table (see the MAX_LOCKS configuration variable)  03 - internal per-file lock table (see the LOCKS_PER_FILE configuration variable)

This indicates an internal error defined by the host file system. The "xx" is the host system's error value. This is similar to error "30", except that "xx" is specific to the host file system instead of the host operating system. For example:

02 - In Acu4GL or AcuXML, 9D,02 indicates that an XFD file is corrupt. This could be the result of a parsing error.

03 - In Acu4GL or AcuXML, 9D,03 indicates that an XFD file is missing. This could be the result of a parsing error.

5 - In AcuXML, 9D,05 indicates that there was an XFD parsing error, so AcuXML was unable to read a record.

Refer to the specific Acucorp product documentation for more details on the host file system's error codes.

91

File not open. (close)

The file may be corrupted. You can try rebuilding the file specified. Rebuild Corrupted File

91

File not open. (unlock)

The file may be corrupted. You can try rebuilding the file specified. Rebuild Corrupted File

91, 02

File not open. (read, start)

The file may be corrupted. You can try rebuilding the file specified. Rebuild Corrupted File

Sometimes this is related to printing. If it is, it's because Windows can't find the printer or it fails to respond. Try rebooting. Contact your IT professional to troubleshoot.

91, 02

File not open. (write)

The file may be corrupted. You can try rebuilding the file specified. Rebuild Corrupted File

Sometimes this is related to printing. If it is, it's because Windows can't find the printer or it fails to respond. Try rebooting. Contact your IT professional to troubleshoot.

91, 02

File not open. (rewrite, delete)

The file may be corrupted. You can try rebuilding the file specified. Rebuild Corrupted File

Sometimes this is related to printing. If it is, it's because Windows can't find the printer or it fails to respond. Try rebooting. Contact your IT professional to troubleshoot.

91, 02 on $windows

91, 02 on $printer

​

Either of these errors likely means this is related to the printer. Try logging out of the software and back in and select the correct printer from within the software.

92

File is already open. (open)

The file may be open by another terminal or a Remote Desktop session that didn't fully disconnect. You can use Computer Management to check this and release the file or, if using Remote Desktop, disconnect any idle sessions you suspect of causing the problem. As a last resort, you can reboot the server.

93

File locked by another user. (open)

The server has locked the file specified and your user can't access it. You typically only see this error when a computer locks up or there is a break in network communication during a read or write process. Try rebooting your computer. If that doesn't work, reboot the server as well.

If you're technically savvy, you might be able to unlock the file at the server using the Computer Management console. This link from Microsoft might help: Close an Open File
If you need assistance with the instructions provided by Microsoft, contact your qualified IT professional. You may also consider rebooting first to see if that fixes the problem.

93, 03

File previously closed with LOCK by this run unit. (open)

94, xx

​

01 - mismatch found but exact cause unknown (this status is returned by the host file system)

02 - mismatch found in file's maximum record size

03 - mismatch found in file's minimum record size

04 - mismatch found in the number of keys in the file

05 - mismatch found in primary key description

06 - mismatch found in first alternate key description

07 - mismatch found in second alternate key description

The list continues in this manner for each alternate key.

94, 10

Too many files open by the current process. (open)

94, 20

File not found. (open, sort)

94, 62

One of the LINAGE values for this file is illegal or out of range. (open, write)

94, 62

Key not specified (specifying a table whose size is zero) in a SORT or MERGE statement

95, 01

The file being opened is not on a mass-storage device which is required for the file type or the requested open mode. (open)

95, 02

Attempt to open a sequential file with fixed-length records as a Windows spool file.

95, 08

Attempt to open a print file for INPUT. (open)

95, 09

Attempt to open a sequential file for I/O and that file has automatic trailing space removal specified. (open)

95, 99

A Windows or Windows NT runtime that is not network-enabled tried to access a file on a remote machine.

No current record. This usually occurs when the previous operation on the file was a START that failed, leaving the record pointer undefined. (read next)

Try rebooting your workstation and running the process again. If this occurs when looking up guests in the PMS, you may need to run GANXREF. Please contact Support for specific instructions on completing this step.

If no file name is given sometimes then it may be printer related. Try printing to screen. If that works, make sure a printer is selected before printing. If printing to screen works but your selected printer doesn't, select a different printer. You'll need to troubleshoot your printer if it seems to be causing the error.

97

Record size changed. The record being rewritten is a different size from the one existing in the file, and the file's organization does not allow this. (rewrite)

This status code can also occur if the record is too large or too small according to the RECORD CONTAINS clause for the file. (write, rewrite)

98, xx

Indexed file corrupt. An internal error has been detected in the indexed file. The secondary status code contains the internal error number. The file should be reconstructed with the appropriate utility.

The file may be corrupted. You can try rebuilding the file specified. Rebuild Corrupted File

99

Record locked by another user. This is different from file error 93, because the file itself isn't locked, just a single record within that file.

It's common to see this error temporarily flash then go away. Sometimes, the error will remain, and if it does, you should check for a couple things:

• Someone may be running a report that takes a while to complete. During this time, some files might be locked.
• Someone may be editing setup records like Rooms, Payment Codes, Point of Sale Store Record, Items or Categories, etc. If someone were to leave their terminal while in the middle of editing the Store Record, for example, you might see file error 99 when selling items, running reports or closing the day. If this happens you can try to find the offending terminal or you can restart the server.