Topology Server Message Help
Internal error during object construction for file file.
Explanation:
An error occurred while constructing an internal object for the specified
file.
Message Inserts:
- file
- Filename of BDF or CDF object was being created for.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Problem parsing file file.
Component information may be incomplete or unavailable.
Explanation:
An error occurred while parsing the specified file.
Message Inserts:
- file
- Filename of BDF or CDF that had parsing problem.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error parsing group group.
Component information may be incomplete or unavailable.
Explanation:
An error occurred while parsing the specified group. Other messages will
indicate the actual error and file.
Message Inserts:
- group
- The name of the group where the error occurred.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error parsing table table, row row, col column.
Explanation:
An error occurred while parsing the specified table.
Message Inserts:
- table
- Name of table where error occurred.
- row
- Table row number of error.
- column
- Column number of attribute with error.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error parsing attribute attribute.
Explanation:
An error occurred while parsing the specified attribute. Additional messages
will provide more details on the error.
Message Inserts:
- attribute
- Name of the attribute in error.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Value missing for required attribute.
Group: group
Attribute ID: attribute
Explanation:
The specified attribute requires a value, but none was specified in the table
and no default is defined in the group description.
Message Inserts:
- group
- Name of group with missing attribute.
- attribute
- ID of attribute with missing value.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Data type mismatch for group group, attribute attribute.
Expected type: expected
Found type: found
Explanation:
The data type of the specified attribute did not match the one specified in the
group description.
Message Inserts:
- group
- Group where error occurred.
- attribute
- Name of attribute in error.
- expected
- Data type expected.
- found
- Data type found.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - duplicate attribute ID specified.
Group: group
Attribute name: attribute, ID: id
Explanation:
The specified group contained two attributes with the same attribute ID.
Attribute IDs must be unique within a group.
Message Inserts:
- group
- Name of group with error.
- attribute
- Name of second attribute with matching id.
- id
- Attribute ID number that is duplicated in this group.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Data type mismatch for attribute attribute.
Expected type: expected
Found type: found
Explanation:
The data type of the specified attribute does not match that defined in the group
description.
Message Inserts:
- attribute
- Name of attribute in error.
- expected
- Data type expected.
- found
- Data type found.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - too many attributes in table row.
Table: table, row row
Explanation:
The specified table had too many attributes specified for the group definition.
Message Inserts:
- table
- Name of table in error.
- row
- Table row where error occurred.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Attribute error in table table, row row, attribute attribute.
Explanation: An error occurred while processing the specified attribute.
Other messages will indicate the problem, and the file where the error occurred.
Message Inserts:
- table
- Name of table with error.
- row
- Table row in error.
- attribute
- Name of attribute in error.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - enum found with no name.
Explanation:
An enumeration was specified with no name.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - enum name not found.
Explanation:
The enumerated type specified was not found in the group description.
Message Inserts:
- name
- Name of the enum being looked for.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - enum symbol symbol not found.
Explanation:
The enumeration symbol value was not found in the group description.
Message Inserts:
- symbol
- Enumeration symbol that had no corresponding integer value.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - enum error in attribute attribute.
Explanation:
There was a general syntax error in the specified attribute. Additional messages
will provide more detail.
Message Inserts:
- attribute
- Name of attribute where error occurred.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - unsupported type type in table table, row
row, col column.
Explanation:
A table entry contains a type not supported by the current code.
Message Inserts:
- type
- Type of data provided.
- table
- Name of table with error.
- row
- Table row with error.
- column
- Column number in table with error.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Error - table missing class name. Table ID = table.
Explanation:
A table was found that did not have a class name specified.
Message Inserts:
- table
- ID of table with missing class name.
System Action: The topology server continues with missing information.
Operator Response:
Do the following:
- Correct or replace the appropriate file.
- Restart the server.
- If the server restarts with no errors and information is still missing,
erase the server databases and restart the server. Erasing
the databases will cause you to lose any customization you may have done.
For that reason, you should
create a backup prior to erasing the databases, so that you can restore
them if the problem persists.
Parsing file file.
Explanation:
The specified file is being parsed.
Message Inserts:
- file
- Name of file currently being parsed.
System Action:
The topology server parses file.
Unable to place BDF file in the BDF hierarchy.
File name: filename
Description: file description
Explanation:
topology typically uses the following four types of BDF files:
- Business system
- Business subsystem
- Business system component
- Mapping
When the topology server starts, it reads all of the BDF and CDF
files from the %BINDIR%\TDS\Server\db\current\appdefs subdirectory on
non-UNIX platforms or the $BINDIR/TDS/Server/db/current/appdefs subdirectory
on UNIX platforms. BINDIR is an environment variable by the installation code
to indicate the root location of the topology server code.
It then places
the BDF files into an internal BDF hierarchy according to the following
rules:
- Place all of the business system BDFs on the top row of the hierarchy
as peers.
- Repeatedly iterate through all of the BDFs that have not
been placed in the hierarchy until you make a complete pass through
all BDFs without placing any.
- Examine each of the remaining BDFs. If its parent is already placed
in the BDF hierarchy, then place the unplaced BDF
in the hierarchy as a child of that parent BDF.
When this process is complete,
all BDF files should be placed in the hierarchy.
This message is written to the message log for each
BDF file that is not placed in the hierarchy.
Message Inserts:
- filename
- The file name of the BDF file the was not placed.
- file description
- The description of the BDF file that was extracted from the
BDF file.
System Action:
The specified BDF file is not used by the server.
Events defined by this BDF file may not be recognized.
Operator Response:
Contact your system programmer or the person responsible for the BDF files.
System Programmer Response:
Correct the BDF file or contact someone who can. The
most common causes of this problem are:
For a Business Subsystem BDF:
- The parent ID is incorrect in the subsystem BDF.
- The component ID is incorrect in the business system BDF
that should be this BDF's parent.
- The business system BDF that should be this BDF's parent is missing
or was not placed in the BDF hierarchy due to some other error.
For a Business System Component BDF:
- The component ID of the business system component BDF is incorrect.
- The subcomponent group of the business system BDF or business
subsystem BDF that should be this BDF's parent is incorrect.
- The business system BDF or business subsystem BDF that should be
this BDF's parent is missing or was not placed in the BDF hierarchy
due to some other error.
For a Mapping BDF:
- The parent ID group of the mapping BDF is incorrect.
- The component ID of the BDF that should be this BDF's parent
is incorrect.
- The BDF that should be this BDF's parent is missing or was not
placed in the BDF hierarchy due to some other error.