apility 1.13.1, createCampaignObject suddenly stopped working

[patrick]

Hi, i am using apility 1.13.1 to run a web page that allows end-users
to do things like change their campaign status from active to paused,
etc. etc.

Starting yesterday (Dec 29, 2009), the page suddenly stopped working,
despite the fact that nothing about the code or the account was
changed. Interestingly and importantly, the page takes a long time to
load, meaning it may be some sort of a timeout issue.

I have tracked the problem down to:
in apility's lib/ directory, in the Campaign.inc.php file, in the
CreateCampaignObject function,
after running
$someCampaign = $someSoapClient->call("getCampaign",
$soapParameters);
$someCampaign is coming up empty (even though it should not be empty,
and was working with the same code, same accounts, same everything,
until yesterday when it stopped working).

Does anyone know if anything is wrong or changed recently? Perhaps
even something to do with URLs used to hit the api (as a timeout issue
of some sort seems possible)? Or parameters expected? Thanks!

[patrick]

i'm finding that due to laziness during a previous upgrade my apility
config & library files may be a hybrid of v13/ v14. in which my config
file would have caused my page to use v14. but my changelog file only
goes up to 1.13.1 causing me to indicate in my previous post that i
was using that version. however, this does not explain the issue as
whatever i was using was working well until dec 29 suddenly.

i am also noting the following:
viewing these urls in human web browser (just to troubleshoot; in
reality these would be requested by soap or whatever:)

https://adwords.google.com/api/adwords/v13/CampaignService?wsdl
works

https://adwords.google.com/api/adwords/v14/CampaignService?wsdl
has an error

(i did not check the above to see if 2nd, v14 link above *was* working
*before* my issue cropped up, however i assume it was.) is this an
issue anyone knows about or am i on the right track with my
troubleshooting? thanks.

[patrick]

there may be false leads in the 2nd post, i'm not even sure if i'm
using the v13 or v14 link, bottom line is, my page stopped working
with no changes to the code or account on dec. 29, and i'm either
using v13 or v14. :)

[AdWords API Advisor]

Hi Patrick,

There is no v14 version of the AdWords API. The successor to v13 is
the v2009 API, which is currently at version v200909. The v2009 API
has some significant changes, which you can read about here:

http://code.google.com/apis/adwords/v2009/docs/

Best,
- Eric Koleda, AdWords API Team

[patrick]

hi eric, thanks for your reply. as i was probably writing
simultaneously to when you were writing i was realizing i am using the
v13 link.

however fact remains with same code & account suddenly stopped working
12/29/09 after working stably for about 6 months. and i thought the
switch to v2009 was only becoming "required" in april/may? i guess i
could just do the switch now but it would have been easier to delay
the switch for a while. are very few ppl using v13 at this point, or
in the hundreds or more?

by the way i have a better than average dedicated server company, they
are looking into whether it's a problem on their end, perhaps somehow
they have an internal feature which suddenly disallowed my script from
contacting adwords.google.com, although "why now?" would be
interesting to find out. :)

[AdWords API Advisor]

Hi Patrick,

A majority of the v13 API is deprecated and scheduled for sunset in
April, but it has not been turned off yet and is not the cause of your
issues. I would recommend looking at the SOAP XML logs for these
requests to get a better idea of what's going on.

Best,
- Eric

[patrick]

my host had been blocking a range of ip addresses including
adwords.google.com, and has removed the block and the page is working
again. thanks