enter image description here

I am getting above error while starting SDL SmartTarget 2011 SP1. Please assist me..

  • Is your Fredhopper installed on the same server as Tridion/SmartTarget? – Philippe Conil Jul 3 '15 at 6:44
  • yeah...it is already installed – Habeeb Jul 3 '15 at 6:48
  • Is your fredhopperUrl correct in TRIDION_HOME\web\SmartTarget\smarttarget.xml ? And can you access that Url directly e.g. – Philippe Conil Jul 3 '15 at 6:52
  • i can't access it directly. – Habeeb Jul 3 '15 at 6:59
  • Please follow this part of the documentation: bit.ly/1NAYdrX you need to start the Fredhopper query server. – Philippe Conil Jul 3 '15 at 7:14

That error message is shown if it cannot connect to the Fredhopper URL configured in SmartTarget.xml (in TRIDION_HOME\web\SmartTarget).

So double-check that the URL is correct and that the Fredhopper instance is up and running.

| improve this answer | |
  • i couldn't connect to fredhopper when i enter localhost:8180/fredhopper/admin – Habeeb Jul 3 '15 at 9:34
  • You need to start the instance. See the following page in the documentation: docs.sdl.com/LiveContent/content/en-US/SDL_SmartTarget_2011_SP1/… – Peter Kjaer Jul 3 '15 at 9:42
  • i have started through my command line but it giving the below error. – Habeeb Jul 3 '15 at 10:00
  • D:\fredhopper\instance01\FAS\bin>startloader The system cannot find the path specified. No universes given, and autodetection failed. Please run this script from the base directory of Usage: startloader [-I instance] [universe...] – Habeeb Jul 3 '15 at 10:00
  • As I commented on above, you need to run it from the FAS folder not the \bin folder. – Peter Kjaer Jul 3 '15 at 10:02

Looks like your fredhopper is stopped hence you are getting this error. Try after starting deployment agent and your indexer service.

| improve this answer | |
  • which service i have to start plz suggest me. – Habeeb Jul 3 '15 at 9:35
  • for deployement agent type bin\deployment-agent from your fredhopper base directory. wait for around 90 sec andtype bin\instance <indexer> start in a new command prompt. – Harish Sharma Jul 8 '15 at 11:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.