Messages in the Message Log

Text displayed in SML

Description when message is displayed

Severity

The attribute <AttName> does not exist in the current project.

Will be displayed each time when source application does not contain that kind of attribute. that means, MAR project has defined some UDA but SAM project does not have them. Because of that, these UDA's will not be set when copy-paste from MAR to SAM project.

Warning

The attribute <AttName> can not be updated because the element is not of type <TypeName> . Type of element is <TypeName>.

An example of this message can look like "The attribute HREF can not be set because element is not SCBRAN, SCSEG type. Type of element is SCCABLE".

This kind of messages should never be displayed, unless something changed in the database, for example if pasting copied data into older database versions. Message will be displayed only for referenced attributes that are responsible for connections (like CRFA, ECRFA but not SCLORE).

Warning

This is not a SCSEGMENT nor SCBRANCH and you are trying to set HREF. IsTypeValid() method failed!

System error message. This should not occur under normal circumstances.

Warning

This is not a SCSEGMENT nor SCBRANCH and you are trying to set TREF. IsTypeValid() method failed!

System error message. This should not occur under normal circumstances.

Warning

<AttName> of branch not set because the connected item does not exist.

Message when HREF or TREF cannot be set because item that was connected in source does not exist in destination. Typically, when a branch is connected to equipment but during copy user copied equipment and branch without tube that was connected to equipment (partial copy) system cannot set HREF/TREF because in destination branch is not connected to equipment (there is no tube).

Warning

<AttName> can not be set because the connected item was not copied. Missing: <missing part name/refnum>

HREF/TREF/STAREF/ENREF can not be set because the item that attribute points to was not copied.

Warning

<AttName> can not be set because connected item is not valid in database.

HREF/TREF/STAREF/ENREF can not be set because the item that attribute points to was copied but for some reason is not valid in DB (there supposed to be different message that explain why item is not valid).

Warning

<AttName> can not be changed because the database element that shape points to already has this attribute set. Database value is <name of element connected in db>, while the value in the drawing is <name of element connected on drawing>.

When copying a cable or multi cable the pasted item has been selected to be secondary. The existing primary item has STAREF/ENDREF already set.

Warning

The <AttName> has been updated according to drawing connection.

When copying a cable or multi cable the pasted item has been selected to be secondary. The existing primary item didn’t have STAREF/ENDREF already set. They have been updated according to the pasted item.

Information

<AttName> can not be set because this item is not connected with <element name> on the drawing

In case STAREF/ENDREF is not connected on drawing, this message will be displayed. Typically it might happen when equipment is connected with primary cable representation. The cable also has secondary shape representation that is not connected with the equipment. When copying and pasting equipment and secondary cable representation then it will not be possible to set the attribute because items are not connected on the drawing.

Warning

The nozzle does not have the required PIPE_1 connection point. CREF attribute is not set.

A nozzle shape was copied that was not properly defined on drawing. The connection point could not be found.

Warning

The connection between nozzle and branch can not be copied because the item is not connected to a valid branch!

This is displayed when the nozzle connection will not be connected in the destination but was in source. For example if an equipment and nozzle were copied without connected branch (or branch is connected but is not valid).

Warning

Could not copy <AttName> because there are no valid connections.

The message will be displayed when copying and pasting an item with CRFA/ECRFA set. For example, a valve in the source has CRFA set (meaning that the valve has a branching point connected to some branch) but was copied without connected branch.

Warning

One of the referenced <AttName> items can not be set. Item is not connected, missing element <name of missing element>

CRFA and ECRFA are arrays, it might be that a valve with two branching points connected is copied, for example a cross, but it was copied only with one branch. In the result in destination there will be a cross with only one branch connected.

Warning

The ECRFA maximum size was reached. Some items can not be connected.

The ECRFA size is constant. Some items like equipment might be a secondary. In case an equipment with connected branches is copied and chosen to be secondary during paste, then the ECRFA array will be extended with the new connections. It might be that this operation will cause too many connected branches – then this message is displayed.

Warning

The attribute <AttName> can not be set because the referenced element {1} does not exist in current MDB

Message will be displayed if referenced attribute is not valid in the destination project.

For example if copying an equipment that refers to some systems and pasting it to a project where one or more of these systems doesn’t exist.

Warning

OPCREF can not be set because of missing connected OPCI/O

Message displayed when OPCREF can not be set because connected OPCI/O was not copied.

Warning

OPCREF can not be set. The connected OPCI/O was copied but it is invalid

Message displayed when OPCREF can not be set because OPCI/O was copied but for some reason it is undefined. It might happen if creating a branch under existing pipelines and one of pipelines belong to database that is read only. Because of that, the item will be pasted but will be undefined.

Warning

Failed to copy SCIRTY because the SCIRTY table has different size than SCIREF table. All values have been set to NONE

In case if SCIRTY has different size than SCIREF then properly setting this array is not possible. Because of that SCIRTY will be reset. This should not normally happen, but it might be that attributes were changed outside of Diagrams or manually in PML.

Warning

The database does not contain UDET type <name of unknown udet>. The base type <name of element base type> will be used.

Displayed when copying a UDET and pasting it in a destination project where this UDET has no definition. In the result base type will be used.

Warning

The object type does not exist in db definition for <database element type name>, failed to create item.

Displayed when the database type of the copied item, that exists in source project does not exist in the destination project.

Warning

There is no schematic DB where the item can be created

The destination project doesn’t have any available Schematics database, or it is read-only.

Warning

Failed creating item because its owner was not created.

Items like Elconns or Nozzles are copied without their owning elements. This will result in the items becoming undefined.

Warning

Failed to get default group for {0} from CE. Item was not created.

Displayed when the Session Defaults option "Get Default Group from CE" is used, but the group could not be fetched. This can for example happen if the current element is the "World" element.

Warning

Failed to get default group for {0}. Item was not created!

Displayed when no default group for an element type is defined in Session Defaults.

Warning

Can not create item in database because the subequipment is copied without its owner. Either copy the subequipment separately and paste it with the parent equipment item as CE, or copy this item together with its equipment parent.

When user is coping sub-equipment items without its owner, it is possible that they will be created in db. However, there is restriction that CE has to be equipment (or one of the CE parent is an equipment) and only sub-equipment items were copied. In case mixed types are copied and sub-equipment items are copied without the parent, then this message will be displayed.

Warning

Can not create subequipment in database because CE is not an equipment. Please set CE to equipment or its member, or copy this item together with its equipment parent.

Displayed when sub-equipment items are copied but CE is not an equipment or an equipment member.

Warning

Some of the segments were copied partially, and the copied data structure was reorganized. When pasting, the newly created data structure will be different than the copied one

This message might be displayed during copy action when copying only a few items from branch. Example: There is a branch that contains tube1, valve1, tube2, valve2. If selecting valve1 and valve2 and executing copy/paste, then this message will be displayed because when paste, the structure has to be changed. Two branches have to be created instead of one. However, if selecting valve1, tube2 and valve2 the message will not be displayed because the branch structure will be the same.

Information

Name should not contain spaces. Evaluated name "<name>" contains spaces.

Error from auto naming. Displayed when auto name rule is wrongly set so that name contains spaces.

Warning

Name already exists.

Error from auto naming. Displayed when auto name rule creates name that already is in use.

Warning

The item was supposed to be copied but the DBElem is not valid!

Critical error that can appear when during paste action another thread/process change pasted database elements.

Critical

The shape can not be linked with database element.

Displayed if it is not possible to establish connection between database element and the shape.

Critical

The database attribute '<AttName>' is not valid for this element.

Displayed when an attribute is valid in the database but the element does not have this attribute. A typical case might be when some UDA is defined in both source and destination projects, but in project A this UDA is assigned to SCOINST and SCEQUI but in project B it is assigned to SCEQUI only. When copying SCOINST from project A where the UDA has value set and paste it to project B, it will not be able to set the attribute.

Warning

Paste action failed. Items might be defined incorrectly

Paste action failed. There is high probability that another error message precedes this message.

Critical

The auto naming of elements failed. Exception message

Auto naming failed. Probably some rules are incorrectly defined or some elements do not have all attributes set that naming rule requires.

Warning