Error and warning messages

The messages are listed as the English interface shows them. {0} and similar marks stand for a value that the message fills in, for example a number of minutes. For the reasons shown after Command rejected, see Command reason codes.

Sign-in and session

Message	Meaning	What to do
Invalid username or password	The user name or the password is wrong, or the user is disabled. Each wrong password counts as a failed attempt.	Check the user name, the password and Caps Lock.
Too many failed attempts. Account locked.	This attempt reached the number of failed attempts set in the lockout policy (5 by default).	Wait, or ask the system administrator (root) to unlock the account. See Password and lockout policy.
Account locked. Try again in {0} minutes.	The account is locked (15 minutes by default).	Wait the stated time, or ask the system administrator (root).
The system use notice must be accepted	The project shows a system use notice before sign-in.	Accept the notice and sign in again.
Authentication is disabled for this project	The project does not use user login.	Nothing; the project needs no sign-in.
Session idle with The session of {0} will close due to inactivity.	The session has had no activity for the idle time (30 minutes by default); a countdown runs.	Click Stay logged in. See Sessions.
Session expired — pending changes are kept; sign in again and retry	In the configuration editor, the session ended while you had changes that were not applied.	Sign in again; the changes are still there.
Session invalid or expired; sign in again	The configuration editor could not use the session.	Sign in again.
Sign-in required: sign in to perform this action.	The action needs a signed-in user.	Sign in.
This server requires a session — sign in.	The runtime screen cannot receive live values without a session.	Sign in.

Permissions and administrators

Message	Meaning	What to do
You are not allowed to do this	Your profile does not have the permission for this action.	Ask the system administrator (root) for the permission. See Permissions and default profiles.
You do not have access to this page.	Your profile may not open this page.	Ask your project engineer. See Page access.
This action requires server administrator rights; sign in with a server administrator account.	The action belongs to the whole server, for example creating a project.	Sign in as root.
This action requires root (system administrator) sign-in.	A design or server action on the home page, for example creating, importing or backing up a project, needs root.	Sign in as root in the window that follows. See Root, the system administrator.
Sign in as root for this operation.	The sign-in window for a root action, with root in Username.	Enter the root password.
This action requires a server account; sign in as the server administrator	A project user tried a server action. Project accounts cannot do server actions.	Sign in as root. See Root, the system administrator.
Default root password (root / root) is in use	Yellow band: root is signed in with the default password. It cannot be closed.	On the home page, click Change password in the band. See Change the root password.
The root password does not meet the security rule	Yellow band: the root password is shorter than 12 characters or lacks an uppercase letter, a lowercase letter or a digit.	Change the password with Strong password required selected.
The current password is wrong	In Change root password, the current password is wrong. It counts as a failed sign-in.	Type the current root password again.
Password changed; sign in with the new password.	The root password was changed and every root session was closed.	Sign in as root with the new password.
The server is already configured	The first-run setup was already completed, for example in another browser.	YTCC opens the home page after a few seconds. Sign in there as root.
The agreement text changed; read and accept it again	The licence text on the server changed while the setup was open.	Reload the page and accept the agreement again.
The last server administrator cannot be removed; add another administrator first	The list of server administrators of earlier versions must keep one entry. With the root account the list decides nothing.	Leave the list as it is. See Root, the system administrator.
No server administrator is defined	The server has no root account and no valid entry in the list of server administrators of earlier versions, so server actions are blocked.	Create the root account with scada-manager server-user reset; see Recover the root account.
The last active user with user management permission cannot be removed; define another administrator first	The project must keep one active user who can manage users.	Give another user this permission first.
Authentication cannot be enabled: no active user with user management permission	User login cannot be turned on without a user who can manage users.	Create such a user first. See Turn on authentication.

Starting a project

Message	Meaning	What to do
Project is running in another version with {0} is running in {1} ({2}, pid {3}, since {4}). The same project cannot run in two versions at the same time.	Another YTCC installation on this computer runs the project.	Stop it there, or use Stop it there and start here…. See Start, stop and restart a project.
{0} is running in an older YTCC installation; stop it there first.	An older installation runs the project.	Stop the project in that installation.
{0} did not stop in time; the project was not started here. Close the project there, then try again.	The other installation did not stop the project when asked.	Stop it there, then start it again here.
The project is running on another computer and cannot be terminated from here. Stop it there first.	The project is held by another computer.	Stop it on that computer.
Waiting for the previous version to stop; the project will start by itself within {0} s.	The other installation is stopping the project.	Wait.
Starting and stopping the project requires the configuration editing permission in this project.	Your profile cannot start or stop the project.	Ask the system administrator (root) for System stop, or sign in as root.
The project is not running; sign in as a real user to start it.	A monitoring-only sign-in cannot start a project.	Sign in with a user account.
Drivers could not be started	The project database and the YTCC programs have different schema versions, so the project did not start.	See When a database does not match the programs.
Could not connect to the database server; the project database cannot be changed safely.	PostgreSQL is not running or cannot be reached.	Start the PostgreSQL service or check the connection. See Databases and schema upgrade.
This port is in use on this computer	During the first setup, the chosen port is already used by another program.	Choose another port.

Versions and formats

Message	Meaning	What to do
Project database is incompatible with this version	The configuration editor does not open the project because its database has another schema version.	Read the line below the title.
This project database (version {db}) is older than this program (version {bin}). The editor does not upgrade the database on its own.	The database must be upgraded. The window shows the command to run.	Stop the stack and run the command shown. See Upgrade to a new version and roll back.
This project database (version {db}) is newer than this program (version {bin}); update all YTCC programs together.	A newer YTCC has upgraded the database.	Use the newer YTCC version.
The project database is older than this version (database {0}, expected {1}). Right-click the project and choose "Upgrade…"; a backup is taken first.	The home page could not run the project action because the database has an older schema. When you start the project, the upgrade window opens instead.	Stop the project, right-click it and choose Upgrade…. See Upgrade a project from the home page.
The project database is newer than this version (database {0}, this version {1}). Install the YTCC version that saved the project, or a newer one.	A newer YTCC has upgraded the database; this version does not start the project.	Install the version named in Saved with, or a newer one.
This project was saved with a newer YTCC version; update to open it	The project files are in a format this version cannot read.	Open the project with the newer version.
This project was saved with a newer YTCC version; update to save it	This version can read the project but may not save it.	Save it with the newer version.
This page was saved with a newer YTCC version and is read-only here. Update YTCC to edit it.	One page is in a newer format. It opens read-only.	Edit it with the newer version.
The package was made with a newer YTCC version than this server; update YTCC first	A project package comes from a newer version.	Update YTCC on this server first.

For the version numbers behind these messages, see Compatibility and contract versions.

Runtime screen

Message	Meaning	What to do
No server connection — data is not up to date (last update {time}). Reconnecting…	The browser has lost the connection to the server. The values on screen are old. The banner is large and flashes.	Wait; check the network if it lasts. See When the connection is lost.
Connected — refreshing data…	The connection is back.	Nothing.
{0} signals cannot be shown (server subscription limit ws_max_subscriptions).	The screen asks for more live signals than the server allows for one connection.	Ask your project engineer. See Limits and capacities.
The browser blocks sound until the page is clicked	The alarm horn cannot sound yet.	Click anywhere on the page once. See Silence the alarm horn.

Licence

Message	Meaning	What to do
Unlicensed use — licence required: {0} CU	Usage is above 80 CU and there is no valid licence. The system runs fully.	Download a request file and order a licence. See Licence and Capacity Unit.
{0} CU overrun — the system keeps running; buy additional CU.	Usage is above the licensed CU.	Order additional CU and load the new licence file.
Unverified licence — the machine identity does not match the licence. Re-activate within {0}.	The server's identity changed. The system runs fully.	Send a new request file and load the new licence. See Machine identity.
Unlicensed use has exceeded 90 days — design changes cannot be saved. Licence required: {0} CU.	The design lock is active. Saving and applying are refused; the running system is not affected.	Load a licence file, or get usage down to 80 CU or less. See Design lock.
Sign in as a server administrator.	The licence actions need a server administrator session.	Click Sign in.
Sign in as a server administrator to see the processes.	The Processes tab needs a server administrator session.	Click Sign in.

The other licence file messages are in Licence and Capacity Unit.

Screen editor

Message	Meaning	What to do
Unsaved Changes with This project has unsaved changes. They will be lost if you leave.	You are leaving the editor with changes that are not saved.	Save first, or confirm that the changes are discarded.
This tab has unsaved changes.	You are closing a tab with changes that are not saved.	Save or discard.
Save Conflict with This project changed on the server while you were editing. Your changes were not saved.	Someone else saved the same project while you were editing.	Choose Take server version or Keep mine. See Undo, save and restore.
{0} changed '{1}'. You have unsaved changes here.	Another user changed an item you are also editing.	Check the change before you save.
This name is already in use.	Another page, symbol, popup or layout has this name.	Choose another name.

Configuration editor

Message	Meaning	What to do
Apply (fix errors first)	Validation found errors; changes with errors cannot be applied.	Fix the listed errors. See Validate, apply and restore.
Apply with warnings	Validation found only warnings.	Check the warnings; you can apply.
A signal named {name} already exists	Signal names are unique in a project.	Choose another name.

Importing a project

These messages appear in the Import project window, which opens with Import on the Projects tab of the home page.

Message	Meaning	What to do
This name is already used on this server	A project with this name exists.	Choose another name, or overwrite the project.
The project is running: it must be stopped to overwrite it (the site cannot be monitored meanwhile)	A running project cannot be overwritten.	Confirm that the project is stopped.
Another import is in progress; try again when it finishes	Only one import runs at a time.	Wait and try again.
Uploaded package not found (it may have expired); drag it again	The uploaded file is no longer on the server.	Drag the package in again.
The file is not a .zip package / The package has no manifest.json — not a YTCC project package	The file is not a YTCC project package.	Use a project backup or package made with YTCC. See Backup and restore.