Error Messages
- Last UpdatedJan 20, 2026
- 13 minute read
This appendix lists Isodraft error messages that may be output to the screen and message file.
-
Messages generated by Isodraft itself have message numbers beginning with 33.
-
Messages generated by the ISODRAW module within Isodraft have message numbers beginning with 35. In most cases these will arise only when the program limits have been reached, and you should contact the AVEVA Customer Services Team.
Any other messages that may be output are not described here as they are not specific to Isodraft.
Note:
Many of the messages you will see when using Isodraft result from design or cataloguing errors, not from errors in using Isodraft. For this reason a data consistency check is strongly advised before Isodraft is used.
The error messages can include variables, presented in this appendix as follows:
|
integer |
an integer |
|
|---|---|---|
|
realno |
a real (that means, non-integer) number |
|
|
name |
an item name (general context) |
|
|
name/refno |
a name of an item (or refno if unnamed) |
|
|
filename |
an Marine filename |
|
|
text |
an alphanumeric character string |
|
|
(33:1) |
Paper size A4 to A0 only allowed See the SIZE command. |
|
|
(33:2) |
ISO 1,2,3,4 only allowed See the ISO command. |
|
|
(33:3) |
AREA must be between 1 & 10 See the WASTAGE AREA command. |
|
|
(33:110) |
BAD RETURN FILE The list of pipes successfully detailed by ISODRAW cannot be read. |
|
|
(33:114) |
VALUE MUST BE BETWEEN 1 AND 25 The maximum number of lines permitted in the title block area is 25. |
|
|
(33:116) |
VALUE MUST BE BETWEEN 201 AND 500 The Atext numbers of texts which can be changed by the ATEXT command must be within the specified range. See Recommendations for Importing DXF files from Isodraft into MicroStation for further information on Atexts |
|
|
(33:121) |
PAPER LENGTH must be greater than ZERO This is self-explanatory. |
|
|
(33:123) |
SPEC REF name gives material code ( text ) longer than max of integer characters The itemcode derived from the component’s name is longer than the width allowed in the itemcode column in the material list (see the ITEMCODE command). |
|
|
(33:124) |
VALUE between 1 & 20 only The identifying number allocated in a KEYS command must be within the specified range. |
|
|
(33:147) |
INST name/refno is not named Itemcodes for instruments are currently defined as Marine names (probably by default) and an instrument has been found without a name. |
|
|
(33:149) |
SYSTEM ERROR Unable to scan pipe network Check data consistency report and flow directions at branch connections. There is a design inconsistency which prevents Isodraft from detailing the specified pipeline. Run a data consistency check to find probable sources of error. In some cases this error may be produced by a configuration which is legal but which cannot currently be scanned by Isodraft. This problem can usually be resolved by splitting the pipe into more branches. |
|
|
(33:150) |
BAD NAME/REF A name or reference specified for detailing cannot be accessed. |
|
|
(33:151) |
Too many items in DETAIL list The Detail list cannot contain more than 100 items. |
|
|
(33:152) |
Can’t remove NAME/REF A name or reference specified in a Remove list cannot be accessed. In particular, note that World must not occur in a Remove list. |
|
|
(33:153) |
Too many items in REMOVE list The Remove list cannot contain more than 100 items. |
|
|
(33:155) |
The DETAIL list is empty Either there are no items in the Add list or the items specified in the Remove list have completely cancelled out those specified in the Add list, leaving nothing to be detailed. |
|
|
(33:156) |
PLOT FILE NAME/PREFIX or TERM have not been specified The output destination (terminal or named file) must be specified before Isodraft can detail anything. |
|
|
(33:157) |
NO PIPES HAVE BEEN PROCESSED SUCCESSFULLY Isodraft has failed to detail any pipes. The reasons may be suggested by other error messages generated during the detailing processes |
|
|
(33:158) |
MORE THAN 100 BRANCHES IN PIPE name/refno Isodraft cannot cope with more than 100 branches in one pipeline. |
|
|
(33:159) |
NO BRANCHES IN PIPE name/refno This is self-explanatory. |
|
|
(33:160) |
name/refno will not be detailed The specified Pipe or Branch cannot be detailed by Isodraft. The reason may be found in another message or a data consistency report. |
|
|
(33:162) |
HEAD & TAIL refs of BRANCH name/refno refer to the same component but head & tail positions are not close enough to that component There is an error in the identified branch, which has both ends connected to the component. This should not normally occur. |
|
|
(33:163) |
HEAD & TAIL refs of BRANCH name/refno refer to the same component and head & tail positions are the same There is an error in the identified branch, which has both ends connected to the component. This should not normally occur. |
|
|
(33:164) |
Component name/refno refers to a BRANCH ( name/refno ) which does not refer back to it There is an inconsistency between the connection attribute of the component and the branch to which it refers. For example:
|
|
|
(33:165) |
The HEAD of name/refno is connected to name/refno but the positions are not the same |
|
|
(33:166) |
The TAIL of name/refno is connected to name/refno but the positions are not the same There is an inconsistency between the HPOS or TPOS attribute of the branch and the p-point of the component to which it should be attached. |
|
|
(33:167) |
ELEMENT name/refno is not a piping component An element found while detailing a pipe is not of an appropriate type. |
|
|
(33:168) |
Cannot find FLANGE to match PPOINT integer of name/refno The connection reference on the given p-point needs to be accessed to determine the bolting requirements. This message means either that the connection reference is unset or invalid, or that a component of type FLAN cannot be found on that connection |
|
|
(33:169) |
Cannot find end of WAFER at name/refno The other end of the wafer fitting at the specified location cannot be found. Connection types commencing with W must be used in pairs. |
|
|
(33:170) |
BOLTING BRANCH Table full |
|
|
(33:171) |
BOLTING MULTIWAY COMPONENT Table full These tables keep account of those items which have already been accessed for bolting requirements. The limits are 100 items in the Branch Table and 200 items in the Multiway Component Table. |
|
|
(33:172) |
No non-standard BOLT lengths for SBOLT name/refno LENGTH is realno |
|
|
(33:173) |
No long enough non-standard BOLT lengths for name/refno |
|
|
(33:174) |
No SPCOM for name/refno The item specified has no component specification from which bolting requirements (the BLTREF attribute) can be derived. See Cataloging Requirements. |
|
|
(33:175) |
No BOLTS for SPCOM name/refno The SPCOM for the specified item does not have its BLTREF attribute set and so its bolting requirements cannot be determined. See Cataloging Requirements. |
|
|
(33:176) |
Invalid SPCOM name/refno for component, or tube connected to, name/refno A component, or the implied tube connected directly to it, does not have a valid specification reference (SPRE or LSTU). Check the data consistency report. |
|
|
(33:177) |
Cannot get DETAIL info. on SPCOM name/refno |
|
|
(33:178) |
Cannot get MATXT info. on SPCOM name/refno These indicate possible cataloguing errors. The SPCOMs specified do not have the appropriate attributes set for the data needed by Isodraft. See Cataloging Requirements. |
|
|
(33:179) |
Reference datum name/refno is unnamed No text will be shown for the reference dimension on the isometric. |
|
|
(33:180) |
PWAST attribute from SPCOM name/refno out of range 0.00 - 100.0 The wastage allowance attribute must be set to a percentage figure between 0 and 100%. See the WASTAGE AREA command. |
|
|
(33:181) |
BOLT TABLE FULL The number of different bolts which can be processed in a single pipe is limited to 1000. |
|
|
(33:182) |
name/refno connected to name/refno but not the other way round |
|
|
(33:183) |
name/refno not close enough to name/refno |
|
|
(33:184) |
ARRIVE or LEAVE PPOINT greater than 4 Isodraft can only deal with 4-way components whose arrive or leave ppoints are not greater than 4. |
|
|
(33:185) |
Multi-way component name/refno is not connected where expected |
|
|
(33:187) |
Both legs of name/refno refer to the same BRANCH but positions are not the same. |
|
|
(33:188) |
Both legs of name/refno refer to the same BRANCH and positions are the same. |
|
|
(33:189) |
One leg of name/refno is connected to name/refno but the positions are not the same. Errors (33:182) to (33:189) all indicate possible errors in the Design databases. Check the data consistency report and correct errors using an Design module. |
|
|
(33:190) |
CANNOT OPEN OPTIONS WORK FILE : ERROR integer |
|
|
(33:191) |
CANNOT OPEN MESSAGE FILE : ERROR integer |
|
|
(33:192) |
OPTIONS STATE IS LOST OPTIONS RESTORED TO DEFAULTS These indicate system filing errors, possibly due to a disc overflow. In most cases further explanatory messages will be output. |
|
|
(33:193) |
MESSAGE FILE NOT SET A file for output messages must be specified before Isodraft can begin any detailing. See the MESSAGEFILENAME command. |
|
|
(33:195) |
BRANCH name/refno is not in the network A pipe must have all its branches connected to each other in order to be detailed. The branch specified does not appear to be connected in this way. |
|
|
(33:196) |
name/refno has already been detailed The Pipe or Branch specified has its Detail Flag set to TRUE. It may be detailed by using the MARK IGNORE ON option, or by resetting the DETA attribute to FALSE in an Design module. |
|
|
(33:197) |
SYSTEM WARNING - MATERIAL NAME TABLE OVERFLOW - MAX integer NAMES This could occur on isometrics which incorporate a very large number of different items. It could result in items with the same itemcodes, but with different suffixes, being treated as different items. |
|
|
(33:198) |
ATTACHMENT POINT name/refno HAS NO STEXT An ATTA being used as a comment (ATTY set to CCCC or CCNN) has no text stored in its STEXT attribute. |
|
|
(33:199) |
ERROR IN DETERMINING BOLTING FOR name/refno See BOLTING for information on the cataloguing requirements for bolts. |
|
|
(33:200) |
Unable to access PIPE SPEC name/refno A pipe specification referenced by a pipe specified in a detailing command is not accessible in the current MDB. |
|
|
(33:203) |
BAD CONNECTION TO name/refno This suggests a possible error in the HREF or TREF of a branch. Check the data consistency report and rectify errors using an Design module. |
|
|
(33:252) |
Unable to locate text text within itemcode The locating text specified in a BOLT LENGTH ITEM INSERT AT ‘text’ command (see the BOLTING command) cannot be found in the itemcode for a bolt. Isodraft will use the default format for this bolt in the itemcode list and outputs this message for information only. |
|
|
(33:267) |
name/refno - Illegal or Inaccessible Reference Datum point The reference dimension is pointing to an incorrect or non-existent element. |
|
|
(33:268) |
Reference datum name/refno - Orientation has been modified to prevent Doubleback Dimension error The reference dimension requested for a Structure is parallel to the centreline. A reasonable orientation has been chosen instead. |
|
|
(33:269) |
Dimension omitted for Reference datum name/refno - Doubleback Dimension The reference dimension requested for a Piping component or Section is parallel to the centreline. |
|
|
(33:299) |
Illegal scale factor found for line flow arrow - default scale 8 used The scale factor for in-line flow arrows must be in the range 5 to 15 inclusive. |
|
|
(33:331) |
Illegal HREF connection on BRAN name/refno |
|
|
(33:332) |
Illegal TREF connection on BRAN name/refno The Head or Tail Reference of the Branch being detailed is invalid. It may have been deleted, or it may be in a DB which is not current in the MDB. |
|
|
(33:338) |
User defined symbol library has not been specified You have tried to define a symbol without first specifying a symbol library file in which to store the definition. See Isodraft User Guide, Chapter 11, Symbol Keys. |
|
|
(33:340) |
Limit of integer user defined symbols exceeded |
|
|
(33:341) |
Symbol key text rejected You have tried to define more symbols than the current maximum limit of 300. The specified symbol will not be added to the symbol library. See Isodraft User Guide, Chapter 11, Symbol Keys. |
|
|
(33:343) |
Error in updating symbol library An existing symbol file cannot be overwritten. Check that you have sufficient access rights. |
|
|
(33:345) |
Unable to create new symbol library text A new symbol file cannot be created. Check that you have sufficient access rights. |
|
|
(33:346) |
Error reading symbol library text An existing symbol file cannot be read. Check that you have sufficient access rights. |
|
|
(33:347) |
Unable to locate key text in symbol library The specified SKEY cannot be found in the current symbol library. |
|
|
(33:348) |
Row number integer is outside the range 1-999 |
|
|
(33:349) |
Table number integer is outside the range 1-999 You have exceeded the limits of table definition for user-positioned text. See the ATEXT command. |
|
|
(33:350) |
Limit of integer user positional text records exceeded You have tried to position more than the current maximum limit of 400 text fields. See the ATEXT command. |
|
|
(33:351) |
Character size integer exceeds maximum limit of 99 You have specified a character height greater than the maximum limit of 99mm. See the ATEXT command. |
|
|
(33:361) |
Option number integer is outside the allowed range 1-140 Debug options must lie within the range 1-140. |
|
|
(33:363) |
Balloon size integer is outside the allowed range 1-5 You have specified an instrument balloon size outside the permitted range of 1-5 character widths. |
|
|
(33:365) |
The no of components :- integer is outside the allowed range 1-50 You may only turn off fallskew boxes for lengths of pipeline which contain no more than 50 components. See the FALLSKEWS command. |
|
|
(33:368) |
SPOOLNumbers must be positioned with table parameters User-positioned text for spool numbers must include X and Y offsets within its definition to form a tabular layout. See the POSITION command. |
|
|
(33:386) |
Bend radius outside allowable range 0 to 50 D The permitted range for standard bend radii is 0-50 pipe diameters. |
|
|
(33:387) |
Illegal value for bend radius You can not specify a standard bend radius of less than 1mm. |
|
|
(33:399) |
Maximum of 20 nested PCOM tappings exceeded Tapping legs off PCOMs or SHUs can themselves contain PCOMs or SHUs with tapping legs, up to a maximum limit of 20 levels of nesting. |
|
|
(33:407) |
Cannot detail at branch level for system iso Detailing at Branch level is restricted to single pipe isometrics. System isometrics must include complete pipes. |
|
|
(33:408) |
Plottingscale limits (50-100%) exceeded - reset to 100 Note: Note: Note: |
|
|
(35:1001) |
OVER 200 ALTERNATIVE TEXT RECS FOLLOWING DATA IGNORED |
|
|
(35:1002) |
MORE THAN 200 TEXT RECORDS - DEFAULT TABLE USED The maximum number of non-standard text phrases which may be used at one time is 200 (see the ATEXT command). |
|
|
(35:1004) |
FITTING NOT FOUND - DEFAULT SHAPE USED A specified SKEY is not recognized. The relevant component will be indicated on the isometric drawing by the default rectangle symbol (see Isodraft User Guide, Chapter 11, Symbol Keys). |
|
|
(35:1006) to (35:1014) |
OVERFLOW IN DATA - PIPELINE REJECTED (message number depends on reason for overflow - see below) This is a fatal error; the isometric will not be plotted. |
|
|
(35:1006) |
PIPELINE MATERIAL DATA The maximum number is 100 |
|
|
(35:1007) |
TRANSFER FILE RECORDS The maximum number is 100000 |
|
|
(35:1008) |
PIPELINE MATERIAL DATA The maximum number is 100 |
|
|
(35:1009) |
NOMINAL SPLIT POINTS The maximum number is 500 |
|
|
(35:1010) |
BORE RECORDS The maximum number is 400 |
|
|
(35:1011) |
NUMBER OF CENTRE LINE SIZES The maximum number is 62 |
|
|
(35:1012) |
NUMBER OF BRANCHES The maximum number is 200 |
|
|
(35:1013) |
NUMBER OF SHEETS The maximum number is 200 |
|
|
(35:1014) |
OVERFLOW MATERIAL LIST The maximum number is 100 |
|
|
(35:1015) |
INVALID ITEM/DESCRIPTION POINTER |
|
|
(35:1016) |
ITEM CODE WIDTH ERROR - APPENDED TEXT LOST An itemcode contains more characters than the specified column width in the material list (see the ITEMCODE command). |
|
|
(35:1017) |
OVERFLOW IN DATA - CHECK DIMENSIONS |
|
|
(35:1018) |
NO FITTING DETAILS EXIST FOR FITTING CODE |
|
|
(35:1019) |
FITTINGS OVERLAP WHICH CANNOT BE CUT BACK |
|
|
(35:1020) |
INSUFFICIENT LENGTH ON OVERLAPPING FITTINGS TO ALLOW CUTBACK |
|
|
(35:1021) |
RUN ABORTED THE WIDTH OR HEIGHT (EXCLUDING BORDERS, MATERIAL LIST ETC) IS LESS THAN 50MM. THIS IS NOT ENOUGH ROOM FOR THE ISOMETRIC The layout specified for the drawing sheet does not leave enough room for the isometric drawing itself. The drawing will not therefore be plotted. See the FILE, SIZE and STACKINGARRANGEMENT commands. |
|
|
(35:1022) |
THE MATERIAL CODE IS TOO WIDE AND HAS BEEN CHANGED FROM ... TO ... |
|
|
(35:1023) |
THE TOTAL NUMBER OF ALLOWED CHARACTERS (3,900) IN FREE MESSAGES HAS BEEN EXCEEDED |
|
|
(35:1024) |
THE NUMBER OF FREE MESSAGES (50) HAS BEEN EXCEEDED |
|
|
(35:1025) |
THE NUMBER OF CHARACTERS IN MESSAGE EXCEED (300) THE (LAST) MESSAGE BEGAN WITH ... |
|
|
(35:1084) |
Warning - Support shape not found |
|
|
(35:1100) |
Error - Unable to position ref.dimension using coordinates given - Ref dimension record co-ords are val val val - Ref dimension not shown on drawing |
|
|
(35:1105) |
Warning - Reference Dimension key " " not found - Default line shown An invalid or blank SKEY has been used for a reference dimension. See Isodraft User Guide, Chapter 5, Design Requirements. |
|
|
(35:2001) |
DRAWING DELETED |
|
|
(35:2003) |
WELD NUMBERS HAVE CAUSED DATA OVERFLOW |
|
|
(35:2004) |
INPUT DATA OVERFLOW |
|
|
(35:2005) |
WARNING TEE OFF TEE >4 DEEP |
|
|
(35:2007) |
TEE IN SKEW |
|
|
(35:2008) |
DATA FAULT SKEW |
|
|
(35:2009) |
SKEW WITH NO CONTENTS |
|
|
(35:2010) |
FITTING WITH OFFSET NOT IN LINE WITH PIPE |
|
|
(35:2011) |
ANGLE FAIL |
|
|
(35:2012) |
DATA FAULT |
|
|
(35:2013) |
UP DOWN |
|
|
(35:2014) |
EAST WEST |
|
|
(35:2015) |
NORTH SOUTH |
|
|
(35:2016) |
DATA OVERFLOW, DRAWING REJECTED |
|
|
(35:2017) |
MESSAGE FAIL |
|
|
(35:2018) |
SHAPE FAIL |
|
|
(35:2020) |
TOO MANY COORDINATES IN FITTINGS |
|
|
(35:2021) |
TOO MANY FITTINGS |
|
|
(35:2023) |
WARNING, PAPER SIZE >A0 OR AD - THIS MAY PRODUCE UNACCEPTABLE RESULTS Isodraft does not recognize standard paper sizes larger than A0 or E. Larger sheet sizes can be specified by using the HEIGHT and WIDTH options. See the SIZE command. |
|
|
(35:2024) |
REJECTED, TOO MUCH DATA, TRY SMALLER SPLIT |
|
|
(35:2025) |
... CHECK |
|
|
(35:2026) |
... FAIL |
|
|
(35:2027) |
... PLOTTED |
|
|
(35:2028) |
... NOT PLOTTED |
|
|
(35:2029) |
... DRG. These are used in progress summaries in the message file. |
|
|
(35:2030) |
WARNING PLOTFILE NUMBER HAS REACHED 999 NEXT PLOTFILE WILL OVERWRITE ...001 PLOT file names are suffixed with a three-digit number to avoid ambiguity. This limits the number of different PLOT files with the same basic file name to 999. See the FILE command. |
|
|
(35:2031) |
THE FOLLOWING DRAWINGS ARE IN PLOTFILE ... |
|
|
(35:2035) |
READY FOR NEXT DRAWING. HIT RETURN TO GO This message appears on screen between plots when more than one drawing is to be output to a graphics terminal. |
|
|
(35:2036) |
THE FOLLOWING DRAWINGS WERE SENT TO THE TERMINAL |
|
|
(35:2037) |
ERROR OPENING UNDERLAY PLOTFILE |
|
|
(35:2038) |
ERROR READING PLOTFILE |
|
|
(35:2039) |
PLOTFILE INCOMPATIBLE PAPER SIZE |
|
|
(35:2040) |
BAD PLOT CODE - PLOTFILE PROBABLY CORRUPT |
|
|
(35:2041) |
THE SCHEMA PLOTFILE OPTION HAS BEEN SWITCHED OFF |
|
|
(35:2042) |
SPECIFIED PLOTFILE LENGTH ... |
|
|
(35:2043) |
... IS LESS THAN DRAWING LENGTH |
|
|
(35:2044) |
PLOTFILE LENGTH HAS BEEN INCREASED TO ... |
|
