from:"Birckin"

Re: Problem getting the info of an AdGroup, AdGroup doesn't exist

2010-07-26 Thread Birckin

Hello again,

Sorry for the delay in the answer, these are the whole SOAP request
and response for the Campaign's AdGroups list:

?xml version=1.0 encoding=UTF-8?
SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/
envelope/ xmlns:ns1=https://adwords.google.com/api/adwords/cm/
v200909 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;SOAP-
ENV:Headerns1:RequestHeader
xsi:type=ns1:RequestHeaderns1:applicationToken/
ns1:applicationTokenns1:authToken/
ns1:authTokenns1:clientEmail/
ns1:clientEmailns1:developerToken/
ns1:developerTokenns1:userAgentAwApi-PHP-2.0.1-Digital Click Media/
ns1:userAgent/ns1:RequestHeader/SOAP-ENV:HeaderSOAP-
ENV:Bodyns1:getns1:selectorns1:campaignId57836699/
ns1:campaignIdns1:statsSelectorns1:dateRangens1:min20100725/
ns1:minns1:max20100725/ns1:max/ns1:dateRange/
ns1:statsSelector/ns1:selector/ns1:get/SOAP-ENV:Body/SOAP-
ENV:Envelope

soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/
envelope/soap:HeaderResponseHeader xmlns=https://
adwords.google.com/api/adwords/cm/
v200909requestId7a3ca53032fdacb78cee511d5036d6bb/
requestIdoperations1/operationsresponseTime251/
responseTimeunits1/units/ResponseHeader/
soap:Headersoap:BodygetResponse xmlns=https://adwords.google.com/
api/adwords/cm/v200909rvaltotalNumEntries1/
totalNumEntriesPage.TypeAdGroupPage/
Page.Typeentriesid2177288939/idcampaignId57836699/
campaignIdcampaignNameDespedida Solteros/campaignNamenameArtÃ
culos despedidas/namestatusENABLED/statusbids xmlns:xsi=http://
www.w3.org/2001/XMLSchema-instance
xsi:type=ManualCPCAdGroupBidsAdGroupBids.TypeManualCPCAdGroupBids/
AdGroupBids.TypekeywordMaxCpcamountComparableValue.TypeMoney/
ComparableValue.TypemicroAmount20/microAmount/amount/
keywordMaxCpc/bidsstatsstartDate20100725/
startDateendDate20100725/endDatenetworkALL/networkclicks54/
clicksimpressions534/
impressionscostComparableValue.TypeMoney/
ComparableValue.TypemicroAmount1200/microAmount/
costaveragePosition3.350187265917603/
averagePositionaverageCpcComparableValue.TypeMoney/
ComparableValue.TypemicroAmount22/microAmount/
averageCpcaverageCpmComparableValue.TypeMoney/
ComparableValue.TypemicroAmount22471910/microAmount/
averageCpmctr0.10112359550561797/ctrconversions0/
conversionsconversionRate0.0/
conversionRatecostPerConversionComparableValue.TypeMoney/
ComparableValue.TypemicroAmount0/microAmount/
costPerConversionconversionsManyPerClick0/
conversionsManyPerClickconversionRateManyPerClick0.0/
conversionRateManyPerClickcostPerConversionManyPerClickComparableValue.TypeMoney/
ComparableValue.TypemicroAmount0/microAmount/
costPerConversionManyPerClickStats.TypeStats/Stats.Type/stats/
entries/rval/getResponse/soap:Body/soap:Envelope


Just as you thought, the id I'm using is not the one in the response
XML. I've checked everything and this is what I found.

First I checked my code verifying I'm using the correct id and
everything is fine. The request I'm doing in PHP is:

$adGroupService = $user-GetAdGroupService('v200909');
$selector = new AdGroupSelector();
$selector-adGroupIds = array($id);
$page = $adGroupService-get($selector);

$user object is an AdWordsUser from the Google's PHP implementation. I
have also verified also that $selector value just before the get()
call is:

AdGroupSelector Object
(
[campaignId] =
[adGroupIds] = Array
(
[0] = 2177288939
)

[statsSelector] =
[paging] =
)

Which have the correct id number. I've also noticed that the id the
SOAP request is using is the max integer, so the Google's PHP
implementation may have some issue with this, I'm going to explore a
bit inside to see when does this overflow happens, I will post any
result. Any ideas or known issues in Google's PHP implementation would
help too.

Thank you very much.


On 23 jul, 12:42, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi Birckin,

 Could you confirm if the adgroup id in your request is correct? I
 can't seem to locate this ad group.
 Could you try retrieving the adgroup ids from the campaign once more
 and post the sanitized xml (or the request id) if this adgroup id is
 valid?

 Cheers,
 Anash P. Oommen,
 AdWords API Advisor

 On Jul 22, 3:47 pm, Birckin birc...@gmail.com wrote:



  Hello,

  I'm currently using v200909 for PHP, and I'm having an issue when
  getting information of some AdGroups.

  The problem is quite odd, because the response from the API is that
  the AdGroup doesn't exist (see SOAP response below), but it does exist
  in the Campaign's AdGroups list, and so it does in the google.com/
  adwords website with its whole information of keywords, ads and such
  (logging in with the same user and password I use in the auth.ini
  file).
  Also, the problem only happens with some AdGroups (even active ones),
  I can retrieve the whole information of other several AdGroups through

Re: Problem getting the info of an AdGroup, AdGroup doesn't exist

2010-07-26 Thread Birckin

I think I've found the overflow. The WSDL scheme for the
AdGroupService from Google uses:

element maxOccurs=unbounded minOccurs=0 name=adGroupIds
type=xsd:long

I believe xsd:long size in SoapClient class from PHP5 is 32 bits, so
any AdGroup id with a value higher than 2147483647 will be cut down to
that number.

Please, notice me if I'm right or wrong, and if there is anything I
can do for fixing this issue if it's the actual problem.

Thank you.


On 26 jul, 12:05, Birckin birc...@gmail.com wrote:
 Hello again,

 Sorry for the delay in the answer, these are the whole SOAP request
 and response for the Campaign's AdGroups list:

 ?xml version=1.0 encoding=UTF-8?
 SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/
 envelope/ xmlns:ns1=https://adwords.google.com/api/adwords/cm/
 v200909 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;SOAP-
 ENV:Headerns1:RequestHeader
 xsi:type=ns1:RequestHeaderns1:applicationToken/
 ns1:applicationTokenns1:authToken/
 ns1:authTokenns1:clientEmail/
 ns1:clientEmailns1:developerToken/
 ns1:developerTokenns1:userAgentAwApi-PHP-2.0.1-Digital Click Media/
 ns1:userAgent/ns1:RequestHeader/SOAP-ENV:HeaderSOAP-
 ENV:Bodyns1:getns1:selectorns1:campaignId57836699/
 ns1:campaignIdns1:statsSelectorns1:dateRangens1:min20100725/
 ns1:minns1:max20100725/ns1:max/ns1:dateRange/
 ns1:statsSelector/ns1:selector/ns1:get/SOAP-ENV:Body/SOAP-
 ENV:Envelope

 soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/
 envelope/soap:HeaderResponseHeader xmlns=https://
 adwords.google.com/api/adwords/cm/
 v200909requestId7a3ca53032fdacb78cee511d5036d6bb/
 requestIdoperations1/operationsresponseTime251/
 responseTimeunits1/units/ResponseHeader/
 soap:Headersoap:BodygetResponse xmlns=https://adwords.google.com/
 api/adwords/cm/v200909rvaltotalNumEntries1/
 totalNumEntriesPage.TypeAdGroupPage/
 Page.Typeentriesid2177288939/idcampaignId57836699/
 campaignIdcampaignNameDespedida Solteros/campaignNamenameArtÃ
 culos despedidas/namestatusENABLED/statusbids 
 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
 xsi:type=ManualCPCAdGroupBidsAdGroupBids.TypeManualCPCAdGroupBids/
 AdGroupBids.TypekeywordMaxCpcamountComparableValue.TypeMoney/
 ComparableValue.TypemicroAmount20/microAmount/amount/
 keywordMaxCpc/bidsstatsstartDate20100725/
 startDateendDate20100725/endDatenetworkALL/networkclicks54/
 clicksimpressions534/
 impressionscostComparableValue.TypeMoney/
 ComparableValue.TypemicroAmount1200/microAmount/
 costaveragePosition3.350187265917603/
 averagePositionaverageCpcComparableValue.TypeMoney/
 ComparableValue.TypemicroAmount22/microAmount/
 averageCpcaverageCpmComparableValue.TypeMoney/
 ComparableValue.TypemicroAmount22471910/microAmount/
 averageCpmctr0.10112359550561797/ctrconversions0/
 conversionsconversionRate0.0/
 conversionRatecostPerConversionComparableValue.TypeMoney/
 ComparableValue.TypemicroAmount0/microAmount/
 costPerConversionconversionsManyPerClick0/
 conversionsManyPerClickconversionRateManyPerClick0.0/
 conversionRateManyPerClickcostPerConversionManyPerClickComparableValue.TypeMoney/
 ComparableValue.TypemicroAmount0/microAmount/
 costPerConversionManyPerClickStats.TypeStats/Stats.Type/stats/
 entries/rval/getResponse/soap:Body/soap:Envelope

 Just as you thought, the id I'm using is not the one in the response
 XML. I've checked everything and this is what I found.

 First I checked my code verifying I'm using the correct id and
 everything is fine. The request I'm doing in PHP is:

             $adGroupService = $user-GetAdGroupService('v200909');
             $selector = new AdGroupSelector();
             $selector-adGroupIds = array($id);
             $page = $adGroupService-get($selector);

 $user object is an AdWordsUser from the Google's PHP implementation. I
 have also verified also that $selector value just before the get()
 call is:

         AdGroupSelector Object
         (
             [campaignId] =
             [adGroupIds] = Array
                 (
                     [0] = 2177288939
                 )

             [statsSelector] =
             [paging] =
         )

 Which have the correct id number. I've also noticed that the id the
 SOAP request is using is the max integer, so the Google's PHP
 implementation may have some issue with this, I'm going to explore a
 bit inside to see when does this overflow happens, I will post any
 result. Any ideas or known issues in Google's PHP implementation would
 help too.

 Thank you very much.

 On 23 jul, 12:42, AdWords API Advisor adwordsapiadvi...@google.com
 wrote:



  Hi Birckin,

  Could you confirm if the adgroup id in your request is correct? I
  can't seem to locate this ad group.
  Could you try retrieving the adgroup ids from the campaign once more
  and post the sanitized xml (or the request id) if this adgroup id is
  valid?

  Cheers,
  Anash P. Oommen,
  AdWords API Advisor

  On Jul 22, 3:47 pm, Birckin birc...@gmail.com wrote:

   Hello,

   I'm

Re: Problem getting the info of an AdGroup, AdGroup doesn't exist

2010-07-26 Thread Birckin

It completely worked, thank you very much ^^

Just casting the id as a float is enough for avoiding the 32 bit
overflow.

Ignore the last answer then, I didn't read you before writing it.


On 26 jul, 12:47, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi Birckin,

 I wonder if your issue is related 
 tohttp://code.google.com/p/google-api-adwords-php/issues/detail?id=5.
 The thread seem to suggest that casting the id to a float fixes the
 error. Could you try it out and let me know if it works?

 You might also want to open an issue 
 athttp://code.google.com/p/google-api-adwords-php/issues/list
 if you think this issue is unrelated to the one I mentioned above.

 Cheers,
 Anash P. Oommen,
 AdWords API Advisor.

 On Jul 26, 3:05 pm, Birckin birc...@gmail.com wrote:



  Hello again,

  Sorry for the delay in the answer, these are the whole SOAP request
  and response for the Campaign's AdGroups list:

  ?xml version=1.0 encoding=UTF-8?
  SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/
  envelope/ xmlns:ns1=https://adwords.google.com/api/adwords/cm/
  v200909 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;SOAP-
  ENV:Headerns1:RequestHeader
  xsi:type=ns1:RequestHeaderns1:applicationToken/
  ns1:applicationTokenns1:authToken/
  ns1:authTokenns1:clientEmail/
  ns1:clientEmailns1:developerToken/
  ns1:developerTokenns1:userAgentAwApi-PHP-2.0.1-Digital Click Media/
  ns1:userAgent/ns1:RequestHeader/SOAP-ENV:HeaderSOAP-
  ENV:Bodyns1:getns1:selectorns1:campaignId57836699/
  ns1:campaignIdns1:statsSelectorns1:dateRangens1:min20100725/
  ns1:minns1:max20100725/ns1:max/ns1:dateRange/
  ns1:statsSelector/ns1:selector/ns1:get/SOAP-ENV:Body/SOAP-
  ENV:Envelope

  soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/
  envelope/soap:HeaderResponseHeader xmlns=https://
  adwords.google.com/api/adwords/cm/
  v200909requestId7a3ca53032fdacb78cee511d5036d6bb/
  requestIdoperations1/operationsresponseTime251/
  responseTimeunits1/units/ResponseHeader/
  soap:Headersoap:BodygetResponse xmlns=https://adwords.google.com/
  api/adwords/cm/v200909rvaltotalNumEntries1/
  totalNumEntriesPage.TypeAdGroupPage/
  Page.Typeentriesid2177288939/idcampaignId57836699/
  campaignIdcampaignNameDespedida Solteros/campaignNamenameArtÃ
  culos despedidas/namestatusENABLED/statusbids 
  xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
  xsi:type=ManualCPCAdGroupBidsAdGroupBids.TypeManualCPCAdGroupBids/
  AdGroupBids.TypekeywordMaxCpcamountComparableValue.TypeMoney/
  ComparableValue.TypemicroAmount20/microAmount/amount/
  keywordMaxCpc/bidsstatsstartDate20100725/
  startDateendDate20100725/endDatenetworkALL/networkclicks54/
  clicksimpressions534/
  impressionscostComparableValue.TypeMoney/
  ComparableValue.TypemicroAmount1200/microAmount/
  costaveragePosition3.350187265917603/
  averagePositionaverageCpcComparableValue.TypeMoney/
  ComparableValue.TypemicroAmount22/microAmount/
  averageCpcaverageCpmComparableValue.TypeMoney/
  ComparableValue.TypemicroAmount22471910/microAmount/
  averageCpmctr0.10112359550561797/ctrconversions0/
  conversionsconversionRate0.0/
  conversionRatecostPerConversionComparableValue.TypeMoney/
  ComparableValue.TypemicroAmount0/microAmount/
  costPerConversionconversionsManyPerClick0/
  conversionsManyPerClickconversionRateManyPerClick0.0/
  conversionRateManyPerClickcostPerConversionManyPerClickComparableValue. 
  TypeMoney/
  ComparableValue.TypemicroAmount0/microAmount/
  costPerConversionManyPerClickStats.TypeStats/Stats.Type/stats/
  entries/rval/getResponse/soap:Body/soap:Envelope

  Just as you thought, the id I'm using is not the one in the response
  XML. I've checked everything and this is what I found.

  First I checked my code verifying I'm using the correct id and
  everything is fine. The request I'm doing in PHP is:

              $adGroupService = $user-GetAdGroupService('v200909');
              $selector = new AdGroupSelector();
              $selector-adGroupIds = array($id);
              $page = $adGroupService-get($selector);

  $user object is an AdWordsUser from the Google's PHP implementation. I
  have also verified also that $selector value just before the get()
  call is:

          AdGroupSelector Object
          (
              [campaignId] =
              [adGroupIds] = Array
                  (
                      [0] = 2177288939
                  )

              [statsSelector] =
              [paging] =
          )

  Which have the correct id number. I've also noticed that the id the
  SOAP request is using is the max integer, so the Google's PHP
  implementation may have some issue with this, I'm going to explore a
  bit inside to see when does this overflow happens, I will post any
  result. Any ideas or known issues in Google's PHP implementation would
  help too.

  Thank you very much.

  On 23 jul, 12:42, AdWords API Advisor adwordsapiadvi...@google.com
  wrote:

   Hi Birckin,

   Could you

Problem getting the info of an AdGroup, AdGroup doesn't exist

2010-07-22 Thread Birckin

Hello,

I'm currently using v200909 for PHP, and I'm having an issue when
getting information of some AdGroups.

The problem is quite odd, because the response from the API is that
the AdGroup doesn't exist (see SOAP response below), but it does exist
in the Campaign's AdGroups list, and so it does in the google.com/
adwords website with its whole information of keywords, ads and such
(logging in with the same user and password I use in the auth.ini
file).
Also, the problem only happens with some AdGroups (even active ones),
I can retrieve the whole information of other several AdGroups through
the API without any problem.

I also haven't changed the application code in some time, and this
problem started to happen suddenly a few days ago, around Thursday
from the past week. What may it be?

I'm copying the SOAP request and response of the problem if it is of
any help:

?xml version=1.0 encoding=UTF-8?
SOAP-ENV:Envelope xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/
envelope/ xmlns:ns1=https://adwords.google.com/api/adwords/cm/
v200909 xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;SOAP-
ENV:Headerns1:RequestHeader
xsi:type=ns1:RequestHeaderns1:applicationToken/
ns1:applicationTokenns1:authToken/
ns1:authTokenns1:clientEmail/
ns1:clientEmailns1:developerToken/
ns1:developerTokenns1:userAgentAwApi-PHP-2.0.1-Digital Click Media/
ns1:userAgent/ns1:RequestHeader/SOAP-ENV:HeaderSOAP-
ENV:Bodyns1:getns1:selectorns1:adGroupIds2147483647/
ns1:adGroupIds/ns1:selector/ns1:get/SOAP-ENV:Body/SOAP-
ENV:Envelope

soap:Envelope xmlns:soap=http://schemas.xmlsoap.org/soap/
envelope/soap:HeaderResponseHeader xmlns=https://
adwords.google.com/api/adwords/cm/
v200909requestId622b963301dfa10acd5452f355f4/
requestIdoperations1/operationsresponseTime134/
responseTimeunits1/units/ResponseHeader/
soap:Headersoap:BodygetResponse xmlns=https://adwords.google.com/
api/adwords/cm/v200909rvaltotalNumEntries0/
totalNumEntriesPage.TypeAdGroupPage/Page.Type/rval/
getResponse/soap:Body/soap:Envelope

Thanks in advance.

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and discussion group:
http://adwordsapi.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

Re: Could not connect to host SOAP Fault on v200909

2010-04-22 Thread Birckin

Hello,

Problem solved.

After contacting to the CampaignService WSDL and checking connectivity
was working perfectly, I tried to figure out what was different
between v13 and v200909. v13 used NuSOAP and works with PHP sockets,
v200909 works directly with SoapClient.
Then I checked all possible configurations, beginning with checking
again the server met all the requirements, and it didn't. I was
missing OpenSSL (in fact I don't know how I missed it the first time I
checked the requirements before starting). After activating the
OpenSSL mod all the connections worked perfectly.

Sorry for the inconveniences caused and the time spent in this stupid
fault.

Thanks a lot for the help ^^

On 21 abr, 22:10, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi,

 Your settings look fine.  Do you need to go through a proxy on your
 server?  The URL of the v200909 CampaignService WSDL is:

  https://adwords.google.com/api/adwords/cm/v200909/CampaignService?wsdl

 Can you try to wget this URL on your server?

 Best,
 - Eric

 On Apr 20, 1:07 pm, Birckin birc...@gmail.com wrote:





  This is my current settings.ini file:

  [LOGGING]
  ; Log directory is either an abosolute path, or relative path to the
  ; AdWordsUser.php file.
  PATH_RELATIVE = 1
  LIB_LOG_DIR_PATH = ../../../../../../logs

  [SERVER]
  DEFAULT_VERSION = v200909

  ; Change tohttps://adwords-sandbox.google.comtowork in the sandbox
  ; environment.
  DEFAULT_SERVER = https://adwords.google.com;

  [SOAP]
  ; Enable/disable gzip compression on SOAP requests and responses.
  COMPRESSION = 1

  ; The level of gzip compression to use, from 1 to 9. The higher the
  level the
  ; greater the compression and time needed to perform the compression.
  The
  ; recommended and default value is 1.
  COMPRESSION_LEVEL = 1

  I've tried both 
  withhttps://adwords-sandbox.google.comandhttps://adwords.google.comasDEFAULT_SERVER.

  I'm not 100% sure if there is no firewall messing with this, but it's
  quite improbable. Any suggestions about how can I check if
  connectivity for v200909 is working correctly? Anyway it's also
  strange that I can still work with v13 perfectly in the same server.

  On 20 abr, 17:43, AdWords API Advisor adwordsapiadvi...@google.com
  wrote:

   Hi,

   What settings are you using in the settings.ini file?  Can you check
   to make sure that there are no firewall configurations on your server
   needed to allow this connection?

   Best,
   - Eric Koleda, AdWords API Team

   On Apr 20, 6:39 am, Birckin birc...@gmail.com wrote:

Hello.

I'm in the process of updating the tool to v200909 from the old v13
using AdWords API PHP Client Library.

Setting the things first I've just tried to log into the AdWords
account (following the simple Getting started video in the library
site) getting a Could not connect to host SOAP Fault message as a
result.

I've tried several things but no one worked: modifying the
AdsSoapClient::__soapCall() code to attempt several trys, appending ?
wsdl string at the end of the URL, trying with and without sandbox,
etc.

The fact is that the old v13 is still running and working, so my
server can successfully connect and operate 
withhttps://adwords.google.com/api/adwords/v13/CampaignService?wsdlbut
cannot do the same 
withhttps://adwords.google.com/api/adwords/cm/v200909/CampaignService
norhttps://adwords.google.com/api/adwords/cm/v200909/CampaignService?wsdl
nor sandbox URL versions.

What could be the problem? Maybe connectivity? Some code issues? Is
just AdWords API having any problem?

--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

Also find us on our blog and discussion 
group:http://adwordsapi.blogspot.comhttp://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 
athttp://groups.google.com/group/adwords-api?hl=en

   --
   =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
   Have you migrated to v200909 yet?
   The v13 sunset is on April 22, 2010.

   Also find us on our blog and discussion 
   group:http://adwordsapi.blogspot.comhttp://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 
   athttp://groups.google.com/group/adwords

Could not connect to host SOAP Fault on v200909

2010-04-20 Thread Birckin

Hello.

I'm in the process of updating the tool to v200909 from the old v13
using AdWords API PHP Client Library.

Setting the things first I've just tried to log into the AdWords
account (following the simple Getting started video in the library
site) getting a Could not connect to host SOAP Fault message as a
result.

I've tried several things but no one worked: modifying the
AdsSoapClient::__soapCall() code to attempt several trys, appending ?
wsdl string at the end of the URL, trying with and without sandbox,
etc.

The fact is that the old v13 is still running and working, so my
server can successfully connect and operate with
https://adwords.google.com/api/adwords/v13/CampaignService?wsdl but
cannot do the same with 
https://adwords.google.com/api/adwords/cm/v200909/CampaignService
nor https://adwords.google.com/api/adwords/cm/v200909/CampaignService?wsdl
nor sandbox URL versions.

What could be the problem? Maybe connectivity? Some code issues? Is
just AdWords API having any problem?

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

Also find us on our blog and discussion group:
http://adwordsapi.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

Re: Could not connect to host SOAP Fault on v200909

2010-04-20 Thread Birckin

This is my current settings.ini file:

[LOGGING]
; Log directory is either an abosolute path, or relative path to the
; AdWordsUser.php file.
PATH_RELATIVE = 1
LIB_LOG_DIR_PATH = ../../../../../../logs

[SERVER]
DEFAULT_VERSION = v200909

; Change to https://adwords-sandbox.google.com to work in the sandbox
; environment.
DEFAULT_SERVER = https://adwords.google.com;

[SOAP]
; Enable/disable gzip compression on SOAP requests and responses.
COMPRESSION = 1

; The level of gzip compression to use, from 1 to 9. The higher the
level the
; greater the compression and time needed to perform the compression.
The
; recommended and default value is 1.
COMPRESSION_LEVEL = 1


I've tried both with https://adwords-sandbox.google.com and
https://adwords.google.com as DEFAULT_SERVER.

I'm not 100% sure if there is no firewall messing with this, but it's
quite improbable. Any suggestions about how can I check if
connectivity for v200909 is working correctly? Anyway it's also
strange that I can still work with v13 perfectly in the same server.



On 20 abr, 17:43, AdWords API Advisor adwordsapiadvi...@google.com
wrote:
 Hi,

 What settings are you using in the settings.ini file?  Can you check
 to make sure that there are no firewall configurations on your server
 needed to allow this connection?

 Best,
 - Eric Koleda, AdWords API Team

 On Apr 20, 6:39 am, Birckin birc...@gmail.com wrote:





  Hello.

  I'm in the process of updating the tool to v200909 from the old v13
  using AdWords API PHP Client Library.

  Setting the things first I've just tried to log into the AdWords
  account (following the simple Getting started video in the library
  site) getting a Could not connect to host SOAP Fault message as a
  result.

  I've tried several things but no one worked: modifying the
  AdsSoapClient::__soapCall() code to attempt several trys, appending ?
  wsdl string at the end of the URL, trying with and without sandbox,
  etc.

  The fact is that the old v13 is still running and working, so my
  server can successfully connect and operate 
  withhttps://adwords.google.com/api/adwords/v13/CampaignService?wsdlbut
  cannot do the same 
  withhttps://adwords.google.com/api/adwords/cm/v200909/CampaignService
  norhttps://adwords.google.com/api/adwords/cm/v200909/CampaignService?wsdl
  nor sandbox URL versions.

  What could be the problem? Maybe connectivity? Some code issues? Is
  just AdWords API having any problem?

  --
  =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
  Have you migrated to v200909 yet?
  The v13 sunset is on April 22, 2010.

  Also find us on our blog and discussion 
  group:http://adwordsapi.blogspot.comhttp://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 
  athttp://groups.google.com/group/adwords-api?hl=en

 --
 =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
 Have you migrated to v200909 yet?
 The v13 sunset is on April 22, 2010.

 Also find us on our blog and discussion 
 group:http://adwordsapi.blogspot.comhttp://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 
 athttp://groups.google.com/group/adwords-api?hl=en- Ocultar texto de la cita -

 - Mostrar texto de la cita -

-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Have you migrated to v200909 yet?
The v13 sunset is on April 22, 2010.

Also find us on our blog and discussion group:
http://adwordsapi.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

Re: Problem getting the info of an AdGroup, AdGroup doesn't exist

Re: Problem getting the info of an AdGroup, AdGroup doesn't exist

Re: Problem getting the info of an AdGroup, AdGroup doesn't exist

Problem getting the info of an AdGroup, AdGroup doesn't exist

Re: Could not connect to host SOAP Fault on v200909

Could not connect to host SOAP Fault on v200909

Re: Could not connect to host SOAP Fault on v200909

7 matches

Site Navigation

Mail list logo

Footer information