Address Verification (On-Premises) 5.12.0
- Address Verification (On-Premises) 5.12.0
- All Products
A pointer parameter was NULL.
A function parameter was 0.
A NULL pointer to an object was used (not relevant for C API).
Two XMLs, one as a string and the other in a file, were entered though only one was required.
The output buffer size is not valid.
Buffer misalignment; an AD_WCHAR* points to an odd address.
A parameter is out of range or is not valid.
An XML string is not valid.
The character sequence of a string is not valid. For example, the string contains control codes or violates some constraint.
The encoding parameter did not match the character size of the API call; for example: UCS2 (16 bit) vs. char (8 bit)
SetConfig.xmlwas entered as parameter for
The engine has already been initialized.
AD_DeInitialize() failed because not all AddressObjects have been released.
No AddressObject is available (all AddressObject handles have already been obtained via AD_GetAddressObject()).
The passed AddressObject handle is not valid.
A database file has not been found.
A database file is invalid/corrupt.
No valid unlock code for a database file.
A database file has a non-supported version.
A feature has not been unlocked.
The country could not be identified or is not supported.
The country is not supported for this processing mode and type of input
Results are available, for this reason no AddressObject modification is allowed.
XML and direct API calls were used intermixed when setting the input data of an AddressObject.
AD_Process() has not been called successfully, no result is available.
The attempted operation was invalid, i.e. trying to set incompatible address elements.
The result index parameter is out of range (must be >= 1).
The output buffer is too small to hold the result, no output was written.
Updated June 08, 2018