Execu/Tech Systems, Inc.
850-747-0581 Email Website
IndexBookmarkPrint This Article

Home > Errors / Fixes > Rebuild Corrupted File

Rebuild Corrupted File

If you have any questions about dealing with a potentially corrupted file, call support before you attempt to perform any of these actions.


 If you experience these situations, you've got network or hardware problems:

  • The errors occur more than four times a year. 
  • The errors come and go, without having to rebuild the file.


Most of the time, corrupted files can be rebuilt with no loss of data. Often, your first symptom of a corrupted file will be an error message similar to this:


File error 91, 02 on GACNTL.FIL . . .

This error message indicates that the file causing the error is GACNTL.FIL and this is the file that would need rebuilding. Your error may indicate a different file, and that is the file that will need rebuilding.


Running the Rebuild Utility


The computer where the rebuild will be performed should be the only one logged into the software. DO NOT LET ANY OTHER COMPUTERS LOG INTO THE SOFTWARE BEFORE YOU RUN THE REBUILD!!!!

There are two ways to run the rebuild utility:

1. Though a Graphical User Interface (GUI)


You get there by clicking File > Special > System Information. It might take a few seconds to open.

Note: If you don't have the modern drop-down menus, type 88 to run a program by name. The program name you will enter is MENUSYSI. Run Program by Name

The System Information window will open:

If the file you are rebuilding is one of the common core files, you'll find it in the Select Item from List for Quick Rebuild drop-down box. If you find it there, select it and then click Quick Rebuild

If you don't see the file, click Select File, below and to the left of the Quick Rebuild button. Find the file, ending in ".fil", to rebuild. After the file is located, click the Open button to return to the main System Information window with the file you selected displayed in the box. To rebuild this file, you click the Rebuild File button, located below and to the right of the Select File button. 

2. Using the Command Prompt

*This can only be done at your server, where the software is installed on a local hard drive.

If you don't have access to the System Information utility, you can run the rebuild from the Command Prompt. Different versions of Windows access the Command Prompt in different ways, so use Google to determine how to access it on your computer. 

  • Make sure you have the name of the file that's causing the error.
  • You'll need to change the directory to where the software is installed.
  • In this example, we use the file name GACNTL.FIL, but the file name in your error message may be different. Use the file name in your error message.

In the Command Prompt, type vutil32 -r GACNTL.FIL and press the Enter key. (You would replace GACNTL.FIL with the file name in your error message.)

The Rebuild

After clicking either Quick Rebuild or Rebuild File, you'll see a command window open with the progress and results of your file rebuild.

If you receive a response similar to this one, telling you how many records were recovered and how many deleted records were removed, then the rebuild was successful. Type Y and press Enter to replace the original (corrupted) file with the new (rebuilt) one. 


Chain of records is broken!

This means that there is a point in the file where the damage is just too severe to recover. This is rare, but it happens, and is usually the result of large chunks of data being removed from the file.


When it does happen, you'll find that you usually lost a single record (the last one to be saved when the problem occurred.) You will lose all of the lost records. Depending on the affected file, these could be reservations, Point of Sale transactions, etc., so it's a good idea to call Execu/Tech Support and ask for advice.


Type N and we will have you rerun this utility, if needed. While you're calling us, you should also try to locate your backup, because you may need to restore it if the damage is too severe.

Duplicate Key


This is usually due to network traffic problems and hard drive caching problems. This does what is impossible to do in the software: add records with a duplicate key. Most often, these are the same records created a second time because of a failure in the hard drive caching. It's very rare, but it happens (typically only to a few records.) As in the previous case, you should call Execu/Tech Support.

File Locked - File not rebuilt



  Sometimes this error occurs but the file is still successfully rebuilt. Verify this by trying the process that produced the error and if the error is gone, the file was rebuilt.


This error often occurs because the file is locked by a computer running the software, the user doesn't have write access, or the file has been set to "Read Only".

  • Make sure that no computers are running the software when you try the rebuild. The computer where the rebuild is run from should be the only one logged into the software.
  • Make sure that the Windows user has "write access" to the file.

  • Make sure that the file isn't set to "Read Only."

  • You can try to release any locks on the file. See Release Locked File below.
Not a Vision File - Rebuild Stopped



Vision is the file structure used in many of the files, and the error can be caused by three reasons:

1. The file really isn't a Vision File, and you may have selected the wrong file to rebuild. 


2. The file is locked by another user, which sometimes happens when a file is corrupted, and the error is on their screen. You can try to release any locks on the file.​ See Release Locked File below.

    ​3. The file has been damaged beyond recognition. Locate your backup, because you may need to restore this file.


    If, after restarting your server, the error continues, call Execu/Tech Support. It may be that you're trying to rebuild a file that doesn't use the Vision File structure, or the file may be damaged beyond all recognition.

    Release Locked File

    • If it's in a shared folder, you can release any locks from the server using Windows Computer Management. See Close an Open File.
    • If you don't see the file in the Computer Management console, you can restart ALL client computers and then restart your server. 
    • ​​You can try this command prompt to unlock the file: VUTIL32 -ZERO GACNTL.FIL  (Example only. Replace GACNTL.FIL with the file name displayed in your error message.)

    The computer where the rebuild is performed should be the only one logged into the software. DO NOT LET ANY OTHER COMPUTERS LOG INTO THE SOFTWARE BEFORE YOU RUN THE REBUILD!!!!

    Related Pages
    Cobol File Errors
    Slow / Stuck Software
    Network Benchmark
    Common System Issues

    Article ID
    Last Modified
     11/26/2023 6:34 PM