Users Guide

Troubleshooting

You can troubleshoot ASM vRO Integration issue using:

• vRO Exceptions

• vRO Application Server Log

• ASM Log

vRO Exceptions

When an API method is invoked through actions or scripts, the operation is requested by the ASM server.

However, the ASM server may return an error message due to internal server issues or bad user inputs. In

such cases, the message is mapped to an exception to be thrown. Typically, these messages are reported

with the following format:

Message<sequence number>

• Message code

• Severity

• Category

• Display message

• AgentId

• Timestamp

• Sequence number

There may be multiple messages sometimes. Plugins throw exceptions with appropriate messages to

indicate any problem during the operation.

vRO Application Server Log

There are exceptional cases where the exception returned to the vRO which does not include enough

details. In this case, the best way to track down the issue is by checking the vRO application server logs.

You need access to the vRO appliance shell and read privileges for the following files (different in custom

installations):

• /var/log/vco/app/catalina.sh

• /var/log/vco/app/server.out