Error Messages for the Version or Property Dependency
Error Messages with Scenarios
For the version dependency:
|
Scenario
|
Error Message
|
|---|---|
|
If you create a version dependency for a package with the operator (> ) but nothing is installed.
|
Version dependency check failed for package "TestPackage123". Dependency value is expected to be > [1.0.0.0].
|
For the property dependency:
|
Scenario
|
Error Message
|
|---|---|
|
If you create a dependency with the property XYZ, but the property XYZ does not exist on the thing.
|
Property Dependency check failed for property “ModelProperty“. Property does not exist.
|
|
If you create a dependency with a string property and the operator (>.)
|
Property dependency check failed for property " ModelProperty". Operator < cannot be applied on property of type STRING.
|
|
If the value on the thing and the value in the dependency are different for the operator (< )
That is, for a scenario when the condition checks that the value in the asset is smaller than the value in the dependency, and that condition is not fulfilled.
For example, the dependency value is expected to be < [2.0] , but value is [3.0] on the asset.
|
Property dependency check failed for property "My_InMemory_Number".
|
|
If the value type in the dependency and on the thing are different.
|
Property dependency check failed for property " ModelProperty ". Value [STRING] is incompatible with asset property type NUMBER.
|
Common Errors in Instruction-based Packages
For instruction-based packages, if the property is remote or empty, it is evaluated on the Axeda agent and you can get different errors, with numbers. A list of some errors with their description is given in the table below.
The format of an error is Error received: <description>[<error code>].
For example: Error received: Data item not found [ec =5].
 |
If there is no description, the error is displayed like this: Error received: Unrecognized error received [<error code>]
|
The following is a list of possible errors:
|
Error Code
|
Description
|
|---|---|
|
ec = -2
|
The error code returned by the agent is unknown
|
|
ec = -1
|
No error
|
|
ec = 0
|
Failed
|
|
ec = 1
|
Version
|
|
ec = 2
|
Bad XML format
|
|
ec = 3
|
Unknown SOAP method
|
|
ec = 4
|
Unsupported function
|
|
ec = 5
|
Data item not found
|
|
ec = 6
|
Registry name not found
|
|
ec = 7
|
Registry file read error
|
|
ec = 8
|
Invalid dependency expression
|
|
ec = 9
|
No files found
|
|
ec = 10
|
Some files not found
|
|
ec = 11
|
Downloaded file could not be executed
|
|
ec = 12
|
Archive error
|
|
ec = 13
|
Read error
|
|
ec = 14
|
HTTP status error
|
|
ec = 15
|
Checksum error
|
|
ec = 16
|
Connection failure
|
|
ec = 17
|
Socks failure
|
|
ec = 18
|
HTTP failure
|
|
ec = 19
|
SSL failure
|
|
ec = 20
|
Agent shutdown
|
|
ec = 21
|
Download checksum incorrect
|
|
ec = 22
|
The upload could not be continued; the file no longer exists
|
|
ec = 23
|
Specified directory was invalid
|
|
ec = 24
|
An attempt was made to restart an asset behind a gateway
|
|
ec = 25
|
The SOAP method returned an error
|
|
ec = 26
|
Multi-file transfer without compression is requested
|
|
sc = 5
|
The package execution timed out on the asset side. Please check the asset’s logs.
|
|
sc = 11
|
The dependency check failed on the asset side. Please re-check the package dependencies.
|
|
sc = 14
|
The asset denied package execution. Please check the asset policies.
|