Invalid API path

Asked by Vivek poddar on 2012-06-15


I have installed the magento-extension as well as OpenERP side modules. I installed the core modules in OpenERP and I was also able import all the product categories, but the problem started when I wanted to do "Synchronize Referential Settings". I am getting: <Fault 3: 'Invalid api path.'>. I am bit stuck here because it seems that all the further settings depends on this step.

Question information

English Edit question
Magento OpenERP Connector Edit question
No assignee Edit question
Solved by:
Vivek poddar
Last query:
Last reply:
Vivek poddar (vivekimsit) said : #1

One more thing! when I tried manually to connect to the resources: ol_websites.list and ol_stores.list, I get the same error.

Vivek poddar (vivekimsit) said : #2


Now I this is really frustating. For a single project there a n numbers of the versions, code repository and everything is so scattered. To use Magento I simply used this key which I got from: and it not installs properly! some config files were missing for which I spend hours to search what is going on. Guys please remove all the code which are absolete now.

     Cheers to me! As I solved the issue myself. :)

JOVICYR (jovicyr) said : #3

Hi Vivek,

I installed the connector :

And proceed to importation.
Steps 1 to 5 work
But I got an error on step 6 importation products : the same as yours :
Fault: <Fault 3: 'Invalid api path.'>

Could you tell me how you fix it ?
Thanks a lot for your kind answer,


Brett Lehrer (brett-lehrer) said : #4

So how did you solve it? I'm seeing the exact same problem as JOVICYR on the exact same step (when importing products).

Any help would be much appreciated.


JOVICYR (jovicyr) said : #5


I downloaded latest release, both of magento module and OpenERP dependencies.
And, check that no zip file still exist in addons folder.

Brett Lehrer (brett-lehrer) said : #6

Ahh, I made the mistake of using the Magento module from the Magento Connect website (which hasn't been updated since February). Downloading the trunk of the module and installing it manually in Magento solved that problem, thank you.