Troubleshooting POS Parameters
This section describes steps for troubleshooting the possible issue related to the parameter data of POS terminals.
Error loading parameters
When attempting to reload parameters, the POS displays an error message that the POS has failed to retrieve parameter data from the store.
Possible causes
The POS may fail to load parameters due to any of the following factors:

During the enterprise batch apply process, the POS is pre-configured with a set of technical users. Through token-based authentication, the technical user credentials provide secured communication between the POS application and the Enterprise Web Server. For more information, refer to Job roles. If the POS technical user is locked, the POS cannot retrieve parameter data from the Enterprise.
Solution
NCR recommends resetting the POS technical user password to its default password value. For more information, refer to POS technical user is locked out.

The POS terminal is offline or has limited internet connection.
Solution
Ensure that the POS has active internet connection.

The EOM Server cannot connect to the RabbitMQ Server due to misconfiguration during installation.
Solution
Verify if the EOM host name in the RabbitMQ server is correct. For more information, refer to Validating the RabbitMQ EOM Host Configuration.

The time period pre-configured for the parameter data retrieval process between the Web Server and a POS terminal is a maximum limit of 30 seconds. If the data retrieval process is not completed within this time period, the POS terminal displays an error message that the parameter data reload has failed.
Solution
Increase the maximum timeout period for the data retrieval process between the Web Server and the POS terminal. This solution requires modifying specific definition tags in the following files.
Definition tag | File name | File location | Directory |
---|---|---|---|
Options channel timeout value | CommunicationManager.xml | POS terminal | %PROGRAMFILES%\NCR\AdvancedStore\POS |
EnterpriseOptions channel timeout value | CommunicationManager.xml | POS terminal | %PROGRAMFILES%\NCR\AdvancedStore\POS |
LocalParametersHttpHandler timeout value | POSClientConnectionManager.xml | POS terminal | %PROGRAMFILES%\NCR\AdvancedStore\POS |
Options timeout value | web.config | Web Server machine | C:\inetpub\wwwroot\NCRRetailOne |
The definition tags must be modified in the order specified in the table above. The timeout value of each definition tag must be at least one second less than the timeout value of the preceding tag. NCR recommends using the following sample setting as a basis for the timeout values configuration:
- Set the Options channel timeout value to 40 seconds.
- Set the EnterpriseOptions timeout value to 39 seconds.
- Set the LocalParameterHttpHandler timeout value to 38 seconds.
- Set the Options timeout value to 37 seconds.
Follow these steps on each component and in the following order:

Configuring the Options and EnterpriseOptions timeout values
Follow these steps:
- Open the CommunicationManager.xml file using a text editor.
- In the <Messages> section, configure the channelTimeout value of the following definition tags as preferred:
- Options
- EnterpriseOptions
- Save the changes.
Configuring the LocalParametersHTTPHandler timeout value
- Open the POSClientConnectionManager.xml file using a text editor.
- In the LocalParametersHTTPHandler plugin configuration section, add the timeout line with the preferred timeout value in seconds:
<timeout>38000</timeout>
NoteThe value for this attribute assumes three decimal places. This example specifies 38 seconds as the timeout value. Configure the value as preferred.
- Save the changes.

Follow these steps:
- Open the web.config file using a text editor.
- In the <appSettings> section, add the OptionsTimeout line with the preferred timeout value in seconds:
<add key="OptionsTimeout" value="37"></add>
NoteThis example specifies 37 seconds as the OptionsTimeout value. Configure the value as preferred.
- Save the changes.