No I/O devices have been defined in this project or any of its included projects (see Add an I/O Device).

An included project (specified in the Included Projects database) does not exist. Check the name of the included project. For more information, see Included Projects.

This error will occur when a Cicode function is defined with a default argument before an argument without a default. For example:

INT
FUNCTION LogFieldValue(string sFile, string sField = """", string sValue)
…
END

In this case, you will need to review how this function is used and either add a default value to argument sValue or remove the default from the argument sField. For example:

INT
FUNCTION LogFieldValue(string sFile, string sField = """", string sValue = """")
…
END

or

INT
FUNCTION LogFieldValue(string sFile, string sField, string sValue)
…
END

Too many or too few arguments have been passed to a Cicode function.

A tag that is included in your project in not referenced and appears to serve no purpose. Consider removing the tag, or add the required reference to the tag.

A Cicode function name within the project has the same name as an in-built Cicode function. It is recommended that you rename your function. You can then use the find and replace dialog to update any references to the original function name.

The compiler has detected a reference to a tag that does not exist. You should create the required tag, or update the reference.

A Cicode function that is used in your project has been deprecated, which means it will be made obsolete in a future release. You should consider replacing the Cicode function.

A Cicode function that is used in your project has been deprecated, which means it will be made obsolete in a future release. Currently, you can only call the function on a server. You should consider replacing the Cicode function.

A Cicode function that is used in your project has been deprecated, which means it will be made obsolete in a future release. Currently, the function does not support online changes. You should consider replacing the Cicode function.

The project refers to an alarm property that is associated with an alarm tag that does not exist. Create the specified alarm tag, or confirm that it is available on the alarm server.

The specified standby I/O device requires a priority setting.

Citect SCADA was unable to execute a command, script or batch file that was specified to run when compilation is complete. Check the replacement strings used for the parameters [CtEdit]CompileSuccessfulCommand and [CtEdit]CompileUnsuccessfulCommand to determine what occurred.

Citect SCADA may behave unexpectedly if you use a tag name that is the same as a cluster name. You should rename the specified tag.

I/O devices with the same unit number must all use the same protocol.

I/O devices with the same unit number must either be all disk devices, or all non-disk devices.

I/O devices with the same unit number must either be all memory or all non-memory.

The compiler has detected a reference to a file cannot be found. Check that the file is available, and that name used is correct.

Multiple translations for a native string have been detected in the language database(s). You should review the language databases associated with your project (including those in any included projects), and remove any duplications.

A language has been defined multiple times in the language database (LANG.dbf). You should check the languages specified your project (including those in any included projects) and remove the duplication.

The compiler has detected some incorrect Cicode syntax. For example, an operand may be missing between a tag and a constant.

When the compiler finds a double-register variable, it remembers which boundary it is on and checks that all other double register variables are on the same boundary. This message will appear if the address of a long or real variable is not aligned correctly. For more information, see [General]CheckAddressBoundary.

The Cicode function uses the keyword RETURN but the function header does not contain a return type.

For example:

FUNCTION LogFieldValue(string sFile, string, sField, string sValue)
...
Return = FileOpen(sFile, "a+")
IF iReturn = -1 THEN
RETURN -1;
END
...
END

Change this function to the following:

INT
FUNCTION LogFieldValue(string sFile, string, sField, string sValue)
...
iReturn = FileOpen(sFile, "a+")
IF iReturn = -1 THEN
RETURN -1;
END
...
END

The compiler has detected that the local language setting is duplicated across the main project and its included projects. This means the language databases associated with each project would have been merged during compilation. For more information see Define the Languages Supported by a Project.

Your project refers to a language that is not specified in the LANG.dbf file. You need to define the language in your project (see Define the Languages Supported by a Project).

A file that is referred to in your project includes an extension type that is not recognized by Citect SCADA. Firstly check that the file extension is correct in the point of reference. If it is, it means the file type is not supported; you should remove the reference.

Your project refers to a language that is not supported by Citect SCADA by default. You should use a supported language instead, or add support for the language to your project (see Define an Unsupported Language).

The compiler has detected that incorrect syntax has been used to mark some text for translation. Review the syntax used and make any required changes. For more information on correct syntax for marking translation text, see Mark Text for Translation and/or Mark Alarm Text for Translation.

A language that has been defined in your project is not recognized by the compiler. Check the Languages Properties settings (see Define the Languages Supported by a Project).

A system parameter setting in the project database has also been detected in an included project. It is recommended you remove any duplicated system parameter settings from the included project(s).

The compiler has detected that an address has not been specified for an I/O device that is configured to use the EWSCLIENT protocol. Add an address to this device.

"Allow RPC" on the Role form determines if a user or group of users can perform remote MsgRPC or ServerRPC calls. When upgrading projects this field is left blank which will raise the compiler warning message.

To ensure existing users can continue to use MsgRPC and ServerRPC, you need to manually change the value of "Allow RPC" to TRUE.

If these functions are used in your project, the roles that execute the functions will also need to have the permissions enabled.

The From Offset and To Offset values specified for the polyline vertex are the same; therefore, the length of the vertex path is zero.

A transparency setting is applied to a color that has been specified for an Alarm Priority display property. Transparency is not supported for Alarm Priority color settings.

“Manager User” on the Role form determines if a user or group of users can update user security settings at runtime. When upgrading projects if this field is left blank, the compiler warning message is displayed.