![]() ![]() The project you are trying to compile has more than 240 included projects defined. Set the ShareFiles parameter to 1 in the Citect.ini file to open files in shared mode. The file has been opened by another user. Increase the limit by changing the DbFiles parameter. The maximum number of DBF files that can be open simultaneously has been exceeded. You should confirm that the file is in the specified location, or remove the reference to the file. The compiler cannot locate a file that is referenced by the project you are trying to compile. If the error persists, contact Technical Support for this product. The database needs to be indexed, but the index file associated with the database cannot be found. Check the structure of your include projects. The project specified in the Context field contains a circular reference. You should add the project, or update the reference. The include project specified in the Context field cannot be located in Citect Explorer. The include project was not found in Citect Explorer Check if the file is in use by another network user. Remove unwanted files from the disk, or replace the existing disk with a larger disk.Ī file that is referenced by the project you are trying to compile appears to be locked. The compiler is unable to function correctly due a lack of available disk space. Contact Technical Support of this product.Īn output file could not be opened during compilation. Check that the file name is correct or change the attributes of the file.Īn internal Citect SCADA software error was detected. Pack the database.Ī file the compiler is attempting to access is set to read only. The database has become corrupt or the file format is unknown. Contact Technical Support for this product. ![]() Increase the amount of memory in the computer or use smaller databases.Īn internal Citect SCADA software error has been detected. If the error persists, contact Technical Support for this product.Ĭitect SCADA has run out of memory. The beginning of the database has been reached or the database has become corrupt. The end of the database has been reached or the database has become corrupt. If the error persists, contact Technical Support of this product. The database has been modified or has become corrupt. You should confirm that the file is functioning as expected and that the required disk space is available.Ī field is being referenced that does not exist. The file has become corrupt or the disk is full. The compiler cannot write to a file that is referenced by the project you are trying to compile. You should confirm that the file is functioning as expected. The end of file was found, or it has become corrupt. The compiler cannot read 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 open a file that is referenced by the project you are trying to compile. Adjust the following settings the associated files: You need to also increase the number used by Citect SCADA with the DbFiles parameter. If you are using Novell Netware you need to also increase the file handles in the NET.CFG or SHELL.CFG file. To increase the number of file handles in DOS, the setup is in the CONFIG.SYS file. With Windows running on a network, the setup of the number of file handles is located in various places. To verify this, remove one of the included projects to see if Citect SCADA can then compile your project. If you get this alert message when you have added another include project, you have run out of file handles. 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. You are likely to run out of file handles if you have many included projects. When you try to open too many files or databases simultaneously, Citect SCADA can need more file handles than are available. Increase value of the parameter DbFilesĬitect SCADA uses a file handle to open each file. If the Type specified for a compile error message is WARNING, see the topic Compile Warning Messages. If the Type specified for a compile error message is ERROR, see the topic Compile Error Messages. For information on how to address a message of this type, use the code included in the error description (for example, " F4001") to locate the fatal message in the following table. ![]() If the Type specified for a compile message is FATAL, it means something was detected that stopped the project from compiling successfully. Compile > Compile a Project > Compile Messages > Compile Fatal Messages Compile Fatal Messages ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |