Nevermind, I found the error. I was doing:
new AdGroupCriterionOperation($op, 'SET')
But AdGroupCriterionOperation does not take a second parameter like
AdGroupOperation, so operator was null.
--
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https:/
Or without catching the original Exception, the stack trace is:
Fatal error: Uncaught SoapFault exception: [soap:Server] Fault occurred
while processing. in /code/bidder/lib/legacy/adwords/Google/Api/Ads/Common/
Lib/AdsSoapClient.php:232
Stack trace:
#0
/code/bidder/lib/legacy/adwords/Google/Api/
Or without catching the original Exception, the stack trace is:
Fatal error: Uncaught SoapFault exception: [soap:Server] Fault occurred
while processing. in /code/bidder/lib/legacy/adwords/Google/Api/Ads/Common/
Lib/AdsSoapClient.php:232
Stack trace:
#0
/code/bidder/lib/legacy/adwords/Google/Api
Hi All,
I am experiencing same issue while add negative ad-group criteria.
I am using code as
$adgroupCriterionService =
$user->GetService('AdGroupCriterionService', ADWORDS_VERSION);
$adgroupCriteria = array();
$placement_url = new Placement();
$placement_url->url = '
Hi,
Well, that was a silly reason for the hold up. The test account also had
just read-only rights. The rights were changed and the campaigns went in at
least with no problem. I'll need to ask about getting the full rights for
the hotmail account for the later time.
Thanks for the help
Timo
Hi Timo,
I see two emails associated to your MCC, one of them is set as read-only.
If you are using that hotmail one that is reason of the error.
Best,
- David Torres - AdWords API Team
On Monday, February 18, 2013 6:41:33 AM UTC-5, Timo Aarnio wrote:
>
> Hi,
>
> It seems the person controllin
Hi,
It seems the person controlling the MCC account has only given the rights
to read data for the test account.. I'll have to ask him change the rights.
I tried through the tests. All of the tests with getting various
information worked properly, showing what they were supposed to show.
When t
Hi Timo,
Just to let you know I'm still working on your issue, and have a follow up
question for you. Do you see the same error trying to call other services?
running other examples.
Best,
- David
On Thursday, February 14, 2013 12:27:44 PM UTC-5, David Torres wrote:
>
> Hi Timo,
>
> I've forw
Hi Timo,
I've forwarded your issue to the team. I will have you a response soon.
Best,
- David
On Monday, February 11, 2013 8:02:47 AM UTC-5, Timo Aarnio wrote:
>
> Hi, I'm sorry for the delay from my side as well.
>
> Yes, the issue is still there, here's the latest error call:
> [Feb 11 2013
Hi, I'm sorry for the delay from my side as well.
Yes, the issue is still there, here's the latest error call:
[Feb 11 2013 15:00:01.00 - ERROR] email=testaccount
effectiveUser=123456789 service=BudgetService method=mutate operators={ADD:
1} responseTime=67 requestId=0004d5727c8b42a00ae53cdb
Hi,
I've already left you a few questions and answers in this thread
https://groups.google.com/forum/?fromgroups=#!topic/adwords-api/grCpR_CmF9Y,
please lets follow up on it.
Best,
- David Torres - AdWords API Team
On Friday, January 25, 2013 12:15:07 PM UTC-5, Timo Aarnio wrote:
>
> Hi
>
> I
Hi,
Sorry for our delay responding you here, are you still experiencing this
issue? if yes, can you give me a fresh requestId of the issue, I'd be glad
to investigate.
To answer your questions:
You don't seem to be doing anything wrong, in fact this type of error is
likely an issue we need loo
Hi Peter,
What you are actually experiencing are CONCURRENT_MODIFICATION errors, which
is the service is not correctly reporting back to you, I'm working with the
team to correct this.
More information on how to handle this kind of CONCURRENT_MODIFICATION error
can be found here
http://code.g
It appears this issue may have been related to attempting to share an
'authToken' in the AdWordsClient header between two seperate
connections which were both attempting to operate at the same time.
I'm not 100% sure as the majority of the API calls appeared to work in
a multithreaded situation wit
Thanks - I was able to make a successful call to the API based on this
and another users' post.
-Bill
On Dec 6, 7:03 am, AdWords API Advisor
wrote:
> Hi Bill,
>
> Your RequestHeader namespace is not correct, it should be
> o:RequestHeader and the child nodes should be cm:userAgent and so on.
> A
Hi Bill,
Your RequestHeader namespace is not correct, it should be
o:RequestHeader and the child nodes should be cm:userAgent and so on.
A sample xml snippet is shown below.
**
**
**
**
**
Cheers,
Anash P. Oommen,
AdWords API Advisor.
On Dec 4, 12:41 am, Bill wr
Hi Chris,
Let us know if you have any addition questions.
Best,
- Eric Koleda, AdWords API Team
On Sep 16, 12:11 pm, Chris Ramsay wrote:
> Well, I found one problem in my SOAP:
>
> xmlns:ns="https://adwords.google.com/api/adwords/cm/v200909";
>
> should be:
>
> xmlns:ns="https://adwords.google.
Well, I found one problem in my SOAP:
xmlns:ns="https://adwords.google.com/api/adwords/cm/v200909";
should be:
xmlns:ns="https://adwords.google.com/api/adwords/cm/v201008";
At least now I am getting a sensible auth error message...!
--
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also
Hi,
I've opened an issue with the Adwords team to investigate this issue.
I'll update this thread once I hear from them.
Cheers,
Anash P. Oommen,
AdWords API Advisor.
On Sep 7, 12:07 pm, "Peer Jakobsen (AdWords API Guru)"
wrote:
> We test a campaign for conversion optimizer eligibility by doing
Hi,
I heard back from the core engineering team, and the error is being
returned because the use of MONTHLY budgets is restricted. The error
message for this problem will be improved in the next version of the
API.
Best,
- Eric Koleda, AdWords API Team
On Apr 9, 8:07 am, JosipK wrote:
> Hi,
>
Hi,
I have the same problem.
Everything works fine for Daily budget, but it fails for Monthly
budget.
Regards,
--
Josip
GemBox.Ppc - http://www.GemBoxSoftware.com/Ppc/Overview.htm - Advanced
AdWords API for C# / VB.NET
On Apr 8, 1:54 am, Simon wrote:
> On Apr 8, 2:21 am, AdWords API Advisor
On Apr 8, 2:21 am, AdWords API Advisor
wrote:
> I ran some tests myself, and it looks like the problem is that you are
> trying to create a campaign with a MONTHLY budget. The same request
> with a DAILY budget works correctly.
Thanks very much Eric. I can confirm that switching to DAILY budget
Hi Simon,
I ran some tests myself, and it looks like the problem is that you are
trying to create a campaign with a MONTHLY budget. The same request
with a DAILY budget works correctly. I'll follow up with the core
engineering team about this problem and let you know when I have more
information
FYI, I've tested a GET campaigns request, and that works fine (returns
0). So authentication creds appear correctly configured here
== request
http://schemas.xmlsoap.org/soap/
envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";>
ht
On Apr 7, 3:57 am, AdWords API Advisor
wrote:
> Hi Simon,
>
> The sandbox was reset last Friday, so this could be just a temporary
> glitch while trying to re-create your account. Can you try this
> request again?
Still same problem today.
When using the v200909 API, there isn't any need to c
Hi Simon,
The sandbox was reset last Friday, so this could be just a temporary
glitch while trying to re-create your account. Can you try this
request again?
Best,
- Eric Koleda, AdWords API Team
On Apr 6, 1:09 am, Simon wrote:
> I tried to run some code that worked last week, and it is now fa
Hi,
Please see my response on your other thread:
http://groups.google.com/group/adwords-api/browse_thread/thread/ad9bbd5ae29b64a9/
Best,
- Eric Koleda, AdWords API Team
On Mar 23, 1:35 am, dsay wrote:
> With changed headers , this is the dump
>
> *** Outgoing HTTP headers
>
With changed headers , this is the dump
*** Outgoing HTTP headers
**
POST /api/adwords/o/v200909/TargetingIdeaService HTTP/1.0
Host: adwords-sandbox.google.com
User-agent: SOAPpy 0.12.0 (http://pywebsvcs.sf.net)
Content-type: text/xml; charset="UTF-8"
Co
Hi,
The problem appears to be that their header isn't set correctly. I'm
not sure how clearly we document it right now, but unlike v13 instead
of setting each header directly you need to set one header called
"RequestHeader" which then has a field for each of the header values:
https://adwords
Hi Eric,
I am using this url
https://adwords.google.com/api/adwords/cm/v200909/CampaignService
hope this is the correct one
-Shriny
On Jan 29, 8:08 am, AdWords API Advisor
wrote:
> Hi,
>
> Which URL are you using to create your service? I think you may be
> sending a v2009 request to a v13 e
Hi,
Which URL are you using to create your service? I think you may be
sending a v2009 request to a v13 endpoint.
Best,
- Eric Koleda, AdWords API Team
On Jan 28, 2:03 pm, shriny wrote:
> I just tried a simple add campaigns and got this error,
> "Fault occurred while processing"
>
> Out Soap M
Hello,
Ah, okay, if you plan on accessing the v200902 Sandbox then APIlity
is not (yet) an option. The sample code will have to make do.
We just started seeing [RangeError.TOO_LOW @ operations
[0].operand.budget.amount] errors with our v200902 code as well, and
it's been reported to the core e
Hello Jeff,
Question, Is APIlity support for v2009 sandbox?
I already try this choice, but it is not work. So I not sure that, it
is my fault or not.
Because it has not any message from server(I already set debug ini to
be yes).
For my code the sample code, I attach xml
Hello,
If you're not familiar with the AdWords API at all, then I'd
recommend you give the APIlity PHP client library a try, as it
simplifies the otherwise manual process of creating the SOAP XML in
PHP:
http://google-apility.sourceforge.net/
If you'd like to stick with using the sample cod
34 matches
Mail list logo
