Business Application Modeling error messages

A list of BAM error messages. For messages that are not self-explanatory, additional information is provided.

Table 1. Business Application Modeling Error Messages
Number Description
GS-13001 Cannot load file.

The file cannot be loaded; depending on the error, the message can change:

  • Unknown node: an unknown node is present in the settings file
  • Cannot register node: a node cannot be added to the file format (it's invalid or already present)
  • Empty extension: a required file extension is empty.

Check file path, format, and permissions.
GS-13002 Cannot save file.

Check file path, format, and permissions.
GS-13003 Template not found.

Check template directory path.
GS-13004 Unknown item 'item'.

The setting.agconf template file format is incorrect. Validate it using the XML schema (or open it in Code Editor) and fix the errors.
GS-13005 Missing version in settings.agconf

The settings.agconf file version attribute is not present.

Add a version attribute corresponding to the product.
GS-13006 settings.agconf version 'version A' is not supported, use version 'version B'.

Modify setting.agconf to match version 2 XML schema.
GS-13007

'value' BLOCK(S) or POINT(S) end tag is(are) missing.

Fix the BLOCK / POINT. For further information, see Using POINTs and BLOCKs.

GS-13008

Incorrect end BLOCK or POINT tag type.

Fix the BLOCK / POINT. For further information, see Using POINTs and BLOCKs.

GS-13009

End BLOCK or POINT tag does not correspond to an open tag.

Fix the BLOCK / POINT. For further information, see Using POINTs and BLOCKs.

GS-13010 'value A''BLOCK/POINT' with name 'name' is already defined.

Rename the BLOCK / POINT.
GS-13011 A BLOCK or POINT cannot be a child of a POINT tag.

Rename the BLOCK / POINT.
GS-13012 Renamed 'value A': 'value B' to 'value C'.

Preprocessor message that a BLOCK / POINT has been renamed:

value A = BLOCK or POINT

value B = old BLOCK / POINT name

value C = new BLOCK / POINT name
GS-13013 Lost 'value A': 'value B'.

'value A' = BLOCK or POINT

'value B' = BLOCK / POINT name
GS-13014 Adding entries outside BLOCK or POINT not allowed.

Add a BLOCK / POINT in the templates or remove your code.
GS-13015 $(agcomp) is deprecated, please prefer using $(generate), tclsh and $(blockpoint) commands.

Modify the build rule to use the new commands.
GS-13016 Modified 'value A': 'value B'.

'value A' = BLOCK or POINT

'value B' = BLOCK / POINT name
GS-13017 Unknown property.

An unknown property has been set in the settings file. Remove the property or change its name.
GS-13019 Cannot open file : extraction load failed.

Check the rights on the generated source file.
GS-13020 Cannot open file : injection save failed.

Check the rights on the generated source file.
GS-13021 Cannot open file : update load failed.

Check the rights on the generated source file.
GS-13022 Cannot open file : update save failed.

Check the rights on the code file.
GS-13023 Code file load failed.

Check the rights on the code file or check that the code file contains valid XML content.
GS-13024 Unknown argument 'argument name' to Application Generator Block & Point task.

The command $(blockpoint) contains an unknown argument in the build rule. Check the argument 'argument name' of $(blockpoint) command in the build rule.
GS-13025 Missing -depth int argument to Application Generator compilation task.

The Application Generator build rule requires the -depth argument in the $generate command. Add the -depth argument to the $(generate) command in Application Generator build rules.  

GS-13026 Invalid -depth argument for Application Generator compilation task, required positive integer or 'unlimited'.The $(generate) command requires a positive number (or keyword unlimited). Fix the argument in the build rule command.
GS-13027 Unknown argument 'argument name' to Application Generator compilation task.

Command or tclsh or $(agcomp) contains an unknown argument in the build rule. Check the argument 'argument name' of $(generate) or tclsh or $(agcomp) command in the build rules.
GS-13028 Invalid -endComment string argument, it cannot be used without -startComment string argument.

The command $(blockpoint) contains an -endComment argument without -startComment argument in the build rules. Remove the -endComment argument or add a -startComment argument in the build rule.  

GS-13029 Error decoding 'value A' using codec 'value B' (encoding='value C')

The file contents cannot be decoded with the codec, the encoding specified in the environment does not correspond to the file and it cannot be read. Change the encoding so that it supports all the file characters.
GS-13030 Error encoding 'value A' using codec 'value B' (encoding='value C')

The file contents cannot be encoded with the codec, the encoding specified in the environment does not correspond to the file and it cannot be written to. Change the encoding so that it supports all the file characters.
GS-13031 Missing codec for encoding 'value'

There is no default text codec for the specified encoding. Use another alias for this encoding, update encodingMap.xml, or add a new POSIX charmap. For further details, go to Language support (text encoding).
GS-13032 Malformed BLOCK/POINT start tag

The BLOCK/POINT start tag has a wrong syntax. Restore the right syntax. For further information, seeUsing POINTs and BLOCKs.
GS-13033 Unexpected characters outside text blocks : 'character'

Some characters have changed outside the topmost block, which is not supported. Insert a new toplevel block around the code you want to modify and regenerate the code.
GS-13034 Missing argument -code in the $(BlockPoint) command

The $(BlockPoint) command is used with multiple generated files, the -code argument is mandatory. Add the -code argument.
GS-13035 Missing files in the $(BlockPoint) command

The $(BlockPoint) command is used without generated files arguments. Add the generated files list.
GS-13036 'value' contains code not managed in the $(BlockPoint) command

Some file managed by the .code were not updated by the $(BlockPoint) command, the .code is not completely up to date. Add the missing files to the command line in the build rule or remove the old file from the .code if they are no longer useful.
GS-13037 .code file version 'version' is not supported

The current version of Genero Studio does not support this version of .code file.

Upgrade Genero Studio.
GS-13038 .code file encoding 'value' differs with current one

The .code file encoding is not the same as the build encoding, the resulting files may be incorrect.

Change the build encoding (the LANG variable for example) to match the .code file encoding or rewrite the .code file with the current encoding.
GS-13039 Resolve conflict before compiling

The code file id does not match the source file id, thus a resulting conflict file. You must merge the differences manually. This may occur after updating from the SVN repository.

Merge the .conflict file and the source file, then delete the .conflict file.
GS-13040 Cannot write conflict file

The code file id does not match the source file id, thus a resulting conflict file which cannot be written to the disk.

Check the directory permissions.
GS-13041 Ignored unknown attribute 'attribute' on element 'element'

In the settings.agconf file, an attribute has been defined where it is not expected.

If the attribute is not required, remove it. If the attribute is required but has an error (a spelling error, for example), fix the error.
GS-13042 '-depth' argument of $(generate) command is deprecated, use 'depth' attribute on 'Item' elements in settings.agconf.

Some Business Application deprecated feature has been used.

Refer to the migration notes in the manual to update the project. In this example, modify the settings.agcong to add the depth, and edit the build rules to remove the depth.
GS-13043 Invalid Template directory 'directory'

The Business Application template directory setting is set incorrect.

Solution:
  • Remove the template directory setting if useless.
  • Change the path for a valid directory containing Business Application settings.
GS-13044 'value A' 'value B' index out of range ('value C') current index is 'value D'

Business Application build command $(BlockPoint) failed, there are inconsistencies between the source files and the code files. This error should not happen during normal operations, but may appear in case of errors during the process of migration between different versions.

If you receive this message, contact your local support center for help during the migration.
GS-13100 The 'Open Mode' property is not set.

The Open Mode property value is empty. The available values are: DISPLAY, MODIFY, ADD, SEARCH and EMPTY. Check settings.agconf and ensure that the initialValue attribute of the <DynamicProperty> node having name = "openMode" contains one of the available values.
GS-13101 The 'Action' property is mandatory.

The Action property is mandatory when a relation is defined between modules (4fdm to 4fdm) or between module and zoom (4fdm to 4fdz) and the relation type=Relation. Check that the Type property of the relation is Relation. Check that the Action property of the relation is not empty.
GS-13102 No report file is defined. Default layout will be used.

If the Report File property is empty, the default layout (ASCII mode) will be used when a relation is defined between a module and a report (4fdm to 4rd) and the relation type=ReportRelation. This is a warning message. Check that the Type property of the relation is ReportRelation. Check that the Report File property of the relation is not empty.
GS-13103 The 'Type' property of the relation is invalid.

The type of relation is not valid between entities: module (4fdm), program (4prg), zoom (4fdz), report (4rd). Check the Type property of the supported relation and ensure that the relation is supported.
GS-13104 The relation is not supported.

Check the entity relations.
GS-13105 Any relation to a program is not supported.

Check the entity relations.
GS-13106 The 'Report file' property contains an absolute path. Prefer a relative path.

Absolute paths are not recommended because the project will not be portable. Use a relative path. Be sure that your Genero environment variables are correctly set to search for your resource files.
GS-13107 A unique key field can only be defined on the master table.

All fields making up the unique key of a record must be fields of the master table of the record. Uncheck the Unique Key property of fields which are not of the master table of the record.
GS-13108 Duplicate table name in the FROM clause.

The joins between a pair of tables must have the same join operator. Check that there are not multiple join operators for the same pair of tables.
GS-13109 The field 'field' updated by an ascending lookup is mandatory in the record.

The field $1 that is updated via an ascending lookup is mandatory in the master table of the record, however currently the field is only defined in the Query clause of the record.

Add the field to the master table of the record. If you don't want to see this field on your form, use the phantom widget. Or, delete the lookup property of the field which triggers the ascending lookup.
GS-13110 Multiple master records are not supported. Define a relation between records.

When there are several records in a managed Form, only one can be the master. This error occurs when at least one record is not linked by a relation. In the Records view, check that all records are linked by a relation.
GS-13111 Invalid relation, primaryField and foreignField must have same number of fields.

A relation must have the same number of primary fields and foreign fields. Modify the relation fields so that a primary field corresponds to each foreign field.

GS-13112 The 'zoom' action in the Toolbar/Topmenu won't be generated, an action is already named 'zoom'.

Rename your action to a name other than zoom.
GS-13113 Several relations ('value A') use the same action name ('value B' - 'value C').

Several relations use the same combination of Action/Source Record property values.

'value A' - Number of relations having the same combination of Action/Source Record.

'value B' - Action name.

'value C' - List of record names.

Rename Action or change the Source Record to have a unique couple.
GS-13114 SQL statement 'FULL OUTER JOIN' is vendor proprietary SQL syntax.
GS-13115 Invalid filename. A filename must be a BDL identifier.

The filename contains invalid characters. Identifiers must confirm to these rules:

  • It must include at least one character, without any limitation in size.
  • Only ASCII letters, digits, and underscore ( _ ) symbols are valid.
  • No blanks, hyphens, and other non-alphanumeric characters.
  • The initial character must be a letter or an underscore.
  • It is recommended to always write identifiers in lower case.

Rename the file to a valid filename. If the file was generated, renaming the object may not be enough; you will have to rename the file itself to match the new object name in Project Manager.
GS-13116 Several comboboxes use the same initializer name.

Make all initializer names unique.
GS-13117 A ComboBox is possibly not initialized.

Set the initializer or the items property of the ComboBox.
GS-13118 Table 'table' unused in query.

A database table is used in the record, but there is no join for it in the query. Add a join for the table in the record query.
GS-13119

Duplicated joins are forbidden in the query.

Remove the duplicated joins.
GS-13120 Building 'file' generates an XML file (version='value A') which cannot be handled by the templates (version='value B').

The build process of the file ('file') has been aborted because the intermediate XML file has a version ('value A') which mismatches the template version ('value B').

Use a valid template set defined in Application Generator Preferences. Verify build rules for the appropriate file type.
GS-13121 The 'property' property is not supported.

In the Business Application diagram, the openMode or defaultMode property defined on a relation between a CRUD Form and a Zoom Form is not supported. Only DISPLAY and SEARCH values are currently supported on a Zoom. Change the openMode or defaultMode property to a supported value.
GS-13122

The property property is missing in settings.agconf.

The build process has been aborted because the property dynamicProperty is missing in the settings.agconf configuration file.

Check settings.agconf and confirm:

  • The <DynamicProperty> node with name="property" is defined in the <BusinessApplication> section.
  • The dynamicProperties attribute of the item raising the error contains property.
GS-13123 No CRUD function will be generated for the 'table' table because no primary key has been defined.

A primary key needs to be defined for the given table in order to have its CRUD functions generated when compiling the database schema.
GS-13124 Record functionalities are incompatible with the 'property' property value ('value').
On a CRUD Form, if the openMode or defaultMode property is:
  • ADD, the master record must have the functionality canAdd activated.
  • EMPTY, the master record must have the functionality canEmpty activated.
  • DISPLAY, all records must have the functionality canDisplay activated.
  • MODIFY, at least one record must have the functionality canModify activated.
On a CRUD Form or Zoom Form, if the openMode or defaultMode property is SEARCH, at least one record must have the functionality canSearch activated.

On incoming relations of a CRUD Form or Zoom Form, the openMode and defaultMode property must follow the same rules as those forms.

To fix the error, change the openMode or defaultMode property value or change the functionality of the record.
GS-13125 'value A' doesn't exist or is not unique'value B', please have a look in the XML intermediate file.

An XPath cannot be resolved. Check the XML intermediate file.

GS-13126 The number of source fields defined on the relation doesn't match the number of unique key fields defined in the destination item.

Change the number of source fields defined on the relation.
GS-13127 Destination fields defined on a relation to a zoom are unused in the code generation.

The destination fields defined on a Zoom relation will not appear in the generated 4gl code.
GS-13128 The table 'seqreg' is missing in your database schema, therefore SERIAL fields cannot be handled by the templates.

A database schema field of datatype SERIAL can only be handled by using the seqreg table. This table contains a list of table names and values, a value is the last SERIAL created for a given table name. In case the couple (table name, last value) does not exist, a new record will be created and the SERIAL value will start at 1.

Create the table seqreg in your database schema file.
GS-13129 Multiple SERIAL fields for the table 'table' cannot be handled by the templates.

Only one SERIAL field can be managed per database table. This is inherent to the seqreg table.

Modify the table in you database schema file.
GS-13130 Business Application diagram is missing in the project.

Add a Business Application Diagram to the project.
GS-13131 Unique key must be a database primary or secondary key of the master table.

All fields making up the unique key of a record must be either a database primary key or secondary key of the master table (unique constraint).

Change the unique key property of fields which are not a database primary key or secondary key of the master table or update the 4dbx schema.

GS-13132 Missing master table for 'record' record.

Select a table in the master table property.
GS-13133 The field 'field' defined on the relation does not exist in Records view.

In the Business Application diagram, when a relation is defined between items, the Source Field and the Destination Field must exist in the Records view.

Check the Source Field and/or Destination Field property of the relation or open the appropriate item and add the missing fields.
GS-13134 Invalid relation, Source and Destination must have same number of fields.

In the Business Application diagram, a relation between Forms must have the same number of fields in the Source Field and Destination Field.

Check  the Source Field and/or Destination Field property of the relation.
GS-13135 Invalid action name. The 'Action' property must be a BDL identifier

The Action property of the relation is not a valid Genero BDL identifier.

For further information, see Identifiers in the Genero Business Development Language User Guide.
GS-13136 The Service Name property is mandatory.

The property Service Name of a WebService item must have a value in the Business Application Diagram.

Set the Service Name property value.
GS-13137 The Namespace property is mandatory. The property Namepace of a WebService Server item in a Business Application diagram must have a value.

Set the Namespace property value.
GS-13138 Several web services use the same name.

Any web service registered to the same Web Service Server must have an unique name.

Ensure that the property Name of a web service is unique.
GS-13139 The 'action' action is a reserved action name.

In the Business Application Diagram, when a relation is defined between items, the Action property can not be a reserved action name. The list of reserved action names is defined in the action defaults file (dbapp.4ad).

Set the value of the Action property to a non-reserved action name.
GS-13140 Unexpected TCL script error: 'error'

An unexpected internal error occurred during code generation. Contact your local support center.

GS-13141 'value' - Check LANG variable or add entry in file encoding.tcl where $1 is the value of the unsupported encoding

The LANG environment variable is set, but the encoding part is either invalid (change the value of the LANG environment variable) or not present in the supported encoding array (add an entry in encoding.tcl).
GS-13142 All fields must be part of the same record.

Choose fields from the same record.
GS-13143 The record 'record' defined on the relation does not exist in Records view.

In the Business Application diagram, when a relation is defined between items, the Record Source must exist in the Records view. Check the Source Record property of the relation or open the source entity and add the missing record.
GS-13144 The 'Source Record' property is missing.

The Source Record property is missing in the Business Application diagram. When a relation is defined between items, if the Row Bound property is checked on an outgoing relation, the Record Source must be defined if there is more than one record in the form. It is implicit if there is only one record.

Check the Source Record property of the relation or uncheck the Row Bound property.
GS-13145 The 'value' functionality is not supported for 'container' container on mobile devices.

Some functionality is not supported by the template. For example canAdd, canModify, and canSearch are not supported for tables.

Uncheck the functionality.
GS-13146 Several records 'records' are candidate for the 'Source Record' property.

Remove the ambiguity and choose a record.
GS-13147 The 'Row Bound' property is not supported for GRID container.

Uncheck the Row Bound property or choose the table container in the form.
GS-13148 The 'Source Field' property is missing.

The position Source Field is required when the destination of the relation is a zoom.
GS-13149 The 'container' container is not supported on mobile devices.

Some containers such Tree and ScrollGrid are not supported on mobile devices. Change container to a supported container.
GS-13150 'Display, Add, Modify, Search are all disabled for record 'record'

This message is a warning, not an error. It simply tells you that all functionality is disabled for the record in question. Verify that having no functionality selected for the record is intentional.
GS-13151 'The 'aggregation function' aggregation function is not supported for this field'

Ensure the data type of the field is compatible with the aggregation function:

  • AVG and SUM can only be performed on Numeric fields.
  • COUNT and DISTINCT COUNT cannot be performed on a Byte field.
  • MAX and MIN cannot be performed on a Byte or Boolean field.

For further information, go to Add aggregate fields to a record.
GS-13152 'Missing 'file' file'

The Java file argument of the 'schemagen' tool is missing. This error can occur on a build of a ReportData file(.4rdj) with Java.

Ensure that the generated Java file exists.
GS-13153 'value'

An error occurred when the external tool used to create the schema file was executing. This error can occur on a build of a ReportData file(.4rdj) with Java.
GS-13154 The 'property' property is unused in the code generation

In the Business Application diagram, a warning is raised when a property is unused in code generation.

Reset the unused property to the default value to remove this warning.
GS-13155 Database connection not generated in Program. The databaseName property is not set on first Form

If the databaseName property is not defined on the first form defined of the outgoing relation of a program, then that database connection is not generated in the program.
GS-13156 The primary field 'field' used in the relation from the 'record' record does't exist

The primary field defined in the relation does not exist. Use an existing field.

GS-13157 The primary field 'field' used in the relation from the 'record' record is not in the scope

The primary field defined in the relation does not exist in the scope of the child record at runtime.

Select a field in a valid scope. A valid scope is a record located:
  • On the path to the master record (named main branch)
  • On a child record that:
    • Is not younger than the current record
    • Is not an unbounded record
    • Is not located on a path from the main branch containing an unbounded record
GS-13158 The primary field 'field' used in the relation from the 'record' record is not in the scope

The primary field that is pointed to by the relation does not exist in the scope of the child record at runtime.

Select a field in a valid scope. A valid scope is a record located:
  • On the path to the master record (named main branch)
  • On a child record that:
    • Is not younger than the current record
    • Is not an unbounded record
    • Is not located on a path from the main branch containing an unbounded record
GS-13159 The primary field 'field' used in the relation from the 'record' record is located in a sibling record 'sibling record'

The primary field defined in the relation is located in a sibling record.
GS-13160 The primary field 'field' used in the relation from the 'record' record is located in a sibling record 'sibling record'

The primary field that is pointed to by the relation is located in a sibling record.
GS-13161 The primary field 'field' used in the relation from the 'record' record is located at the unbounded record 'unbounded record'

The primary field defined in the relation is located at an unbounded record.

Set the occurrences property of the field to '1' or '0 - 1'. For further information, go to Set occurrences for a record.
GS-13162 The primary field 'field' used in the relation from the 'record' record is located at the unbounded record 'unbounded record'

The primary field that is pointed to by the relation is located at an unbounded record.

Set the occurrences property of the field to '1' or '0 - 1'. For further information, go to Set occurrences for a record.
GS-13163 The primary field 'field' used in the relation from the 'record' record passed through an unbounded record

The primary field defined in the relation passed through an unbounded record.

For the record(s) which are passed through to reach the field defined by the parameter, set the occurrences property to '1' or '0 - 1'. For further information, go to Set occurrences for a record.
GS-13164 The primary field 'field' used in the relation from the 'record' record passed through an unbounded record

The primary field that is pointed to by the relation passed through an unbounded record.

For the record(s) which are passed through to reach the field defined by the parameter, set the occurrences property to '1' or '0 - 1'. For further information, go to Set occurrences for a record.
GS-13165 Outgoing Form from 'value' not implemented

In the Business Application diagram, a program has an outgoing relationship to an unimplemented form.

Implement the form.
GS-13166 Outgoing Web Service from 'value' not implemented

In the Business Application diagram, a Web Service Server has an outgoing relationship to an unimplemented Web Service.

Implement the Web Service.
GS-13167 The foreign field 'field' used in the relation from the 'record' record appears more than once

Check that the foreign field (field defined by the parameter) is not already used by the record relation.
GS-13168 Search criteria not managed on detail 'value' because SQL is custom

When custom SQL is set to a detail business record of a form, report, or service, the search criteria is not managed.

To handle query by example, manage the SQL by hand within a <POINT> tag.
GS-13169 Invalid relation name. The 'Name' property of the relation must be a valid identifier.

The name of the relation contains invalid characters. Identifiers must confirm to these rules:

  • It must include at least one character, without any limitation in size.
  • Only ASCII letters, digits, and underscore ( _ ) symbols are valid.
  • No blanks, hyphens, and other non-alphanumeric characters.
  • The initial character must be a letter or an underscore.

Rename the name of the relation to a valid name.
GS-13170 The table 'table' can not have the same name as the database schema.

In the database schema diagram, a table has the same name as the database schema. This is not allowed.

Either rename the schema file or rename the table.
GS-13171 The 'field' field used in ORDER BY is missing in the 'record' record.

The field used in ORDER BY is not present is the record.

Either add the missing field to the record or replace the ORDER BY field with a field present in the record.
GS-13172 The 'record' record name is incompatible with report filename.

The record and the report file cannot have the same name.

Either change the name of the record or the report filename.
GS-13173 The value A is not allowed as dialog control instruction for 'value B' code event function in mode value C. Use value D instead

This is a runtime error that occurs when the event code uses an invalid dialog control instruction.

Adapt the return values of the dialog control instruction according to the code events function.
GS-13174 Invalid relation, it must have at least one field

This error is raised only for templates dbapp4.*, dbapp3.*, dbapp2.0, and dbapp1.0.

In a record relation, the whereParameters property cannot be empty. Add a value for whereParameters.

GS-13175 Relation data types do not match. 'name' is a 'data type', which is not compatible with the 'value' data type of 'field name'

name = parameter field name

data type = parameter data type

value = parameter value data type

field name = parameter field name

The type of a parameter does not match the type of the corresponding value.

Check the relation, change the field types, or fix the parameter/value.
GS-13176 The 'file' must contain at least one database field

The records in file 'file' do not contain any database fields.

To resolve this error:

  1. Define the databaseName property on the root node document.
  2. Either add a new field or select an existing field.
  3. Set the field type to something other than NON_DATABASE.
GS-13177 The foreign field 'field' used in the relation from the 'record' record does't exist

The foreign field (field defined by the parameter) does not exist. Use an existing field.

GS-13178 'value A' requires a colAliasName because 'value B' is already used

The generated colAliasName for the database field conflicts with a non database field name or with the colAliasName of another field.

To resolve this error, do one of the following:
GS-13179 Invalid 'value' lookup field. It must be a database field

The 'value' formonly field lookup property must match one of the <table.column> database fields available in the comboBox.
GS-13180 'data type' must match the 'database' database type of the 'field' lookup field

When an ascending lookup is defined, the data type 'data type' of the formonly must match the 'database' database type of the 'field' lookup field.