Skip to content

Operating System Error Messages

Overview

This section lists all operating system errors in numeric order.

The operating system errors are those in the error number range of 1-10 and are stored in the FlexErrs.dat database table.

Error List

1 - Disk full

Cause

  1. Disk space used up.
  2. Printer failure.

Resolution

  1. Make more disk space available.
  2. Check to ensure the printer is online and working. Try printing a test page if in doubt.

2 - Disk directory full

Cause

  • Folder (number of files) full.

Resolution

Move some files in the affected folder to another folder. You will have to make the appropriate change to the pathing environment of the application to reflect this change.

Example

Let us assume that the Order Entry sample workspace that ships with DataFlex has this problem when trying to write to one of its database tables. In that case, we would make a second data folder (Data2) and move some of the files in the first data folder (Data) into the new Data2 folder.

In that case, we would have to append the new data folder to the DataPath in the Registry key for the Order workspace:

DataPath = "C:\DataFlex {version} Examples\Windows\Order\Data; C:\DataFlex {version} Examples\Windows\Order\Data2"

where {version} is the version of DataFlex you are using.

3 - Cannot close current extent

Cause

Generally indicates problems with the operating system’s directory structure of the disk drive. Power failure is a common cause of directory corruption. If you have had other media errors, they can show up later as directory problems.

Resolution

Generally, the disk should be reformatted and data recovery techniques used. Usually, database tables triggering this error are irrecoverably damaged. Restoring data from a good backup is the best recovery method.

Verify proper configuration of Read Caching and Opportunistic Locking on your network.

4 - Seek to unwritten extent

Cause

  1. Generally indicates problems with the operating system’s directory structure of the disk drive. Power failure is a common cause of directory corruption. If you have had other media errors, they can show up later as directory problems.
  2. Can also occur if the transaction type of the database table is set to server atomic, but there is some problem with the Transaction Tracking System (TTS) on the Novell Netware server.
  3. Can also be generated by network problems.

Resolution

  1. Generally, the disk should be reformatted and data recovery techniques used. Usually, database tables triggering this error are irrecoverably damaged. Restoring data from a good backup is the best recovery method.
  2. Verify proper configuration of Read Caching and Opportunistic Locking on your network.
  3. Rebooting the Novell server sometimes resolves the problems. If not, consult your Novell Netware administrator and/or Netware documentation to fix the TTS problems.

5 - Directory overflow (disk full)

Cause

  • Directory (number of files) full.

Resolution

Move some files in the affected folder to another folder. You will have to make the appropriate change to the pathing environment of the application to reflect this change.

Example

Let us assume that the Order Entry sample workspace that ships with DataFlex has this problem when trying to write to one of its database tables. In that case, we would make a second data folder (Data2) and move some of the files in the first data folder (Data) into the new Data2 folder.

In that case, we would have to append the new data folder to the DataPath in the Registry key for the Order workspace:

DataPath = "C:\DataFlex {version} Examples\Windows\Order\Data; C:\DataFlex {version} Examples\Windows\Order\Data2"

where {version} is the version of DataFlex you are using.

6 - Seek past end of disk (disk full)

Cause

  • Disk space used up.

Resolution

Make more disk space available or relocate the table to another disk with more available space.

7 - Too many LOCK/REREADs in force

Cause

  1. Incorrect coding, where the application does not execute as many Unlock statements as Lock and Reread statements.
  2. Not enough file handles available to handle all the file locking in the application. This is usually the case if the error occurs after moving an application from one operating system to another or from one computer to another.

Resolution

  1. Correct the application source code so that the programming logic executes 1 Unlock statement for each Lock and Reread statement that is executed. You can use the DF_TRAN_COUNT attribute to debug problem code.
  2. Increase the available file handles; Windows operating systems should do this automatically. You can also reduce this problem by using the DF_FILE_MODE attribute to set database tables that are not written to read-only. You can also reduce this problem by using the close command to close database tables that you no longer need to keep open.

8 - Read error on .VLD file

Cause

This error is triggered when a read is attempted on a .VLD (compressed database table) file and the operating system returns an error. A typical cause of this error is damaged .VLD files. Rights are not typically a cause of this since the rights violation would be triggered when the file is opened.

Resolution

Restore the database file from backup.

9 - Write error on .VLD file

Cause

This error is triggered when a .VLD (compressed database table) file is written to. The operating system reports the error to DataFlex. This error may be caused by:

  1. Full disk.
  2. Lack of write rights.
  3. .VLD file damage.

Resolution

  1. Make more disk space available.
  2. Allow the user and/or application to have write rights to this database table.
  3. Restore the database file from backup or use data recovery techniques.

Verify proper configuration of Read Caching and Opportunistic Locking on your network.

10 - Out of memory

Cause

  1. Not enough physical memory (RAM) available for program loading and/or execution.
  2. An icon file embedded in the program is too big.

This error is fatal.

Resolution

  1. Make more physical memory available. Also, check to make sure that enough disk space is available to create a swap file (virtual memory).
  2. Reduce the icon file's size.