To enable logging in the step.0 log for troubleshooting the Loqate and address services, add the following case-sensitive properties to the sharedconfig.properties file.
Important: These settings will create a large number of logging messages and should only be used during initial setup or for short-term troubleshooting.
Errors
An address validation call from STEP to Loqate that results in an error will be indicated on the address itself in the ‘Validation Integration Status’ field with the value: ‘Failed.’
In case of errors, the ‘Validation Response’ field will include an XML element named ‘statusDetails.’ This field will contain the error message that was provided by the Loqate Local server. Of the possible error messages, this one will typically indicate that Loqate was not (properly) installed or not properly configured:
'Since Loqate returned an empty response, some settings might be misconfigured'
For example, this improper install or misconfiguration will occur if the ‘Knowledge Base Common’ data package was not installed. For more information, refer to the Loqate Local Software Install topic here.
Loqate API Testing
The lqtDemo.exe file provides feedback to determine if an issue is with Loqate or with STEP. This file is in the Loqate server folder.
Open the lqtDemo.exe file and provide the location where the data packs have been created.
After setting the data packs location, select the ‘Verify’ tab at the top. This tab allows users to enter an address and test that standardized information is returned. The lower left corner error information displays.
In this example, the GKR location is set to a directory that does not exist.
Below, another address is entered, and returns no errors. This means any issues are not with the Loqate API and reference data installation, but with STEP or the STEP-Loqate connection (for example, a misconfiguration in sharedconfig.properties file).
