Error messages

The following table lists the error messages and explains the probable cause of the error and the workarounds that can be performed to counter these errors.

Related topics


Linux error messages

Error codeMessage descriptionCorrective action(s)
TRO900IConnection established.
TRO9001E

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.

Verify the policy settings.

TRO9005E

Failed to resolve device (host) IP address.

Verify the policy settings.

TRO9007E

Script execution failure.


Verify the Script before execution.

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.

TRO9009IModified script copied to remote device, and monitoring will start in the next polling cycle.
TRO9010IScript copied to remote device, and monitoring will start in the next polling cycle.

TRO9012E

Failed to copy the script to device (host).

Verify the host connection.

TRO9013E

Initialization error occurred.Verify the host connection.
TRO9014W

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.

TRO9015W

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.
TRO9016WFailed while initializing loggers. This may be caused by corrupted installation or running the PATROL Agent with an user that cannot write to some directories inside the PATROL installation PATH.Verify the directories inside the PATROL installation path.
TRO9017W

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.

Verify 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).

Copy the script to the remote system.

TRO9019E

Failed to initialized connection settings

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

Verify policy settings (Password,public/private key and correct if needed).
TRO9020WContent match found.
TRO9021E

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].

TRO9022W

Script timeout

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

Increase configured timeout of script execution.
TRO9023E

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).

TRO9024E

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]).

Windows error messages

Error codeMessage descriptionCorrective action(s)

TROMS9000I

Connection established.

TROMS9001E

Connection is broken, reconnecting to the remote machine.Verify the policy settings.

TROMS9002E

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

TROMS9003E

General error occurred while connecting to the device.
  • Verify the remote PowerShell access using the configured connection settings.
  • Consult with BMC support.

TROMS9004E

Failed to initialized connection settings for the configured device.
  • 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

Failed to resolve device (host) IP address.Verify the configured host can be resolved to an IP address.

TROMS9006E

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

TROMS9007E

Script execution failure. No valid connection to device.Verify the remote PowerShell access using the configured connection settings.

TROMS9008E

General error occurred while executing the script
  • Verify the script can be run on the PowerShell
  • Verify the script output has a valid format.

TROMS9009I

Modified script copied to remote device, and monitoring will start in the next polling cycle.

TROMS9010I

Script copied to remote device, and monitoring will start in the next polling cycle.

TROMS9011E

The script file does not exist. Unable to find the configured script file in any of the standards locations.

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

TROMS9012E

Failed to copy the script to the configured device (host).

TROMS9013E

Initialization error occurred.

TROMS9014W

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

TROMS9015W

The Csharp (C#) collector found that the PATROL Agent is not running on the server. Monitoring cannot be done until an active PATROL Agent controls the Csharp (C#) collector.
  • Install and run the PATROL Agent
  • Set the PATROL_HOME environment variable to the right PATH.

TROMS9016W

Failed while initializing loggers. This might be caused by a corrupted installation or running the PATROL Agent with a user that cannot write to some directories inside the PATROL installation PATH.

TROMS9017W

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

TROMS9018E

Failed to read from the channel. This problem can occur when a PATROL Agent halts running or the .NET runtime version is not supported.

TROMS9019E

Failed to initialize connection settings. Missing username or password.Verify the policy settings (username and password) and correct if needed.

TROMS9020W

Content match found. 

TROMS9021E

Metadata is invalid. PATROL Agent 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 invalid characters:

TRO9022WScript execution timeout. The Script execution time in seconds exceeded the configured timeout (sec) value in the policy.Verify the script policy settings, Timeout(sec) and increase the value accordingly to a value higher than the time in seconds took for the script to complete the execution.

TROMS9023E

Invalid metadata for monitor type creation. Metadata is invalid this means PATROL Agent 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

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

Invalid script output format. Metadata is invalid this means PATROL Agent cannot create the monitor types required for monitoring with the configured script.

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

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


Was this page helpful? Yes No Submitting... Thank you

Comments