Are you seeing this error on other services? This error should be unrelated to your authorization mechanism (OAuth2).
Can you try downloading the wsdl from the server using wget or something. Then checking it's formed correctly. Finally modify your application so that it reads the WSDL from your local machine. We're not getting reports of this error from other customers, so the wsdl should be available and correct. Regards, - Paul, AdWords API Team. On Wednesday, 8 January 2014 14:54:56 UTC, Mehul HvInfotech wrote: > > Hello Paul, > > We are using version > > *v201309 with ClientLogin. Also tested with OAuth2.*We are getting this > error, > > SOAP-ERROR: Parsing WSDL: Couldn't load from ' >> https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' >> : failed to load external entity " >> https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl"; >> > > Our server has OpenSSL Enabled in php.ini and we have also tested > connection between our server to google adwords as, > > openssl s_client -connect adwords.google.com:443 >> >> > Kindly check & Let us know ASAP. > > Thanks, > > > > On Wednesday, 8 January 2014 19:52:26 UTC+5:30, Paul Matthews (AdWords API > Team) wrote: >> >> If you're still requesting the WSDL you listed before, you'll be hitting >> this problem because the v201302 has >> sunset<https://developers.google.com/adwords/api/docs/sunset-dates> - >> you would need to update to a current version of the AdWords API. >> >> If you've updated to a working API version then as Evgeniy suggested, you >> should try to download the WSDL from the URL yourself: >> >> 1. Download the >> wsdl<https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl>and >> store it somewhere accessible locally on your webserver >> 2. Point your application to the local wsdl rather than the URL it >> will currently have >> 3. Make a request & check the soap logs >> >> Regards, >> >> - Paul, AdWords API Team. >> >> On Wednesday, 8 January 2014 12:50:08 UTC, Mehul HvInfotech wrote: >>> >>> Do you means by setting.ini ? >>> we have tried with all tree option for this ... >>> >>> >>> >>> On Wednesday, 8 January 2014 14:37:02 UTC+5:30, Evgeniy Bogdanov wrote: >>>> >>>> You could save WSDL on local disk and alter library to use it instead >>>> of remote URL. >>>> >>>> >>>> 2014/1/8 Mehul HvInfotech <me...@hvinfotech.com> >>>> >>>>> Hi Paul , >>>>> Again From This Morning we are facing this problem .. >>>>> Till the the Day it was working fine .. >>>>> we have also checked about Open SSL enabled And it is enabled ... >>>>> >>>>> can you suggest in this , Please , Its so urgent ... >>>>> >>>>> >>>>> On Wednesday, 3 April 2013 15:47:38 UTC+5:30, Paul Matthews (AdWords >>>>> API Team) wrote: >>>>>> >>>>>> Hi Mahesh, >>>>>> >>>>>> *Firstly:* >>>>>> Have you enabled WSDL_CACHE? We've had reported issues where caching >>>>>> of WSDLs has caused errors. Can you try turning it off and making the >>>>>> same >>>>>> number of requests. This setting is configurable in the >>>>>> settings.ini<https://code.google.com/p/google-api-adwords-php/source/browse/src/Google/Api/Ads/AdWords/settings.ini>. >>>>>> >>>>>> *Secondly:* >>>>>> This kind of problem is generally due to connectivity issues between >>>>>> the client server and the google servers. Often caused by either >>>>>> a miss-configured network proxy or a network issue. You may need to do >>>>>> some >>>>>> investigation to see if there is a network issue there. >>>>>> >>>>>> *Finally:* >>>>>> I recommend building in fault tolerance, to allow you to retry the >>>>>> failing request. I.e. whenever a request fails, it waits and retries the >>>>>> original request - such as the exponential backoff >>>>>> algorithm<http://en.wikipedia.org/wiki/Exponential_backoff> >>>>>> . >>>>>> >>>>>> Regards, >>>>>> >>>>>> - Paul, AdWords API Team. >>>>>> >>>>> -- >>>>> -- >>>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >>>>> Also find us on our blog and discussion group: >>>>> http://googleadsdeveloper.blogspot.com >>>>> http://groups.google.com/group/adwords-api >>>>> =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ >>>>> >>>>> You received this message because you are subscribed to the Google >>>>> Groups "AdWords API Forum" group. >>>>> To post to this group, send email to adwor...@googlegroups.com >>>>> To unsubscribe from this group, send email to >>>>> adwords-api...@googlegroups.com >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/adwords-api?hl=en >>>>> --- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "AdWords API Forum" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to adwords-api...@googlegroups.com. >>>>> For more options, visit https://groups.google.com/groups/opt_out. >>>>> >>>> >>>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://googleadsdeveloper.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
