SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity

[Mahesh]

Hello All,
we are getting the Soap Error During the Google Campaign pause event with Api ..
We are using version v201309
The Original Error is as below

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"

we have Checked for Open SSL enabled Or not.. So It is Enabled we checked by printing phpinfo().

The Variable for Open SSL is showing as below ..

Can any one suggest in this ?

[दिपक मोक्तान]

Hi,

Can you confirm if
  parse_ini_file function is not disabled.


This can be checked directly on phpinfo output or in phpp.ini file. You can search the same string on both cases.

[Ray Tsang (AdWords API Team)]

Hi Mehul,

Could I trouble you to try to fetch the WSDL directly from the server with something like wget or curl and copy/paste the full output?

E.g., `curl -v https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl`

Furthermore, will you be able to fetch the WSDL using wget or curl from a different server?

Thanks!

[Mathis Lübbers]

Hello! I have the same problem. Is there any solution?

[Ray Tsang (AdWords API Team)]

Mathis,

Please confirm if you can fetch the URL via curl or wget.  If not, please post the responses. 

Thanks

--

Ray Tsang (AdWords API Advisor)

[Mathis Lübbers]

Yes, I can fetch the URL via curl,

Mathis

[Ray Tsang (AdWords API Team)]

Mathis,

Just to be sure - you were able to fetch the URL via curl from the same machine that was throwing SOAP-ERRORS?

Could I also trouble you to paste the error log regarding SOAP-ERROR?

Thanks,

--

Ray Tsang (AdWords API Advisor)

[Mathis Lübbers]

I got the following output when I try to fetch the URL via curl:

see addition

[Ray Tsang (AdWords API Team)]

Mathis,

That sounds right.  But, are you still receiving errors from the client library?  If so, I'd need the error log generated from the client library (without any sensitive information), and I'll need your help to confirm if curl was able to run successfully from the same machine that ran the client library.

Thanks,

Ray

[Mathis Lübbers]

Hey Ray,

thank your for your response!

I think, I have you to tell the whole problem again, because I've made a mistake in the discription of the problem, sorry therefore!

We have installed the API with it's configurations on two different machines (A,B) using these steps:

download the current php library 

create MCC production account (developer token in auth.ini)

create MCC test account (creat client --> client costumer ID in auth.ini)

create Project at Google Developers Console (client ID , clientSecret in auth.ini)

get RefreshToken --> insert in auth.ini

uncomment       extension=php_openssl.dll

                           extension=php_curl.dll

                           extension=php_soap.dll        in php.ini (on Machine A in php.ini-developement and php.ini-production, too)

             

tried GetCampaigns on two different machines and got two different errors.

Machine A : 

An error has occurred: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adw

ords.google.com/api/adwords//api/adwords/cm/v201309/CampaignService?wsdl' : fail

ed to load external entity "https://adwords.google.com/api/adwords//api/adwords/

cm/v201309/CampaignService?wsdl"

Machine B:

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /Applications/XAMPP/xamppfiles/htdocs/adwordsapi/src/Google/Api/Ads/Common/Util/Logger.php on line 236

Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone. in /Applications/XAMPP/xamppfiles/htdocs/adwordsapi/src/Google/Api/Ads/Common/Util/Logger.php on line 236

An error has occurred: [QuotaCheckError.INCOMPLETE_SIGNUP @ ; trigger:'<null>']

In both cases we got no soap_xml.log files in the Basic_Operations folder.

On machine A curl doesn't run successfully, but on machine B it does. (So I wasn't able to fetch the URL via curl from the same machine that throws SOAP ERROR, I'm sorry for this confusion!)

When we tried to fetch the URL (https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl) via curl we got:

see Addition (Machine_A.txt, Machine_B.text)

We are very grateful for your help!

[Ray Tsang (AdWords API Team)]

Mathis,

This is great:

Machine A: there is a bigger issue here w/ the machine setup if curl doesn't work at all.  It could be caused by many many factors that's outside of my expertise.

Machine B: regarding the date function error, please make sure you have set a default timezone.

For INCOMPLETE_SIGNUP_ERROR, please send me your MCC's CID and the AW CID that you are accessing in private (respond to author).

Thanks!

--

Ray Tsang (AdWords API Advisor)

[Ray Tsang (AdWords API Team)]

Mathis,

Following up on your private thread - 

Machine A: even though curl works, it appears you may have additional environmental issues that's behind my expertise.  Please make sure both machines are setup with the same versions and configurations of PHP, etc.

Machine B: did you use a developer token from a production MCC?  Please send me the MCC CID.

Thanks,

[Mathis Lübbers]

Hi,

I solved the problem regarding the SOAP-ERROR with deinstalling xampp and installing it again without running any anti-virus program or User Account Control.

Maybe someone has the same problem.

Now logically, we have the incomplete sigUp error on both machines. I've sent you my production MCC CID in private. 

Thanks!

[Ray Tsang (AdWords API Team)]

Mathis,

Please see our sign up guide to make sure you have a completed billing and T&C setup.

Secondly, the the developer token has not been approved - have you submitted the new token form?

The developer token can only be used with test accounts prior to its approval.  Please visit our test account guide for more info.

Thanks!

Ray

[Mathis Lübbers]

I wanted to test GetCampaigns.php with the test account and I've done all the things that are required (developer token from production MCC)

I have completed billing and T&C setup in production and test account, but still there's the incomplete-signUp-error.

I can't understand why I am still getting this error.

Thanks a lot!

[Joseph Collins]

Ray,

I have only seen this issue appear when Google's load balancer directs traffic to 173.194.115.0/24. This issue affects adwords.google.com, google.com, gmail.com, youtube.com, etc. with both HTTP (cURL feedback: Recv failure: Connection was reset) and HTTPS (cURL feedback: Unknown SSL protocol error in connection) requests via cURL, Telnet and Google Chrome.

The issue has been consistently reproduced in every big network (Comcast, Limestone Networks, Amazon AWS and several unknowns via VPN) accessible to me.

The failure rate on 173.194.115.0/24 was roughly 70% over ~200 requests.

[Ray Tsang (AdWords API Team)]

Mathis,

I've sent you a T&C.  Please follow up in that the private thread.

Cheers,

Ray

[Joseph Collins]

I can only reproduce this issue on Windows Server 2012; all requests to 173.194.115.0/24 in Linux work fine.

For those affected by these errors, I have had success using a static host address for adwords.google.com (http://en.wikipedia.org/wiki/Hosts_(file)) that is not contained in 173.194.115.0/24 (keeping pinging adwords.google.com until you receive one).

[Ray Tsang (AdWords API Team)]

Joseph,

That's an interesting find.  Could I trouble you to elaborate more your use cases?

Thanks,

Ray

[Mathis Lübbers]

The example GetCampaigns.php is now runnnig successfully with my  mcc test account.

Thank you very much for your help, Ray!

[Ray Tsang (AdWords API Team)]

That sounds great.  Cheers.

Ray