Device Data Sync Errors in Transactions¶

The DataSync from a device has two steps:

A list request for all the resources of a specific type is made, for example for a User or Phone.
Requests for detailed information of each resource of the specific type.

The tables below show errors raised by devices and how these are handled or written to the transaction log by VOSS Automate. In the case of failed transactions, the tables point to possible causes of some errors.

Note

A number of CUCM device model errors are non-critical and will not fail data sync transactions.

CUCM AXL handled by VOSS Automate (DataSync transaction final status is not failed)

Model	Operation	Device Error Message Match	VOSS Automate DataSync Action and/or error log
LocalRouteGroup	GET	No Search Criteria Defined	Ignored known error
LdapDirectory	GET	Item not valid: The specified LdapDirectory was not found	Ignored known error
UniversalDeviceTemplate	GET	Item not valid: The specified UniversalDeviceTemplate was not found	Ignored known error
LicensedUser	GET	Item not valid: The specified LicensedUser was not found’,’The endpoint reference (EPR) for the Operation not found is No License found for the specified user: Could not open database table	Ignored known error
LdapSyncCustomField	GET	Invalid ldapConfigurationName	Ignored known error
EndpointReleaseKey	GET	Column (name) not found in any table in the query (or SLV is undefined)’,’The endpoint reference (EPR) for the Operation not found is	Ignored known error
DirNumberAliasLookupan dSync	GET	Item not valid: The specified DirNumberAliasLookupandSync was not found	Ignored known error
DeviceSerialNumber	GET	endpoint reference (EPR) for the Operation not found is	Ignored known error
LicenseCapabilities	GET	The endpoint reference (EPR) for the Operation not found is	Ignored known error
PhoneTypeDisplayInstance	GET	Wrong value for Protocol. Please enter a valid value.	Not all Phone Types have Vendor Config Rules. Ignored.

HCMF handled by VOSS Automate (DataSync transaction final status is not failed)

Model	Operation	Device Error Message Match	VOSS Automate DataSync Action and/or error log
TransportModeSettings	GET	API Call Error [404]	Ignored known error
SmartAccountsAccessCredentials	GET	API Call Error [404]	Ignored known error

CUCM Device errors not handled by VOSS Automate (DataSync transaction final status is failed)

Model	Operation	Model Error	Possible Cause
(All model types)	GET	Resource not found	A workflow in VOSS Automate deleted an item between the DataSync LIST operation and the GET operation
(All model types)	GET	AXL Error [-1]	This is a non-specific error raised by CUCM. Follow up with the CUCM team.

CUC Device errors not handled by VOSS Automate (DataSync transaction final status is failed)

Model	Operation	Model Error	Possible Cause
(All model types)	GET	Resource not found	A workflow in VOSS Automate deleted an item between the DataSync LIST operation and the GET operation
ImportUser	GET	Resource not found	A sync between CUC and LDAP is running at the same time as the VOSS Automate sync to CUC. If the User is disabled or deleted on LDAP, then the User would removed as an Import User on CUC. A workflow on VOSS Automate promoted a user from Import User to User by creating a Voicemail Box for that User, which also causes the user to be removed as Import User and created as a full User.

VOSS Automate 21.2

Device Data Sync Errors in Transactions¶