Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Engineering

Error Messages

  • Last UpdatedJan 03, 2023
  • 2 minute read

The following is a complete list of those messages specific to the Monitor module that may be output to the terminal (with message number) and message file (with message number suppressed). All such messages will have a message number beginning with 39. Any other messages that may be output are not described here as they are not specific to the Monitor module.

(39,3)

MDB not found

The MDB name referred to does not exist in the current project.

(39,4)

DB not found

The DB name referred to does not exist in the current project.

(39,5)

TEAM not found

The team named does not exist in the current project.

(39,6)

Insufficient status to set this mode

User’s access rights do not allow him to modify the relevant files.

(39,7)

USER not found

The user named is not a member of the specified or current team.

(39,8)

MODULE not found

No runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.

(39,11)

DB not current

The DB specified in an EXCHANGE or DEFER command is not current within the MDB.

(39,12)

User number not found

No user is currently logged in under the specified id number.

(39,13)

Resume file not found

No runfile for the specified module can be found in the current Project Database. The runfile must be set by the System Administrator using Admin.

(39,14)

Insufficient status to run module

You do not have access rights to the specified module.

(39,15)

No MDB has been specified

An MDB must be selected before Monitor will transfer control to most other modules or before individual DBs can be made current.

(39,16)

DB is not part of this MDB

The DB referred to is not within the specified MDB, or within the current MDB if none was specified.

(39,17)

DB already current

.

The DB specified in a CURRENT or EXCHANGE command is already current within the MDB.

(39,18)

Filing error - cannot delete macro file

The macro identification number given in a DELETE MACRO command is not valid.

(39,19)

Cannot delete - macro not yet read

The DELETE MACRO command cannot be used until the inter-DB connection macro specified has been read by the recipient team.

(39,20)

Current position out of range

The list position for adding a current DB to an MDB must be in the range 1 to 1000.

(39,21)

There are already 1000 current DBs

A maximum of 1000 DBs are accessible within an MDB at any time. Use the EXCHANGE command to substitute the required DB for one not currently needed.

(39,22)

Actions turned off

The ACTIONS OFF command has been issued.

(39,23)

BATCH command ignored for interactive use

The BATCH command is only valid if entry was made using the batch option.

(39,25)

/* is not a valid MDB

The MDB must be fully specified by name; wildcard characters are not allowed in this context.

(39,36)

User password not changed - passwordLock is on. Please contact the system administrator at location =0/0 to change passwords.

Your Administrator has set the PASSWORDLOCK ON. You may not reset your password in Monitor.

Related Links
TitleResults for “How to create a CRG?”Also Available in