Skip to main content

Shopping

Application requests are going to the wrong client

Depending on which component is installed and working, the following is the fallback behavior for the Shopping website when it attempts to get information from the local computer:

  1. It tries to access the Shopping Agent web service – it has the widest support across existing and more recent browser releases.

  2. If for any reason the web service is not available, and the browser supports ActiveX or NPAPI, it will try to access the Shopping Client Identity component.

  3. If both the above fails, it will use the IP Address and reverse DNS lookup to identify the machine so that details may be retrieved from Configuration Manager.

So, if the application request is not going to the correct client, you may want to:

  1. Check for Reverse DNS Lookup issues and incorrect PTR records in Active Directory as they are the most probable causes for this to happen.

  2. Check if there are multiple SMS GUIDs for the same machine in ConfigMgr.

  3. Always ensure that latest version of 1E Client with the Shopping module is installed and enabled and configured correctly on all client machines.

  4. Check the 1E ShoppingAgent.log on the client machine, typically located in C:\ProgramData\1E\ShoppingAgent, for further details

In this section: