Missing M1 not defined [CHECK 267]

Missing M1 not defined [CHECK 267]

M1 display file graphic:302 not defined in testStack

This message means that the graphic indicated calls for another graphic, which was not found.

The usual sources of this error are:

  1. Failure to build all graphics in the DBDOC document. If the graphic is not built, the DBDOC process will not find it. This is normally the case when there are a lot of messages in this file.
  2. Graphics becoming obsolete and being eliminated, without correction of other graphics that call for the obsolete graphic.
  3. Graphics being planned and anticipated that have not yet been built or installed.
  4. Errors in pop-ups.

When there are a lot of these errors showing up, it normally means that all the graphics needed were not built, or the graphics are not used. It suggests that operator graphic keys and touchpoints may be "dead" because those graphics are not in the system. In Hyperview, go to "MISSING GRAPHICS / Index of Unconfigured Graphics" in the "System Information" Chapter to see where these graphics are referenced.

You can find where the graphic is linked using either the Audit Window or the Index of Unconfigured Graphics in the System Information chapter.

This message shows a potential error in the system configuration, although most such errors prove to be harmless. It should be reviewed and hidden, unless it shows an issue that should be addressed.

Please contact us for help resolving your error messages.