Forums › Forums › OroCRM › OroCRM – Installation/Technical Issues or Problems › Magento Channel correct configuration
January 15, 2014 at 4:49 am #25846
i use Magento 126.96.36.199.
i’ve tried to configure the Magento channel with the following settings:
Soap wsdl Url: http://mymagentohost/index.php/api/v2_soap/?wsdl
and other link
Soap api user: api_user
New soap api key: password
Sycn start date: Jan 14, 2014
The Result is everytime “parameters are not walid”
Can anyone help for the right configuration?
January 15, 2014 at 5:05 am #25847
You should use v2 Magento API, so first URL seems to be correct.
Did you add this api_user in “System -> Web services -> SOAP/XML-RPC – Users” Magento admin panel and assign this user all necessary roles?
Let us know if this is the case and you still in trouble.January 15, 2014 at 6:03 am #25848
yes i do this before i configured the magento channel.
SOAP/XML-RPC = api_user
Role Resources = Resource Access (all)January 16, 2014 at 4:08 am #25849
Possible cases are:
1. wrong API credentials (username, api key, password or wsdl url), check that you’re able to get this url from your browser and from host where OroCRM installed.
2. SoapClient unable to parse wsdl
3. SoapClient unable to perform request or get malformed response
4. Some chances you have unique case where our system crashed
Anyway, here’s a patch http://pastebin.com/A3sH7HVb that add logging for this error,
if you apply this, you will be able to check for “MageCheck error …” message in app/logs/prod.log (or dev.log, depending on your environment).
Here’s how to apply it:
git apply channel-conn-log.patch
And here’s how to check your potentially big log:
cat app/logs/prod.dev | grep MageCheck
Please provide error log or error message when you do this. Thank you.January 16, 2014 at 8:02 am #25850
thanks for your feedback.
i’ve edit the file for the log.
The the message is unfortunately still “parameters are not valid”
“app.CRITICAL: MageCheck error: 0: Error cannot find parameter  ”January 16, 2014 at 11:04 am #25851
I guess that you are using WS-I mode, in some reasons our integration incompatible with this mode. We are looking for good solution. Please try to disable it in magento(System -> Configuration -> Magento Core API) I will keep you posted.
Thanks for reporting an issue.April 16, 2014 at 2:20 pm #25852
This is almost identical to the issue I’m getting – can’t get the Magento connector to work.
I found this in the logs:1app.CRITICAL: MageCheck error: 0: SOAP-ERROR: Parsing WSDL: Couldn't load from 'mydomain.co.uk/api/soap/?wsdl' : failed to load external entity "mydomain.co.uk/api/soap/?wsdl"
I checked, and WS-I mode is disabled. I can also ran:1wget mydomain.co.uk/api/soap/?wsdl
from the command line, and it retrieved what seems to be perfectly well-formed XML.
I guess it all works via port 80? I’m port-forwarding through my router for this, so there might be an issue there.
Really keen to hear any ideas!
TonyApril 16, 2014 at 2:34 pm #25853
Please use SOAP V2 (mydomain.co.uk/api/v2_soap?wsdl=1)April 16, 2014 at 3:51 pm #25854
Staggering on a little – that got past the current issue – now getting:123456789[2014-04-16 23:27:43] security.DEBUG: Read SecurityContext from the session  [2014-04-16 23:27:43] security.DEBUG: Reloading user from user provider.  [2014-04-16 23:27:44] security.DEBUG: Username "xxx" was reloaded from user provider.  [2014-04-16 23:27:44] security.DEBUG: Invoked controller "OroCRM\Bundle\MagentoBundle\Controller\SoapController::checkAction". (MASTER_REQUEST)  [2014-04-16 23:27:44] security.DEBUG: Check an access using "oro_integration_channel_update" ACL annotation.  [2014-04-16 23:27:44] security.DEBUG: ACL found, permission granted. Voting to grant access  [2014-04-16 23:27:45] app.CRITICAL: MageCheck error: 0: looks like we got no XML document  [2014-04-16 23:27:45] security.DEBUG: Write SecurityContext in the session  
I’m using an API ID I set up with all access. I did notice though that deliberately getting the API user and key wrong makes no difference to the error I’m getting. I tried using http://mydomain.com/api.php?type=v2_soap&wsdl=1 so I could rename .htaccess to check that wasn’t messing things up, but again it returned the error above.
Interestingly, when I used “http://mydomain.com/api.php?type=v2_soap&wsdl=1” in SoapUI and looked at the example “login” call, it seemed to be posting to http://mydomain.com/index.php/?type=v2_soap, and getting HTML back for the home page. Changing this manually to “http://mydomain.com/api.php?type=v2_soap” and posting to that resulted in the error “<faultstring>SOAP-ERROR: Parsing WSDL: Couldn’t load from ‘http://mydomain.com/index.php/?type=v2_soap&wsdl=1’ : Extra content at the end of the document</faultstring>”
This does seem to come from the WSDL:12345<service name="MagentoService"><port name="Mage_Api_Model_Server_V2_HandlerPort" binding="typens:Mage_Api_Model_Server_V2_HandlerBinding"><soap:address location="http://mydomain.com/index.php/?type=v2_soap"/></port></service>
Thanks for any help. I’ve burned many, many hours trying to get this all set up.
TonyOctober 23, 2014 at 5:52 am #25855
I’m having the same “parameters not valid” issue.
– Setup the role, user and applied the role to the user
– Using this for the SOAP URL – http://mydomain.com/index.php/api/v2_soap/?wsdl=1
– Double checked the username and password
– WS-I Compliance set to no in System -> Configuration -> Magento Core API
This is Magento CE 188.8.131.52. Anyone find a solution to this yet?October 23, 2014 at 7:13 am #25856
Hi every one!
@nvanprooyen could you please share error message from log file in order to find out what happens ?
@tony7671 it seems for me that your url is not correct it should be http://mydomain.com/index.php/api/v2_soap/?wsdl=1 otherwise url that you tried will be rewritten by webserver to index.php/?type=v2_soap&wsdl=1 because api.php file is not exist.October 23, 2014 at 7:45 am #25857
Thanks for the quick reply Alexandr. We ended up getting it worked out. It was htaccess denying the connection.March 8, 2015 at 11:56 pm #25858
I met the same issue as above, my site is running on nginx, so how should i do with nginx config?June 8, 2015 at 3:43 am #25859
First of all (as it’s my first post) I’d like to thank you for OroCRM and OroCRM Bridge!
I have installed OroCRM, Magento and OroCRM Bridge, OroCRM Tracking plugin also I have created “connection” between them and now can’t work around error like tony7671’s one.
This is the error I get on “Integrations” page in OroCRM:
[message] SOAP-ERROR: Parsing WSDL: Couldn’t load from ‘http://646100.nightmar.web.hosting-test.net/index.php/api/v2_soap/index/?wsdl=1’ : failed to load external entity “http://646100.nightmar.web.hosting-test.net/index.php/api/v2_soap/index/?wsdl=1″
[request] <?xml version=”1.0″ encoding=”UTF-8″?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/” xmlns:ns1=”urn:Magento” xmlns:xsd=”http://www.w3.org/2001/XMLSchema” xmlns:xsi=”http://www.w3.org/2001/XMLSchema-instance” xmlns:SOAP-ENC=”http://schemas.xmlsoap.org/soap/encoding/” SOAP-ENV:encodingStyle=”http://schemas.xmlsoap.org/soap/encoding/”><SOAP-ENV:Body><ns1:storeList><sessionId xsi:type=”xsd:string”>4e4b3450cb6a08ed55e796cb2fcdab1d</sessionId></ns1:storeList></SOAP-ENV:Body></SOAP-ENV:Envelope>
[response] <?xml version=”1.0″ encoding=”UTF-8″?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV=”http://schemas.xmlsoap.org/soap/envelope/”><SOAP-ENV:Body><SOAP-ENV:Fault><faultcode>WSDL</faultcode><faultstring>SOAP-ERROR: Parsing WSDL: Couldn’t load from ‘http://646100.nightmar.web.hosting-test.net/index.php/api/v2_soap/index/?wsdl=1’ : failed to load external entity “http://646100.nightmar.web.hosting-test.net/index.php/api/v2_soap/index/?wsdl=1”
I have googled it well and found nothing to help me to fix it.
Will be glad to get any help.
P.S. I’m running OroCRM on VPS server, it was very hard for me to configure it and I think server can be a problem. And magento is running or shared hosting.
P.P.S. Here is screnshot of my error:
The forum ‘OroCRM – Installation/Technical Issues or Problems’ is closed to new topics and replies.