Error messages

SSH connection to target host failed.

Verify the policy settings (IP address and port).

TRO9002E

Connection failure to device.

• Verify the policy settings.
• Consult the BMC Customer support for additional assistance.

TRO9003E

General error occurred while connecting to the device.

• Verify the policy settings.
• Consult the BMC Customer support for additional assistance.

TRO9004E

Failed to initialized connection settings for device.

TRO9005E

Failed to resolve device (host) IP address.

TRO9007E

Script execution failure.

TRO9007E

Script execution failure.

Additional information: No valid connection to device.

• Verify the policy settings.
• Check if the configured host is active and can be accessed or not.

TRO9008E

General error occurred while executing the script

Verify the Script before execution.

TRO9012E

Failed to copy the script to device (host).

TRO9013E

Failed while loading properties file. This may be caused by a corrupted installation or the files are not accessible to the PATROL Agent user.

Verify the PATROL Agent connection.

The JAVA collector found there is no is no running PATROL agent on this server. Monitoring cannot
be done without the an active agent controlling the JAVA collector.

• Install and run the PATROL agent
• Set the PATROL_HOME environment variable to the right PATH.

Failed to load the messages file. This may be caused by corrupted installation or running the patrol agent with a user that cannot access some of the directories inside the PATROL installation PATH.

TRO9011E

Script does not exist

Additional information: Script does not exist in any defined location on the device (host).

TRO9019E

Failed to initialized connection settings

Additional information: Missing password or public/private key path.

Metadata is invalid

Additional information: Metadata is invalid this means PATROL cannot create the monitor types required
for monitoring with the configured script.

Make sure monitor type name and parameter names do not contain any of the following (invalid) characters:

[%s].

Script timeout

Additional information: Script execution time in milliseconds exceeded the configured timeout.

Invalid metadata for monitor type creation.

Additional information: Metadata is invalid this means PATROL cannot create the monitor types required
for monitoring with the configured script.

The cause of the problem is in having multiple parameters with the same name.

Make sure that the parameters are unique and presented only once in each line of the script's output

(e.g.: [MonitorTypeName=instanceName1,parameter1=value,parameter2=value,parameterN=value] is valid but [MonitorTypeName=instanceName1,parameter1=value,parameter1=value,parameterN=value] is invalid because the
parameter name [parameter1] exist more than once in the same line of output).

Invalid script output format

Additional information: Metadata is invalid this means PATROL cannot create the monitor types required for monitoring
with the configured script.

• Make sure the script output has 1 of the following format patterns:
• Single value (the first line is a number and all other lines can be a text base)
• Multiple instances (each line simulate an instance with its name and parameters
  [e.g.: MonitorTypeName=instanceName1,parameter1=value,parameter2=value,parameterN=value]).

TROMS9000I

TROMS9001E

TROMS9002E

• Verify the remote PowerShell access using the configured connection settings.
• Verify the policy settings (port,username,password) and correct if needed.

TROMS9003E

• Verify the remote PowerShell access using the configured connection settings.
• Consult with BMC support.

TROMS9004E

• Verify the remote PowerShell access using the configured connection settings.
• Verify the policy settings (device and script configuration).
• Verify the file based configuration defined according to the instructions. 

TROMS9005E

TROMS9006E

• Verify that the script can be run successfully using PowerShell Cli
• Verify that the script output has a valid format.

TROMS9007E

TROMS9008E

• Verify the script can be run on the PowerShell
• Verify the script output has a valid format.

TROMS9009I

TROMS9010I

TROMS9011E

Please make sure that the script file exist on the remote device.

TROMS9012E

TROMS9013E

TROMS9014W

TROMS9015W

• Install and run the PATROL Agent
• Set the PATROL_HOME environment variable to the right PATH.

TROMS9016W

TROMS9017W

TROMS9018E

TROMS9019E

TROMS9020W

TROMS9021E

Make sure monitor type name and parameter names do not contain any of the invalid characters:

TROMS9023E

Make sure that the parameters are unique and presented only once in each line of the script's output

Example: [MonitorTypeName=instanceName1,parameter1=value,parameter2=value,parameterN=value] is valid but [MonitorTypeName=instanceName1,parameter1=value,parameter1=value,parameterN=value] is invalid because the parameter name [parameter1] exist more than once in the same line of output.

TROMS9024E

Make sure the script output has one of the following format patterns:

Single value (the first line is a number and all other lines can be a text base)

Multiple instances (each line simulate an instance with its name and parameters

[Example: MonitorTypeName=instanceName1,parameter1=value,parameter2=value,parameterN=value]). 

TROMS9025E

• Verify that the script can be run successfully using PowerShell Cli
• Remove the script format list attribute.