Remap of a customized view failed: rc=return code, layout_rc=layout return code.
Explanation: During the creation of a customized view, the server positions the resources and creates view information for use by the console. The function that handles the positioning of resources in the view has failed. This error may be caused by the database file containing the customized view information being corrupt or missing.
Message Inserts:
System Action: In order to position the resources, the server invokes another function. The result is that the customized view information will not be displayed.
Operator Response: Undo the customization for the view. Make view changes and save it again.
System Programmer Response: Examine the error log for additional information.
Explanation: An error occurred when the topology console requested to save a view on the server. This is caused by an internal error in the server, such as the view not being found in the server database.
System Action: The topology server ignores the request to save the view.
Operator Response: Contact the server administrator.
System Programmer Response: Examine the log file for additional information.
An installation error was detected (rc). The server will terminate. Please contact Tivoli Support Center.
Explanation: The server detected a corrupted file during initialization.
Message Inserts:
System Action: The server terminates.
Operator Response: Contact your system programmer.
System Programmer Response: Re-install the server.
Enclosing parenthesis for Query Task response entry are not matched or ordered correctly.
Explanation: Each entry in the Query Task response must begin with an open parenthesis and end with a closed parenthesis. The topology server detected that the Query Task response contained an entry that did not begin with an open parenthesis or did not end with a closed parenthesis. This message is also issued when two open parentheses are found without an intervening closed parenthesis.
System Action: The topology server ignores any remaining Query Task response entries. The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
Entry identifier entry-identifier for a Query Task response entry is missing or not a valid identifier.
Explanation: The topology server detected an entry identifier in the Query Task response that is not valid. Valid identifiers for Query Task response entries are: 1, 2, 3, 4, 5, 7, and 8.
Message Inserts:
System Action: The topology server ignores any remaining Query Task response entries. The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
Query Task response entry with identifier entry-identifier has number-received data tokens. Expected number-expected data tokens.
Explanation: The topology server detected an entry in the Query Task response that specified an incorrect number of data tokens.
Message Inserts:
System Action: The topology server ignores any remaining Query Task response entries. The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
No entry with identifier entry-identifier found in Query Task response.
Explanation: The topology server detected a missing entry in the Query Task response.
Message Inserts:
System Action: The topology server ignores any remaining Query Task response entries. The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
Found number-received entries with identifier entry-identifier in Query Task response. Only one such entry permitted.
Explanation: The topology server detected multiple entries having an entry identifier of entry-identifier. The Query Task response can have only one entry with that entry identifier.
Message Inserts:
System Action: The topology server ignores any remaining Query Task response entries. The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
Query Task response contains incorrect syntax. No monitor value updates will be performed.
Explanation: The topology server detected one or more errors in the syntax of the Query Task response returned from the instrumentation.
System Action: The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
Query Task response contains valid syntax. Proceeding with monitor value updates.
Explanation: The topology server successfully parsed the syntax of the Query Task response returned from the instrumentation.
System Action: The topology server proceeds with monitor updates based on the information in the Query Task response.
No entry with identifier entry-identifier-1 or entry-identifier-2 found in Query Task response. At least one expected.
Explanation: The Query Task response must have at least one entry with either of the specified entry identifiers.
Message Inserts:
System Action: The topology server ignores any remaining Query Task response entries. The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
Each Query Task response entry must start with open parenthesis.
Explanation: The topology server detected that the Query Task response contained an entry that did not begin with an open parenthesis.
System Action: The topology server ignores any remaining Query Task response entries. The monitor associated with the failing Query Task is not updated.
Operator Response: Contact the provider of the Query Task instrumentation.
Setting value of monitor resource monitor-name to monitor-value.
Explanation: The topology server is updating the value for a monitor resource.
Message Inserts:
Performing periodic polling of selected monitors on resource resource-name.
Explanation: The polling interval for the specified resource has expired. The topology server will begin querying selected monitors on that resource and updating views with the current monitor values.
Message Inserts:
The file descriptionFile2 has the same manufacturer, product, version and abstraction level as descriptionFile1 which was parsed earlier. This is not allowed.
Explanation: Description files must be uniquely identified by the combination of their following four key identifiers:
Identifier | Source group |
---|---|
manufacturer | component ID group | product | component ID group | version | component ID group | abstraction level | component type group |
All four of these identifiers are the same in descriptionFile1 and descriptionFile2, so descriptionFile2 is not used.
Message Inserts:
System Action: The server logs this message and continues running.
Operator Response: Contact your system programmer.
System Programmer Response: Remove or modify one or both of the files in order to resolve the conflict. If you are unable to fix the problem, contact the suppliers of the description files.
Aggregation task aggregation_task_name for exit exit_name failed with return code return_code_value.
Explanation: IHSXSRV.EXE encountered an error while invoking the designated aggregation query task.
Message Inserts:
System Action: The component for which this task was defined is added to the last successfully queried aggregate, and marked for retry. The next time a heartbeat is received for this component, the aggregation tasks are retried (unless this component is manually moved to another aggregate).
Operator Response: Verify that the specified aggregation task is correctly defined and installed. If the problem persists, contact your system programmer.
System Programmer Response: If the specified aggregation task is correctly defined and installed, contact your Tivoli Support Center.
Component information task task_name for exit exit_name failed with return code return_code_value.
Explanation: The topology server encountered an error while invoking the specified component information task.
Message Inserts:
System Action: The instance of the component for which this task was defined is not included as a member of the business system to which it is being mapped. This task is marked for retry and will be attempted again on the next heartbeat.
Operator Response: Verify that the specified component information task is correctly defined and installed. If the problem persists, contact your system programmer.
System Programmer Response: If the specified component information task is correctly defined and installed, contact your Tivoli Support Center.
Component component_name is not a member of business system
business_system_name.
Origin: origin
Suborigin: suborigin
Subsource: subsource
Explanation: This instance of the component was not included as a member of the specified business system. This is usually a normal condition and indicates that membership criteria specifications supplied in the business system mapping were not met by this component instance. It can also mean that the criteria are not valid or the component information tasks could not be run.
Message Inserts:
System Action: The specified instance of the component is not included in any views related to the business system.
Operator Response: If the component instance should be a member of the business system, check the message log for additional messages indicating a problem. The membership criteria specified in the instrumentation may not have been valid or the component information tasks may not have run successfully. Check the helps for any messages for more information.
If no other messages were logged, then the output from the component information tasks does not meet the membership criteria, and one or both will need to be modified in order for the component instance to be included.
Component component_name in business system business_system_name had errors in the membership criteria specification.
Explanation: A component information change event was received, but there was no resource in the resource database, or there was no previous component information available for the specified task.
Message Inserts:
System Action: The specified instance of the component is not included in any views related to the business system.
Operator Response: Check the message log for additional messages indicating a problem with instance membership criteria specification.
Component information change event did not have a matching resource or any matching component information.
Business system: business_system_name
Origin: origin
Suborigin: suborigin
Subsource: subsource
Task Name: component_information_task_name
Task Value: component_information_task_value
Change: type_of_change
Explanation: The mapping of the business system to the component had errors in the specification of the membership criteria in the management tool extensions.
Message Inserts:
System Action: The change event is ignored and the instance membership is unaffected.
Operator Response: If this component information task is being used for specifying aggregation information, but not membership information, ignore this message. In other cases, check the error log for additional messages that might indicate that the task did not run successfully.
Component information substitution value substitution_value could not be resolved.
Explanation: The topology server was unable to substitute any resource instance data for the specified substitution value. The value is probably not one of the support values.
Message Inserts:
System Action: The instance of the component for which this substitution value was defined is not included in the business system to which it is being mapped. This message will continue to be logged each time membership evaluation is attempted for this resource.
Operator Response: Make sure that the substitution value is one of the values supported. If it is supported, notify your system programmer.
System Programmer Response: Contact your Tivoli Support Center.
Do you want to delete Customized Dynamic View view_name?
Explanation: This message is a confirmation message to insure you want to delete the customization of the dynamic view you have selected.
Message Inserts:
System Action: If you respond YES the view will be deleted, if you respond NO no action is taken.
Operator Response: Confirm either YES or NO for deleting or not deleting the customized dynamic view.
System Programmer Response: None
Unable to open configuration file configuration_file_name.
Explanation: The topology server encountered an error while trying to open the specified configuration file.
Message Inserts:
System Action: No events will be sent to TEC from this topology server.
Operator Response: Verify that the configuration file exists exactly as shown in the message and can be accessed by the machine on which the topology server is running.
System Programmer Response: If the configuration file exists in the expected location, contact your Tivoli Support Center.
Error in server specification or connecting to server specified on line line_number of configuration file.
Explanation: The topology server encountered an error while trying to parse the specified line in the specified configuration file. Another possible cause is that the line was successfully parsed, but communications could not be established with the server specified on the line.
Message Inserts:
System Action: No events will be sent to the specified TEC server from this topology server.
Operator Response: Verify that the specified TEC server exists and is listening on the specified port (if the portmapper is not in use on the TEC server machine). Check the syntax of the configuration file entry using the instructions in the comments contained in the file.
System Programmer Response: If the TEC server specification is correct and specifies a valid active TEC server, contact your Tivoli Support Center.
Error sending APM_NOTIFICATION event to server server_name,port port_number.
Resource: resource_label
Old status: old_status
New status: new_status
Explanation: The specified event was created but could not be successfully sent to the specified TEC server. The server was located and communications was established, but the topology server was unsuccessful in opening a port and sending the event data to the TEC server.
Message Inserts:
System Action: No event was sent to the specified TEC server, but the topology server will attempt to send the event to any other TEC servers specified in the configuration file.
Operator Response: Consult with your system programmer to determine if the specified server/port combination represents a valid active TEC server.
System Programmer Response: If the TEC server specification is correct and specifies a valid active TEC server, contact your Tivoli Support Center.
The server is terminating due to an internal error, RC=retcode.
Explanation: An unrecoverable error occurred in the topology server.
Message Inserts:
System Action: The topology server terminates. Databases may not be saved.
Operator Response: Contact your system programmer responsible for the topology server.
System Programmer Response: Try to restart the server. If the problem persists, check the message and error logs for information. If you are unable to fix the problem, contact the Tivoli Support Center.
An error was encountered during the compilation of an
extended regular expression used for instance membership filtering.
Type of error: ErrType
Extended regular expression: ExtRegExp
Filename: Filename
Explanation: An error was encountered while compiling an extended regular expression used for instance membership filtering. This indicates that the specified ExtRegExp is not a valid extended regular expression. The source of the ExtRegExp in error is an entry in the management tool extensions group with a variable name of InstanceMembershipCondition or InstanceMembershipTest in Filename.
Message Inserts:
System Action: The InstanceMembershipCondition and InstanceMembershipTest entries in the management tool extensions group of the specified file are not used for instance membership filtering.
Operator Response: Correct the extended regular expression that is in error and restart the topology server.
An error was encountered during the evaluation of an extended regular
expression used for instance membership filtering.
Type of error: ErrType
Extended regular expression: ExtRegExp
Filename: Filename
String evaluated: StringEvaluated
Explanation: An error was encountered while evaluating the specified string using the extended regular expression ExtRegExp for the purpose of instance membership filtering. This indicates that the extended regular expression is not valid. The source of the the erroneous expression is an entry in the management tool extensions group with a variable name of InstanceMembershipCondition or InstanceMembershipTest in Filename.
Message Inserts:
System Action: Some or all of the resources of the type described by Filename may not be included in the appropriate views.
Operator Response: Correct the extended regular expression that is in error and restart the topology server.
An invalid sequence number was found in an InstanceMembershipCondition entry in the management
tool extension group.
Filename: Filename
Sequence number: SeqNumber
Explanation: Sequence numbers are used to determine the order in which InstanceMembershipCondition entries should be evaluated. These sequence numbers should have the following characteristics:
The sequence number of the entry in error violates one of these required characteristics.
Message Inserts:
System Action: The InstanceMembershipCondition and InstanceMembershipTest entries in the management tool extensions group of the specified file are not used for instance membership filtering.
Operator Response: Correct the sequence number or numbers that are in error and restart the topology server.
More than one InstanceMembershipTest entry was found in the management tool extensions group.
Filename: Filename
Explanation: More than one InstanceMembershipTest entry was encountered in the management tool extensions group in the specified file. Only one InstanceMembershipTest entry is allowed per management tool extensions group.
Message Inserts:
System Action:
The InstanceMembershipCondition and InstanceMembershipTest entries in the management tool extensions group of the specified file are not used for instance membership filtering.
Operator Response: Remove all but one of the InstanceMembershipTest entries from the management tool extensions group of the specified file and restart the topology server.
A syntax error was encountered in an InstanceMembershipCondition entry in the management
tool extensions group.
Filename: Filename
Explanation: The syntax is not valid in one or more InstanceMembershipCondition entries in the management tool extensions group of the specified file.
Message Inserts:
System Action: The InstanceMembershipCondition and InstanceMembershipTest entries in the management tool extensions group of the specified file are not used for instance membership filtering.
Operator Response: Correct the syntax of the InstanceMembershipTest entries in the management tool extensions group of the specified file and restart the topology server.
Message from sender sender_name:
the_message
Explanation: A message has been sent to you from the topology server or another topology console.
Message Inserts:
Explanation: This message displays a keyword and its value in seconds read from the server.properties file. For more information, see the server.properties file.
Message Inserts:
Explanation: This message displays a keyword and its value in intervals read from the server.properties file. For more information, see the server.properties file.
Message Inserts:
Explanation: This message displays a keyword and its value in percent read from the server.properties file. For more information, see the server.properties file.
Message Inserts:
Explanation: This message displays a keyword and its value read from the server.properties file. For more information, see the server.properties file.
Message Inserts:
Explanation: This message confirms that a broadcast message has been sent to all consoles logged on to the server.
Message Inserts:
Explanation: This message confirms that a broadcast message has been sent to a specific console.
Message Inserts:
Explanation: The message could not be delivered because the receiver is either not signed or is the originator of the message.
Message Inserts:
Explanation: This message indicates that a broadcast message could not be delivered because no receiving consoles were signed on.
Message Inserts:
Explanation: This message displays a keyword and its value in milliseconds read from the server.properties file. For more information, see the server.properties file.
Message Inserts:
Explanation This message displays a keyword and its value in ticks read from the server.properties file. For more information, see the server.properties file.
Message Inserts:
Explanation: This message displays a keyword and its value in statusUpdateIntervals read from the server.properties file. For more information, see the server.properties file.
Message Inserts:
Explanation: This message displays a keyword and its value in viewChangeIntervals read from the server.properties file.
Message Inserts: