Troubleshooting the Experience Optimization installation

If you get stuck installing Experience Optimization, refer to this section for resolutions to common problems.

Query Server could not start on port 1099
Problem: If you install Fredhopper on the same machine as your Content Delivery server, you may get the following error in your qserver.log:
2014-04-02 13:29:09,917 ERROR [NamingService] Could not start on port 1099
The problem may be due to the Cache Channel Service, which runs by default on 1099 (the same as the Query Server). As using Experience Optimization requires you to publish more Dynamic Component Presentations, SDL recommends that you use Content Delivery caching.
Solution: Change the port on which either the Fredhopper Query Server or the Cache Channel Service is running.
Port conflicts
The ports on which your Application Server are running may conflict with ports required by Fredhopper. Modify the ports Fredhopper uses as needed.
Query Server
Restart the Query Server nightly.