Rapidminer Server - Requested repository XXX does not exist..

felix_w
felix_w New Altair Community Member
edited November 5 in Community Q&A
Dear Rapidminer Team, 

I set up a Rapidminer Server via your AWS (BYOL) builds, set up a server repository and connected it to the server. So far so good. 

My problem is now that when I try to run a process I stored in the Rapidminer Server repository I only get fails with this error message: 

Cannot retrieve repository data
Cannot retrieve repository data from entry '//XXX/2 Data/Test1'. Reason: Requested repository XXX does not exist..

I can see the repository in the Web UI and when I run processes locally everything works but as soon as I start the process via the web interface it fails. 

Did I miss to set a certain connection? 

I hope you can help me!

Best regards
Felix
Tagged:

Best Answer

  • mmichel
    mmichel New Altair Community Member
    edited September 2019 Answer ✓
    Hi Felix,

    it seems that you are using absolute paths within the process. So, paths which start with the name of the repository. These processes are not shareable as the repository name might be different on other machines. Instead you should use relative paths. RapidMiner Studio will automatically resolve the data relatively if the process you are building is stored first - otherwise it will use the absolute path strategy as it does not know the storage location of the process.

    So, in a nutshell, change repo locations like this:
    //MyRepoName/data/nominal
    to this (assuming the process is stored in the root level)
    data/nominal

    Cheers,
    Marcel

Answers

  • sgenzer
    sgenzer
    Altair Employee
  • mmichel
    mmichel New Altair Community Member
    edited September 2019 Answer ✓
    Hi Felix,

    it seems that you are using absolute paths within the process. So, paths which start with the name of the repository. These processes are not shareable as the repository name might be different on other machines. Instead you should use relative paths. RapidMiner Studio will automatically resolve the data relatively if the process you are building is stored first - otherwise it will use the absolute path strategy as it does not know the storage location of the process.

    So, in a nutshell, change repo locations like this:
    //MyRepoName/data/nominal
    to this (assuming the process is stored in the root level)
    data/nominal

    Cheers,
    Marcel
  • felix_w
    felix_w New Altair Community Member
    @mmichel: Thank you very much! Now it works :)