Sometimes, a control action fails, but the error message does not always help me pinpoint the true cause of the problem. How can I figure out what was the source of the error?
Sometimes, failed control actions will store their exception message and stack trace. Use the CLI to display this exception data. First, issue the CLI command “apl list history” to list the control history action items: jon-shell::jonadmin> apl list history -server “my resource name” where -server can also be -service or -platform depending on what resource the control action was executed on. “my resource name” is the name of the resource, but you can also specify the resource identifier, if you know it (e.g. -server 10001). An example response to this command is: Id Batch User Date Started Action Duration Status Description Results — —– —- ———— —— ——– —— ———– ——- 10004 jonadmin 2/21/06 12:15:39 PM TheActionThatFailed 00:00:06 Failed This did not complete successfully This lists all the control history items. Find the one that failed that you are interested in and remember its ID number.
Related Questions
- Sometimes, a control action fails, but the error message does not always help me pinpoint the true cause of the problem. How can I figure out what was the source of the error?
- When trying to print reports, I get an error message "Cannot shift objects off sheet" or Cashflow Plan fails to hide columns in certain reports?
- I m getting an error message saying Hardlock EYE not found. What is the problem?
