Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
That sounds great. Cheers. Ray On Monday, March 10, 2014 3:54:58 PM UTC-4, Mathis Lübbers wrote: The example GetCampaigns.php is now runnnig successfully with my mcc test account. Thank you very much for your help, Ray! Am Montag, 10. März 2014 16:07:13 UTC+1 schrieb Ray Tsang (AdWords API Team): Joseph, That's an interesting find. Could I trouble you to elaborate more your use cases? Thanks, Ray On Friday, March 7, 2014 6:36:15 PM UTC-5, Joseph Collins wrote: I can only reproduce this issue on Windows Server 2012; all requests to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcgin 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/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg(keeping pinging adwords.google.com until you receive one). On Friday, March 7, 2014 1:18:10 PM UTC-5, Joseph Collins wrote: Ray, I have only seen this issue appear when Google's load balancer directs traffic to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg. 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. On Wednesday, March 5, 2014 5:09:40 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
I can only reproduce this issue on Windows Server 2012; all requests to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcgin 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/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg(keeping pinging adwords.google.com until you receive one). On Friday, March 7, 2014 1:18:10 PM UTC-5, Joseph Collins wrote: Ray, I have only seen this issue appear when Google's load balancer directs traffic to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg. 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. On Wednesday, March 5, 2014 5:09:40 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
Joseph, That's an interesting find. Could I trouble you to elaborate more your use cases? Thanks, Ray On Friday, March 7, 2014 6:36:15 PM UTC-5, Joseph Collins wrote: I can only reproduce this issue on Windows Server 2012; all requests to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcgin 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/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg(keeping pinging adwords.google.com until you receive one). On Friday, March 7, 2014 1:18:10 PM UTC-5, Joseph Collins wrote: Ray, I have only seen this issue appear when Google's load balancer directs traffic to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg. 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. On Wednesday, March 5, 2014 5:09:40 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
The example GetCampaigns.php is now runnnig successfully with my mcc test account. Thank you very much for your help, Ray! Am Montag, 10. März 2014 16:07:13 UTC+1 schrieb Ray Tsang (AdWords API Team): Joseph, That's an interesting find. Could I trouble you to elaborate more your use cases? Thanks, Ray On Friday, March 7, 2014 6:36:15 PM UTC-5, Joseph Collins wrote: I can only reproduce this issue on Windows Server 2012; all requests to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcgin 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/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg(keeping pinging adwords.google.com until you receive one). On Friday, March 7, 2014 1:18:10 PM UTC-5, Joseph Collins wrote: Ray, I have only seen this issue appear when Google's load balancer directs traffic to 173.194.115.0/24http://www.google.com/url?q=http%3A%2F%2F173.194.115.0%2F24sa=Dsntz=1usg=AFQjCNHP6tysKvLsSEisPB-qo2K2J0cpcg. 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. On Wednesday, March 5, 2014 5:09:40 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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 TC 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! Am Donnerstag, 6. März 2014 23:48:59 UTC+1 schrieb Ray Tsang (AdWords API Team): Mathis, Please see our sign up guidehttps://developers.google.com/adwords/api/docs/signingupto make sure you have a completed billing and TC setup. Secondly, the the developer token has not been approved - have you submitted the new token formhttps://services.google.com/fb/forms/newtoken/ ? The developer token can only be used with test accountshttps://developers.google.com/adwords/api/docs/test-accountsprior to its approval. Please visit our test account guide for more info. Thanks! Ray On Thursday, March 6, 2014 6:57:46 AM UTC-5, Mathis Lübbers wrote: 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! Am Mittwoch, 5. März 2014 23:09:40 UTC+1 schrieb 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
Mathis, I've sent you a TC. Please follow up in that the private thread. Cheers, Ray On Friday, March 7, 2014 6:03:44 AM UTC-5, Mathis Lübbers wrote: 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 TC 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! Am Donnerstag, 6. März 2014 23:48:59 UTC+1 schrieb Ray Tsang (AdWords API Team): Mathis, Please see our sign up guidehttps://developers.google.com/adwords/api/docs/signingupto make sure you have a completed billing and TC setup. Secondly, the the developer token has not been approved - have you submitted the new token formhttps://services.google.com/fb/forms/newtoken/ ? The developer token can only be used with test accountshttps://developers.google.com/adwords/api/docs/test-accountsprior to its approval. Please visit our test account guide for more info. Thanks! Ray On Thursday, March 6, 2014 6:57:46 AM UTC-5, Mathis Lübbers wrote: 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! Am Mittwoch, 5. März 2014 23:09:40 UTC+1 schrieb 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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:
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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! Am Mittwoch, 5. März 2014 23:09:40 UTC+1 schrieb 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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! Am Montag, 3. März 2014 20:17:27 UTC+1 schrieb 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 On Saturday, March 1, 2014 11:04:58 AM UTC-5, Mathis Lübbers wrote: I got the following output when I try to fetch the URL via curl: see addition Am Freitag, 28. Februar 2014 23:56:56 UTC+1 schrieb Ray Tsang (AdWords API Team):
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
Mathis, Please see our sign up guidehttps://developers.google.com/adwords/api/docs/signingupto make sure you have a completed billing and TC setup. Secondly, the the developer token has not been approved - have you submitted the new token formhttps://services.google.com/fb/forms/newtoken/ ? The developer token can only be used with test accountshttps://developers.google.com/adwords/api/docs/test-accountsprior to its approval. Please visit our test account guide for more info. Thanks! Ray On Thursday, March 6, 2014 6:57:46 AM UTC-5, Mathis Lübbers wrote: 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! Am Mittwoch, 5. März 2014 23:09:40 UTC+1 schrieb 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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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! Am Montag, 3. März 2014 20:17:27 UTC+1 schrieb Ray Tsang (AdWords API
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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, On Tuesday, March 4, 2014 2:30:20 PM UTC-5, Ray Tsang (AdWords API Team) wrote: 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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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! Am Montag, 3. März 2014 20:17:27 UTC+1 schrieb 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 On Saturday, March 1, 2014 11:04:58 AM UTC-5, Mathis Lübbers wrote: I got the following output when I try to fetch the URL via curl: see addition Am Freitag, 28. Februar 2014 23:56:56 UTC+1 schrieb 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) On Friday, February 28, 2014 10:56:14 AM UTC-5, Mathis Lübbers wrote: Yes, I can fetch the URL via curl, Mathis Am Freitag, 28. Februar 2014 00:29:31 UTC+1 schrieb Ray Tsang
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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.dllin 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! Am Montag, 3. März 2014 20:17:27 UTC+1 schrieb 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 On Saturday, March 1, 2014 11:04:58 AM UTC-5, Mathis Lübbers wrote: I got the following output when I try to fetch the URL via curl: see addition Am Freitag, 28. Februar 2014 23:56:56 UTC+1 schrieb 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) On Friday, February 28, 2014 10:56:14 AM UTC-5, Mathis Lübbers wrote: Yes, I can fetch the URL via curl, Mathis Am Freitag, 28. Februar 2014 00:29:31 UTC+1 schrieb 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) On Thursday, February 27, 2014 10:07:46 AM UTC-5, Mathis Lübbers wrote: Hello! I have the same problem. Is there any solution? Am Mittwoch, 8. Januar 2014 05:35:35 UTC+1 schrieb Mehul HvInfotech: 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 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 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 ..*
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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 timezonehttp://us3.php.net/manual/en/datetime.configuration.php#ini.date.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) On Tuesday, March 4, 2014 9:53:03 AM UTC-5, Mathis Lübbers wrote: 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.dllin 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! Am Montag, 3. März 2014 20:17:27 UTC+1 schrieb 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 On Saturday, March 1, 2014 11:04:58 AM UTC-5, Mathis Lübbers wrote: I got the following output when I try to fetch the URL via curl: see addition Am Freitag, 28. Februar 2014 23:56:56 UTC+1 schrieb 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) On Friday, February 28, 2014 10:56:14 AM UTC-5, Mathis Lübbers wrote: Yes, I can fetch the URL via curl, Mathis Am Freitag, 28. Februar 2014 00:29:31 UTC+1 schrieb 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) On Thursday, February 27, 2014 10:07:46 AM UTC-5, Mathis Lübbers wrote: Hello! I have the same problem. Is there any solution? Am Mittwoch, 8. Januar 2014 05:35:35 UTC+1 schrieb Mehul HvInfotech: Hello All, we are getting the Soap Error During the Google Campaign pause event with
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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 On Saturday, March 1, 2014 11:04:58 AM UTC-5, Mathis Lübbers wrote: I got the following output when I try to fetch the URL via curl: see addition Am Freitag, 28. Februar 2014 23:56:56 UTC+1 schrieb 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) On Friday, February 28, 2014 10:56:14 AM UTC-5, Mathis Lübbers wrote: Yes, I can fetch the URL via curl, Mathis Am Freitag, 28. Februar 2014 00:29:31 UTC+1 schrieb 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) On Thursday, February 27, 2014 10:07:46 AM UTC-5, Mathis Lübbers wrote: Hello! I have the same problem. Is there any solution? Am Mittwoch, 8. Januar 2014 05:35:35 UTC+1 schrieb Mehul HvInfotech: 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 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 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 ..* https://lh4.googleusercontent.com/-GADIC5ZTlc8/UszVbH_noII/AHg/GorVoHze91M/s1600/opensl.png *Can any one suggest in this ?* -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
Yes, I can fetch the URL via curl, Mathis Am Freitag, 28. Februar 2014 00:29:31 UTC+1 schrieb 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) On Thursday, February 27, 2014 10:07:46 AM UTC-5, Mathis Lübbers wrote: Hello! I have the same problem. Is there any solution? Am Mittwoch, 8. Januar 2014 05:35:35 UTC+1 schrieb Mehul HvInfotech: 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 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 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 ..* https://lh4.googleusercontent.com/-GADIC5ZTlc8/UszVbH_noII/AHg/GorVoHze91M/s1600/opensl.png *Can any one suggest in this ?* -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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) On Friday, February 28, 2014 10:56:14 AM UTC-5, Mathis Lübbers wrote: Yes, I can fetch the URL via curl, Mathis Am Freitag, 28. Februar 2014 00:29:31 UTC+1 schrieb 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) On Thursday, February 27, 2014 10:07:46 AM UTC-5, Mathis Lübbers wrote: Hello! I have the same problem. Is there any solution? Am Mittwoch, 8. Januar 2014 05:35:35 UTC+1 schrieb Mehul HvInfotech: 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 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 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 ..* https://lh4.googleusercontent.com/-GADIC5ZTlc8/UszVbH_noII/AHg/GorVoHze91M/s1600/opensl.png *Can any one suggest in this ?* -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
Hello! I have the same problem. Is there any solution? Am Mittwoch, 8. Januar 2014 05:35:35 UTC+1 schrieb Mehul HvInfotech: 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 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 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 ..* https://lh4.googleusercontent.com/-GADIC5ZTlc8/UszVbH_noII/AHg/GorVoHze91M/s1600/opensl.png *Can any one suggest in this ?* -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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) On Thursday, February 27, 2014 10:07:46 AM UTC-5, Mathis Lübbers wrote: Hello! I have the same problem. Is there any solution? Am Mittwoch, 8. Januar 2014 05:35:35 UTC+1 schrieb Mehul HvInfotech: 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 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 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 ..* https://lh4.googleusercontent.com/-GADIC5ZTlc8/UszVbH_noII/AHg/GorVoHze91M/s1600/opensl.png *Can any one suggest in this ?* -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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. On Wednesday, January 8, 2014 10:05:35 AM UTC+5:30, Mehul HvInfotech wrote: 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 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 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 ..* https://lh4.googleusercontent.com/-GADIC5ZTlc8/UszVbH_noII/AHg/GorVoHze91M/s1600/opensl.png *Can any one suggest in this ?* -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
Re: SOAP-ERROR: Parsing WSDL: Couldn't load from 'https://adwords.google.com/api/adwords/cm/v201309/CampaignService?wsdl' : failed to load external entity
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! On Tuesday, January 7, 2014 11:35:35 PM UTC-5, Mehul HvInfotech wrote: 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 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 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 ..* https://lh4.googleusercontent.com/-GADIC5ZTlc8/UszVbH_noII/AHg/GorVoHze91M/s1600/opensl.png *Can any one suggest in this ?* -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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.
