Citect SCADA uses a file handle to open each file. When you try to open too many files or databases simultaneously, Citect SCADA can need more file handles than are available.

You are likely to run out of file handles if you have many included projects. When Citect SCADA compiles your project, it will open several files in each include project at the same time, so each extra project you include will increase the usage of file handles. If you get this alert message when you have added another include project, you have run out of file handles. To verify this, remove one of the included projects to see if Citect SCADA can then compile your project.

With Windows running on a network, the setup of the number of file handles is located in various places. To increase the number of file handles in DOS, the setup is in the CONFIG.SYS file. If you are using Novell Netware you need to also increase the file handles in the NET.CFG or SHELL.CFG file. You need to also increase the number used by Citect SCADA with the [CtEdit]DbFiles parameter. Adjust the following settings the associated files:

CONFIG.SYS
FILES=120
NET.CFG or SHELL.CFG
file handles=120

The compiler cannot open a file that is referenced by the project you are trying to compile. The file does not exist, or it has become corrupt, or your system is out of file handles.

The compiler cannot read a file that is referenced by the project you are trying to compile. The end of file was found, or it has become corrupt. You should confirm that the file is functioning as expected.

The compiler cannot write to a file that is referenced by the project you are trying to compile. The file has become corrupt or the disk is full. You should confirm that the file is functioning as expected and that the required disk space is available.

A field is being referenced that does not exist. The database has been modified or has become corrupt. Pack the databases. If the error persists, contact Technical Support of this product.

The end of the database has been reached or the database has become corrupt. Pack the database. If the error persists, contact Technical Support for this product.

The beginning of the database has been reached or the database has become corrupt. Pack the database. If the error persists, contact Technical Support for this product.

Citect SCADA has run out of memory. Increase the amount of memory in the computer or use smaller databases.

An internal Citect SCADA software error has been detected. Contact Technical Support for this product.

The database has become corrupt or the file format is unknown. Pack the database.

A file the compiler is attempting to access is set to read only. Check that the file name is correct or change the attributes of the file.

An internal Citect SCADA software error was detected. Contact Technical Support of this product.

An output file could not be opened during compilation. Pack the database. If the error persists, contact Technical Support for this product.

The compiler is unable to function correctly due a lack of available disk space. Remove unwanted files from the disk, or replace the existing disk with a larger disk.

A file that is referenced by the project you are trying to compile appears to be locked. Check if the file is in use by another network user.

The include project specified in the Context field cannot be located in Citect Explorer. You should add the project, or update the reference.

The project specified in the Context field contains a circular reference. Check the structure of your include projects.

The database has a corrupted index. Pack the database.

The database needs to be indexed, but the index file associated with the database cannot be found. Pack the database.

The database is full. If the error persists, contact Technical Support for this product.

The end of the database has been reached or the database has become corrupt. Pack the database. If the error persists, contact Technical Support for this product.

The compiler cannot locate a file that is referenced by the project you are trying to compile. You should confirm that the file is in the specified location, or remove the reference to the file.

The maximum number of DBF files that can be open simultaneously has been exceeded. Increase the limit by changing the [CtEdit]DbFiles parameter.

The file has been opened by another user. Set the [General]ShareFiles parameter to 1 in the Citect.ini file to open files in shared mode.

The project you are trying to compile has more than 240 included projects defined. Reduce the number of included projects.

The project you are trying to compile refers to a protocol that does not exist.

The function library did not compile correctly.

More than 4500 user functions have been defined. To increase the number of functions allowed (up to 10000), use the parameter [CtEdit]MaxCicodeFunctions This error is often due to Cicode functions being defined in a number of included projects. Extending this parameter might affect system performance. Only set it when advised by Citect Customer Service.

The maximum number of points that can be referenced has been reached. The maximum point limitAn individual digital (or analog) variable read from an I/O device. Citect SCADA only counts physical points (and counts them only once, no matter how many times they are used). The point limit is the maximum number of I/O device addresses that can be read and is specified by your license. is determined by your Citect SCADA license. Contact Technical Support for this product.

The incorrect point limit is specified in the Citect.ini file. The point limit needs to correspond to your Citect SCADA license.

A system file has become corrupt, or been deleted. Re-install Citect SCADA on your system. If the error persists, contact Technical Support for this product..

A Cicode functions file, report format file, or an include file is too big. The maximum file size is 1 MB.

The code generated by a Cicode file is too large. Place the functions within the file into separate Cicode files.

An internal error has occurred within a DBF file. Set the parameter [OID]Reset=1 to regenerate the OIDs in the database.

An internal error has occurred within a DBF file. Set the parameter [OID]Reset=1 to regenerate the OIDs in the database.

The project you are trying to compile (or one of its included projects) does not appear to have a project ID. Specify an ID for the project in the Project General Properties.

The project you are trying to compile (or one of its included projects) does not appear to have a valid project ID. Specify an ID for the project (between 1 and 500) in the Project General Properties.

The project you are trying to compile has the same project ID as one of its included projects. Specify a new ID for one of the projects in the Project General Properties.

The project you are trying to compile references a protocol that is no longer supported. You should determine where the point of reference occurs and implement a supported protocol.

The Citect.ini file includes a parameter that is no longer supported. You should determine how the parameter is used and implement an alternative solution.

Alarm devices no longer need to be defined to use Alarm Properties as tags. Please refer to the help for the Migration Tool to make the required changes to your project.

The total size of your code is too large. Refer to article Q5600 in the Citect SCADA Knowledge Base.