Dealing with a corrupt file

Modified on Mon, 2 Aug, 2021 at 5:57 PM

If you got an error message ‘Could not open file’ – saying the file was corrupt or has a wrong extension (due to the network failure or disk space issue when you previously saved the file) you should be able to retrieve an earlier version, saved as backup.

Corruption of a project may happen because of one of the following:

The Omniscope server was brutally killed in the middle of saving (the process was killed, the VM was terminated, the power was cut...).
The file was on network storage and the network went down in the middle of saving it.

Note that Omniscope automatically saves IOX files in the background up to 30 seconds after making a change to a project.

Omniscope automatically creates an adjacent backup before proceeding with the save. If something goes wrong (such as the above), the file will be there for you to recover from manually. Otherwise, if Omniscope succeeds in saving the project completely, the backup will be automatically removed.

If there is insufficient disk space, if it is unable to create that backup, e.g. due to insufficient disk space, it creates a backup in your system temp folder, called "visokio_temp_tempres*.iok" (likely alongside many other Visokio temp files) where * is some unique auto-generated value. You may need to search by timestamp to find the right file.

If the IOX file in question has a timestamp you can see, it may indicate when the problem occurred. Perhaps you can correlate with your records for server maintenance, or find evidence of a problem in Omniscope's own logs.

If you need any further help let us know.