Deployed package statuses

In general, Automatic deployments show a category of status in the Package Deployment Manager page. Each category has at least one corresponding status:

Package Deployment Statuses and Error Codes for Manual Deployments

Manual deployments may display any of the following package deployment statuses or error codes in the status column.

Package Deployment Statuses:

o        Agent Asking Permission - The action or command to the Agent was sent to the Axeda Policy Server for that Agent, and is actively awaiting its permission.

o        Agent shut down - The Agent receiving the deployment shut down before completion.

o        Canceled - The agent received an asynchronous Cancel command (SOAP call) for the package. Note that only a package that is Pending, Queued, or Started can be canceled. If the agent started to process the package, the status changes to Cancel pending, unless the message has not been sent to the asset. In the latter case, the message is removed and the status of the package goes to Canceled immediately.

o        Cancel Pending - A command to cancel the package was sent from the Axeda® Platform but the agent has not yet cancelled the package.

o        Complete - The package has been successfully deployed and run at the asset.

o        Delivered to Agent - The Platform has deployed the package to the agent.

o        Dependency Failed - The in-process dependency failed, and the agent has stopped processing the package.

o        Error - The agent failed at some point while processing the package. The agent reports the error to the application, using a code that indicates the instruction that failed. That error is visible in the lower half of this page. To see it, click the package name in the list of Deployed Packages. When the Selected Package panel appears, click the Assets tab. The Status column contains the text of the error message from the agent.

o        File Upload Inhibited - Custom functionality in the Agent prevented the Agent from uploading files specified in Upload instruction; however, the Agent continued processing with next instruction.

o        Ineligible - The asset, which was included in a scoped deployment, did not pass eligibility criteria. Scoped deployments are based on a list of assets specified for auto-deployment through the Axeda Platform SDK. Eligibility of scoped assets is determined as a first step in the deployment process.

o        Missing - The asset is no longer pinging the Platform. The package could not be deployed.

o        Pending Ask - The agent has asked its Axeda® Policy Server for permission to execute the package and is awaiting permission.

o        Permission Denied - The Axeda Policy Server has denied permission for the agent to execute the package.

o        Queued - The agent has received the package, but has not started to process it. This status occurs when a package is scheduled for a later date/time. The agent places such packages in its queue of packages.

o        Rollback Failed - The agent encountered an error in performing the rollback instructions. The agent includes an error code to indicate which instruction failed.

o        Rollback Successful - The agent has successfully completed the rollback instructions.

o        Rolling Back - The agent encountered an error while processing the package and is performing the rollback instructions as configured in the package, or a user issued the Rollback action from the Package Deployment Manager page.

o        Skipped - The current deployment will not attempt to send the package to these assets. Assets may be skipped for one of the following reasons:

§         The assets are in the process of receiving the same package through an earlier deployment (this also applies to deployments with force redelivery (redeploy) enabled).

§         The deployment has force redelivery disabled, so that when a deployment is sent, assets that have already received the package through another deployment will not receive the package again.

§         Redeploy is invoked on a deployment with a status of cancel pending.

§         The package is for the primary agent, and after the deployment was initiated the asset was switched to backup mode before the deployment reached the asset (and vice versa).

o        Stalled - The Agent did not respond in a timely fashion for a deployment. Deployments may be stalled for one of the following reasons:

§         The Agent is online and eligible for the deployment, but it goes offline and never receives the deployment. The deployment is marked as Stalled when the configured ping rate for the asset is passed 4 times (this is the default, but your Platform administrator may modify this to more or less pings) with no successful deployment.

§         The Agent is in the middle of a deployment, and there is no communication from the Agent.

§         The Platform sends shoulderTap messages to a wireless asset that does not poll frequently, and the Platform reaches the shoulderTap message limit while the asset has still made no contact.

o        Started -The package has been deployed to the asset and, the agent has started processing it.

o        Timed out - One of the package dependencies has not been met during the time allotted; the agent has stopped processing the package. One cause of a time out is that a deployment has remained in a Stalled state for a long period of time (determined by the time out delay value configured by your Platform administrator).

o        Waiting for egress (deployment slot) - The message has been prepared to send to the asset, but it is waiting for a deployment slot.

o        Waiting for evaluation - The asset is being evaluated according to the package dependencies and deployment routing criteria to determine if it is eligible for deployment of the package.

o        Waiting to Deliver - The Platform is waiting to deliver the package to the agent (for example, waiting until the agent contacts the Platform).

Error Codes:

o        An attempt was made to restart an asset behind a gateway - An attempt to restart an asset managed by an Agent was made. A restart action can be directed only at an Agent, and not at an asset managed by the Agent.

o        Archive error - The Agent failed to add or extract files to/from the archive that is used for file transfer during upload/download.

o        Bad SOAP format - The SOAP content for the package is formatted incorrectly.

o        Bad XML file format - The XML content for the package is formatted incorrectly.

o        Bad value quality - The package instructions are defined to write a value to a data item but the value to write is bad.

o        Checksum error - The Agent could not validate the checksum associated with a segment of a downloaded file.

o        Connection failure - The Agent could not connect to the Platform when attempting to transfer files.

o        Data conversion error - The package instructions are configured to write a data value to a data item but the item and the value are different data formats.

o        Data item not found - The agent detected an unknown data item name in a dependency. The specified data item was not found.

o        Data type mismatch - The package instructions are configured to write a data value to a data item but the item and the value are different data formats.

o        Download checksum incorrect - The Agent could not validate the checksum associated with a downloaded file.

o        Downloaded file could not be executed - The Agent could not execute the downloaded file.

o        Duplicate Script Name - The Agent attempted to register a script using a script name already registered.

o        Failed (unspecified failure) - The package has failed with no specified failure.

o        File open error - The file is open and the package cannot be deployed properly.

o        File read error - The Agent Failed in reading or parsing registry file; the dependency cannot be executed.

o        Function not implemented - The package contains a bad function.

o        HTTP failure - The Agent encountered an HTTP error when attempting to transfer files.

o        HTTP status error - The Agent encountered an unexpected HTTP response status when attempting to transfer files.

o        Invalid dependency expression - The package dependency defined for the deployment is not valid.

o        Invalid handle - The handle defined in the instructions for accessing an object in the agent is incorrect.

o        Invalid name - The name defined in the instructions for accessing an object in the agent is incorrect.

o        Invalid parameters - The package instructions contain a script with invalid parameters.

o        Invalid script configuration - The Agent tried to run a script that contains improperly formatted XML commands.

o        Item is read only - A data item defined in the package for writing is read only.

o        Multi-file transfer without compression requested - The Agent cannot upload multiple files without combining them in a compressed file archive.

o        No Error - The Platform did not receive an error code when the package failed.

o        No files found - The Agent could not locate the files needed to complete the deployment (for example, files needed for an upload). If the deployment includes more than one instruction, then this status is appended with the instruction that failed due to the missing files. For example, if the status is "Some files not found (instruction #2)", then one or more files were missing or not found during the deployment, which caused the second instruction to fail.

o        Object already exists - The package instructions are defined to create an object in the agent but that object already exists.

o        Object not found - An object defined in the instructions cannot be located.

o        Operation timed out - The package deployment operation timed out before the package was deployed.

o        Permission Denied (Timeout) - The action or command sent to the Agent was denied because it did not receive approval from the Axeda Policy Server for that Agent within the specified timeout period.

o        Permission Denied - The action or command sent to the Agent was denied based on the permission policies set on that Agent.

o        Permission Granted - The action or command to the Agent was sent to the Axeda Policy Server for that Agent, and was granted permission to be performed.

o        Read error - The Agent encountered an error when reading a file to be uploaded.

o        Registry file read error - The Agent Failed in reading or parsing registry file; the dependency cannot be executed.

o        Registry name not found - The specified registry name was not found.

o        Retry limit exhausted - The asset deployment has gone over its limit for retries. For example, if a restart is initiated when retries are exhausted, the asset deployment is marked by the Platform as Failed with the Platform error code "Retry Limit Exhausted".

o        Script contained invalid command - The Agent tried to run a script that contains an invalid command.

o        Script in Bad State-Bad state - A script is in a bad state on the asset.

o        Script is not running - The Agent attempted to register a script using a script name already registered.

o        Script is running - A script is currently running on the asset.

o        Script was not found - The Agent cannot locate the script it tried to run.

o        Sequence file was not found - The Agent cannot find the sequence file for the script it tried to run.

o        Successful - The Agent successfully processed an action or command sent from the Platform.

o        Script has an empty name - The Agent tried to run a script defined without a script name.

o        Script is waiting - The Agent is waiting to run a script.

o        Script is disabled - The script to run is disabled on the Agent.

o        Script is scheduled already - The Agent tried to register a schedule for a script that already has a schedule.

o        Script is not scheduled - The Agent has a script defined without a schedule.

o        Script is not dynamic - The Agent tried to run a script that does not have an associated dynamic timer.

o        Script finished with error state - The Agent ran a script and that script finished unsuccessfully (in error).

o        Socks failure - The Agent encountered a SOCKS proxy error when attempting to transfer files.

o        Some files not found -  The Agent could not locate some of the files requested for upload. If the deployment includes more than one instruction, then this status  is appended with the instruction that failed due to the missing files. For example, if the status is "Some files not found (instruction #2)", then one or more files were missing or not found during the deployment, which caused the second instruction to fail.

o        Specified directory was invalid - The Agent could not create the specified directory during the file transfer.

o        SSL failure - The Agent encountered an SSL error when attempting to transfer files.

o        The error code returned by the agent is unknown - The Agent returned an unknown error code to the Platform.

o        The SOAP method returned an error - The Platform received an error because a package dependency based on custom components has returned an error.

o        The upload could not be continued; file no longer exists - The Agent could not resume a file upload because the file no longer exists.

o         

o        Unknown SOAP method - The agent did not recognize the SOAP method. Check for a possible misspelling in the package content or a mismatch between the versions of the Agent and the Platform.

o        Unsupported Function - The Platform sent an action or command to the Agent that the Agent does not support.

o        Value out of range - The package instructions are defined to write a value to a data item but the value to write is out of the range of acceptable values for that item.

o        Version - The Agent did not recognize the version of the package format.