What do the action status messages mean?

Technote (troubleshooting)


Problem(Abstract)

Actions will report the following action status messages back up to the TEM Server/Console at various points during an actions execution cycle.

Resolving the problem

Action Status Messages:

  • not reported - no report on this action yet. No report has yet been received from the endpoint for the action taken. We cannot confirm if the action has been propagated, mirrored, gathered, processed, or reported until this status changes to something else.
  • Fixed - The action executed successfully. The TEM Client has run the action and the relevance is now false (meaning that not only did the action run, but it fixed the issue).
  • Running - The action is currently running.
  • Evaluating - Evaluating relevance and action constraints. The TEM Client has received the action targeted at it and will evaluate the action to see if it is time to run, the issue is still relevant, etc
  • Completed - The action has completed and no other actions are required
  • Failed - The action failed. The TEM Client has run the action and the issue is still relevant (even if the action ran successfully). Note that in the cases of patches, 'Failed' usually means the patch file was run, but failed to actually patch the computer.
  • Cancelled - The action was canceled by the user. The user clicked the "cancel" button when prompted with a message box.
  • Download Failed - A required download failed.
  • Locked - This computer is locked. The TEM Client is in the "Locked" state that prevents it from running actions until unlocked
  • Waiting - The TEM Client is waiting for some condition to actually run the action. The waiting conditions include: waiting for user input, waiting to retry after failure, waiting for a time/date range, waiting for a distribution time, waiting for a user to login, and waiting until the custom constraints property becomes relevant.
    • Action has failed and is waiting before trying again.
    • Waiting on action dependency.
    • Waiting to run in specified time range.
    • Waiting until the action start time.
    • This computer is not licensed.
    • Waiting to satisfy temporal distribution time constraint.
    • Waiting for active user condition.
  • Pending Downloads - Waiting for downloads to be mirrored. The TEM Client is waiting to receive the complete file. This state will persist until the download makes it to the TEM Server -> TEM Relay -> TEM Client.
  • Pending Restart - Waiting for restart to complete action. The action was completed, but the action status of 'Fixed' or 'Failed' cannot be assessed until the computer is restarted.
  • Pending Message - Waiting for user to respond to message.
  • Pending Login - Waiting for user to log in.
  • Constrained - The computer doesn't meet the specified retrieved property constraint.
  • Expired - This action expired before it could be executed.
  • Postponed - The user postponed execution of this action.
  • Invalid Signature - The client was unable to verify the signature on this action.
  • Not Relevant - The Fixlet which this action addresses is not relevant on this machine. Before running the action, the TEM Client checked the relevance for the action and it is no longer true
  • Pending Offer Acceptance - Waiting for user to accept this offer.
  • Offers Disabled - No user is able to accept this offer.
  • Disk Limited - The download size exceeds the maximum value set in the client setting _BESClient_Download_PreCacheStageDiskLimitMB, which can be modified through the Edit Computer Settings dialog.
  • Disk Free Limited - The remaining disk space is smaller than the value set in the client setting _BESClient_Download_MinimumDiskFreeMB. In order for the download to complete, space must be cleared on the endpoint, or the client setting must be changed using the Edit Computer Settings dialog.
  • Hash Mismatch - The download completed but the file failed a hash comparison. To troubleshoot, investigate the network between the agent and its parent to eliminate network problems.
  • Transcoding Error - The action failed transcoding from the deployment codepage.
  • Pending Client Restart - Waiting for client restart to complete action.
  • <error> -
    • An unknown error occurred.
    • The Fixlet context is missing or invalid.
    • Invalid site context. The Fixlet site may no longer exist.
    • Invalid action content: the action is empty.
    • Invalid action content: the action type is invalid.
    • Invalid action content: the action script contains a syntax error.
    • This action contained invalid download syntax.
    • The download manager encountered a configuration error.
    • This action was not executed for unknown reasons.
    • This action was run but could not be restarted due to a client UI translation error.
    • This action was not executed due to an error encountered while translating the client UI elements.
    • This action was not executed due to an error showing the client UI.
    • This action failed to complete because the Management Extender plugin reported an error.
    • This action was not executed because the operator who created it is not an administrator of this client

Note that after an action expires, the action status is no longer updated.

Historical Number

172

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Endpoint Manager

Software version:

Version Independent

Operating system(s):

Platform Independent

Software edition:

Edition Independent

Reference #:

1505986

Modified date:

2014-09-25

Translate my page

Machine Translation

Content navigation