SPECONMODE Error Messages
- Last UpdatedJan 13, 2023
- 6 minute read
The following is a list of those error messages specific to SPECON. All such error messages have a message number beginning with 17. Any other messages that may be output are not described here as they are not specific to SPECON.
Note:
Since some other modules access the Specifications directly during their normal functioning
(for example, to select insulation data) you may receive SPECON error messages while
working in those modules.
|
(17:2) |
Cannot access ID |
|
The element specified does not appear to exist in this DB. Check that you have entered the identifier correctly. |
|
|
(17:3) |
Cannot access SPECIFICATION |
|
Check that you have entered the identifier for the SPEC correctly. |
|
|
(17:4) |
Cannot create SPCOM or SELEC |
|
You can only add a new SPCOM line or SELEC question after you have created a new SPEC or have accessed an existing SPEC (refer to Creating a Specification to Entering Tabular Data). |
|
|
(17:5) |
Cannot create SPECIFICATION |
|
You can only create a new SPEC as a member of a Specification World (SPWLD) element in a Catalog DB. Check your current position in the hierarchy. (Refer to Structure of the Catalog Database and Content and Format of a Specification.) An accompanying message should give a fuller explanation. |
|
|
(17:6) |
CATREF already used in heading |
|
You have specified two CATREF pointers in a heading line. The second entry will be ignored, but should preferably be deleted. |
|
|
(17:7) |
Answers select previously defined spcom |
|
The combination of answers listed for this SPCOM line leads to an SPCOM which has already been defined. The second SPCOM line will, therefore, never be reached during the selection process. |
|
|
(17:9) |
DB unsuitable for SPEC |
|
You can only create a new SPEC as a member of a Specification World (SPWLD) element in a CATALOG DB (refer to Structure of the Catalog Database and Content and Format of a Specification). |
|
|
(17:10) |
DITTO IN FIRST LINE |
|
The ditto symbol (+) means ‘repeat the corresponding entry in the preceding line’ and is therefore only valid in the second or subsequent lines of the table. |
|
|
(17:11) |
No SPECIFICATION defined |
|
You must have created a new SPEC or accessed an existing SPEC before you can add to, modify, or output any tabulated Specification data (refer to Manipulating the Catalog Database using SPECONMODE). |
|
|
(17:12) |
ID name/refno does not correspond to column heading |
|
An element identifier in an SPCOM line must correspond to a relevant Reference Pointer in the heading line. It cannot be given as an answer under a SELEC question in the heading (refer to How Component Selection Works). |
|
|
(17:13) |
ID is not a SPEC |
|
The identifier given in an OUTPUT command must refer to an accessible SPEC (refer to Outputting a Specification). Check that you have entered the identifier correctly. |
|
|
(17:14) |
Too many headings for output |
|
You cannot output more than 20 headings in a table. |
|
|
(17:15) |
More answers than questions - extra answers ignored |
|
You have more entries in an SPCOM answer line than you have corresponding entries in the heading line. Check for unintentional spaces. |
|
|
(17:16) |
More defaults than questions - extra defaults ignored |
|
You have more entries in the defaults line than you have corresponding entries in the heading line. |
|
|
(17:17) |
More than 20 HEADINGS |
|
The maximum number of entries permitted in a heading line is 20. |
|
|
(17:18) |
DETAIL already used in heading |
|
You have specified two DETAIL pointers in a heading line. The line will be ignored. |
|
|
(17:19) |
Name already defined. Name/refno will remain unnamed. |
|
The NAME specified for this SPCOM has already been used and so this second SPCOM line will have only its AVEVA E3D Design refno as its identifier. Redefine this line with a new NAME if required. |
|
|
(17:20) |
No. of QUESTIONS and ANSWERS do not match up |
|
If the answers in a given SPCOM line do not correspond in a relevant way with the SELEC questions in the heading then that SPCOM will be ignored. (Refer to the Note in Selector Answers for one possible cause of this problem.) |
|
|
(17:22) |
Reserve name /*LIMBOSPEC has been used - object with this name has been unnamed |
|
The Specification /*LIMBOSPEC is reserved for holding REMOVED SPCOMs (refer to Deleting or Removing a SPEC or SPCOM). You cannot use it for any other purpose. |
|
|
(17:23) |
SPCOM does not exist |
|
Check that you have entered the SPCOM identifier correctly when modifying an existing Specification. |
|
|
(17:24) |
SPEC does not exist |
|
Check that you have entered the SPEC identifier correctly. |
|
|
(17:26) |
This command only allowed in SPEC |
|
You can only use a DELETE or REMOVE command after you have accessed an appropriate SPEC (refer to Accessing an Existing Specification and Deleting or Removing a SPEC or SPCOM), otherwise SPECON does not know which Specification you are telling it to modify. |
|
|
(17:28) |
TYPE required as first answer |
|
When adding a new SPCOM you must enter its TYPE (an AVEVA E3D Design noun) before its NAME. You may only use the reverse order when referring to an existing SPCOM (refer to Entering Tabular Data). |
|
|
(17:29) |
Unable to create TEXT element |
|
You can only specify one string of descriptive text for each SPEC. |
|
|
(17:30) |
Unable to put CATREF |
|
You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. |
|
|
(17:33) |
Undefined name |
|
Check that you have entered the required identifier correctly. |
|
|
(17:34) |
SPEC or an offspring is locked. |
|
The SPEC is protected against modification. Use the UNLOCK command before trying to use any of the SPECON editing facilities. |
|
|
(17:35) |
SPEC is not empty |
|
When using the COPY command, the SPEC into which the copy is transferred (name1 in Copying a Specification) must be empty. You cannot concatenate SPECs with the COPY command. |
|
|
(17:36) |
ID must be SPCOM |
|
The REMOVE command can only be used to remove SPCOMs. You cannot remove an entire SPEC, although you may use the REMOVE ALL option to empty it of its contents (refer to Deleting or Removing a SPEC or SPCOM). |
|
|
(17:38) |
No databases to work from |
|
(17:39) |
No SPEC database |
|
The specified MDB does not contain an appropriate CATALOG DB in which SPECON can create SPECs. |
|
|
(17:40) |
TEXT longer than 50 characters |
|
The text associated with a SPEC cannot exceed 50 characters in length (refer to Creating a Specification). |
|
|
(17:41) |
Unable to put CMPREF |
|
You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. |
|
|
(17:42) |
Unable to put DETAIL |
|
You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. |
|
|
(17:43) |
Unable to put MATXT |
|
You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. |
|
|
(17:44) |
Unable to put BLTREF |
|
You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. |
|
|
(17:45) |
You may not delete /*LIMBOSPEC |
|
The SPEC named /*LIMBOSPEC, used to hold removed SPCOMs, is created automatically by AVEVA E3D Design and cannot be deleted, otherwise future REMOVE commands would not work (refer to Deleting or Removing a SPEC or SPCOM). |
|
|
(17:46) |
You cannot REMOVE SPEC - use REMOVE ALL |
|
The REMOVE command applies only to the contents of a SPEC. Use REMOVE ALL to empty the SPEC of all contents or DELETE SPEC specname to eliminate the complete SPEC. (Refer to Deleting or Removing a SPEC or SPCOM.) |
|
|
(17:47) |
You cannot REMOVE items from /*LIMBOSPEC |
|
The REMOVE command can only transfer SPCOMs to /*LIMBOSPEC. Only by re-entering an SPCOM under its existing name can it be transferred back from /*LIMBOSPEC into a user‑defined SPEC. (Refer to Deleting or Removing a SPEC or SPCOM.) |
|
|
(17:48) |
MATXT already used in heading |
|
You have specified two MATXT pointers in a heading line. The second entry will be ignored, but should preferably be deleted. |
|
|
(17:49) |
CMPREF already used in heading |
|
You have specified two CMPREF pointers in a heading line. The second entry will be ignored, but should preferably be deleted. |
|
|
(17:50) |
BLTREF already used in heading |
|
You have specified two BLTREF pointers in a heading line. The second entry will be ignored, but should preferably be deleted. |
|
|
(17:51) |
SPCON NAME name already exists |
|
You must use a unique name for each SPCON. The new SPCON will be rejected. |
|
|
(17:52) |
word is not valid as a GTYPE |
|
Refer to Applicability for examples of valid GTYPEs. |
|
|
(17:53) |
TMPR already used in heading |
|
You have specified two TMPR pointers in a heading line. The second entry will be ignored, but should preferably be deleted. |
|
|
(17:54) |
Unable to put TMPR |
|
You are unable to set this Reference Pointer to the element specified. Possibly you have specified it incorrectly. |
|