Hi Jack,
The core engineering team got back to me and this issue has been
resolved. Are you still seeing this behavior?
Best,
- Eric Koleda, AdWords API Team
On Sep 17, 2:23 pm, AdWords API Advisor
wrote:
> Hi Jack,
>
> Thank you for bringing this issue to our attention. The problem
> appear
Hi Jack,
Thank you for bringing this issue to our attention. The problem
appears to be affecting a few users, and the core engineering team is
looking into it now. I'll update this thread once I have more
information.
Best,
- Eric Koleda, AdWords API Advisor
On Sep 16, 5:24 pm, Jack2006 wrot
Hello Joe,
Please see
http://groups.google.com/group/adwords-api/browse_thread/thread/da1417b7d2500871#
The engineering team is looking into things as we speak. Apologies for
the inconvenience in the meantime.
Cheers,
-Jeff Posnick, AdWords API Team
On Jul 2, 12:09 pm, jrj10 wrote:
> I'
Hello,
The issue appears to be the values you're using for the "email" and
"clientEmail" SOAP request headers, and the "clientEmails"
DefinedReportJob property. You're specifying the email address of your
MCC account for all of those values, which does not make for a valid
request.
Assuming yo
Hello All,
I found the same behaviour and I wrapped all my DAO calls to AdWords
API with retry logic :)
Btw, it stable failure when I do several webservice calls
simultaneously for one account (login/password).
Do you know is it bug? Or is it it will be fixed soon?
Thanks,
On May 4, 7:40 pm, A
Hello, erm, EvilGuy,
Could you pass along the log of the outgoing SOAP request you're
sending to the Sandbox's KeywordToolService? Make sure to X-out your
email and password information.
There's no good way for me to find your request in the Sandbox logs
and that's a very generic error, so wit
Hello Phil,
What looks like ended up being the fix was a configuration change. We
didn't have any code changes that took place around the time that the
problem first started cropping up. I don't think I could go into much
more detail than that, other than to say I'm doing what I can to make
sure
Can I ask,
Was it an issue related to permissions, or was it actually a code bug?
(In the spirit of general interest.)
On Jan 15, 6:09 pm, AdWords API Advisor
wrote:
> I'm waiting to get confirmation from the engineers who were looking at
> this, but yes, hopefully we do have a resolution in pl
I'm waiting to get confirmation from the engineers who were looking at
this, but yes, hopefully we do have a resolution in place. If ad and
criteria creation are still *not* working for you in the Sandbox,
please post and let us know.
I'll update this thread with more info when I get it.
Cheers,
Yes, working here too.
"If it ain't broke, it doesn't have enough features yet." - Unknown
--~--~-~--~~~---~--~~
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@g
Yup I just tried it and it works for me as well.
On Jan 14, 4:20 pm, pquery wrote:
> I've been experiencing this problem as well. Put I've just refreshed
> and the ad as been added successfully.
>
> On Jan 14, 11:19 pm, AdWords API Advisor
>
> wrote:
> > It is unfortunately more complicated. W
I've been experiencing this problem as well. Put I've just refreshed
and the ad as been added successfully.
On Jan 14, 11:19 pm, AdWords API Advisor
wrote:
> It is unfortunately more complicated. What the Sandbox is experiencing
> is a failure to communicate with the service that checks for ad/
It is unfortunately more complicated. What the Sandbox is experiencing
is a failure to communicate with the service that checks for ad/
criteria policy violations, and there are several engineers from both
the AdWords API team and the team responsible for our AdWords policy
checks working on resol
Yup still broke for me too. Wish they could just hit a magic roll
back button but I imagine it's a bit more complicated than that.
On Jan 13, 9:08 am, Phil <5000...@googlemail.com> wrote:
> It apperas this problem is still ongoingI am getting the same
> problem as everyone else here.
> Can a
It apperas this problem is still ongoingI am getting the same
problem as everyone else here.
Can add everything up to the Adgroup level, then everything fails from
then on - no textads or criteria.
I am supprised this has gone on for 6 days - no chance of a roll back?
Phil.
--~--~-~--~
I have the same problem, can not test addCriteria or addAd any more.
--~--~-~--~~~---~--~~
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 unsu
I have the same problem, can not test addCriteria and addAd any more.
--~--~-~--~~~---~--~~
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 uns
the problem is still actual and there is no any other possibility to
test Keywords and TextAds
soapenv:Server.generalException
An internal error has occurred. Please retry your
request.
https://adwords.google.com/api/adwords/
v13">
0
An internal error has occurr
I unfortunately don't have any updates today on a change to the
situation. I do want to assure everyone that the issue continues to
receive our core engineering team's attention, but a resolution still
has not been reached.
Apologies for the continued inconvenience,
-Jeff Posnick, AdWords API Tea
I also, am continunig to get a response of "An internal error has
occurred. Please retry your request."
On Jan 12, 9:09 am, "sergio.sprite" wrote:
> Hello there, I am having the same problems since saturday, when I try
> to add an Ad I get theerror"Aninternalerrorhasoccurred.
> pleaseretryyou
Hello there, I am having the same problems since saturday, when I try
to add an Ad I get the error "An internal error has occurred. please
retry your request. is invalid" I've tryed with 2 differents google
accounts
On 9 ene, 16:49, AdWords API Advisor
wrote:
> Hello,
>
> I just spoke to the e
Hello,
I just spoke to the engineer investigating this issue, and as
previously mentioned the underlying issue is due to a failure when the
Sandbox AdService and CriterionService attempt to check new ads or
keywords for violations. This appears to be affecting the majority of
addAds() and addCri
Hello ,
I am also getting same exception...
FINE: POST /api/adwords/v12/CampaignService HTTP/1.0
Content-Type: text/xml; charset=utf-8
Accept: application/soap+xml, application/dime, multipart/related,
text/*
User-Agent: Axis/1.2.1
Host: sandbox.google.com
Cache-Control: no-cache
Pragma: no-cac
I appreciate your diligence. Because you can't reproduce the error
yourself I've been working under the assumption that it's a problem
with my code; however I'm still getting the same error when I try to
create an ad, regardless of whether it's from the awords4r sample code
or the stuff I'm workin
Hello,
Just to keep folks updated, the root cause is actively being looked
into by a member of the core engineering team. There were also some
server restarts performed this morning that *may* have improved the
situation, but I can't reproduce the problem myself so I couldn't say
for sure.
Chee
Thanks for continuing to look at this.
I'm using adwords4r. I just tried the create_all.rb example code with
a new sandbox account. Here is the result:
Campaign id 5346 was successfully added.
Ad group id 518300 was successfully added.
SOAP Error: An internal error has occurred. Please re
Hello,
We took a look at Peer's request, and there's an exception being
thrown in the Sandbox during the stage at which criteria are checked
for policy violations. Ads are also checked for policy violations in
the Sandbox, and the problems with adding those may have a similar
cause. It's not imm
Okay, this still isn't something that I or my colleagues have been
able to reproduce (I tried using my own ad group id but an otherwise
similar addCriteria() call with no issues, and I can create ads as
well). I'll have this escalated to see what we can learn about the
errors from the Sandbox logs
Thanks for popping in.
I can create a campaign, create an ad group, then I get the error when
I try to create an ad.
On Jan 7, 8:05 am, AdWords API Advisor
wrote:
> Hello,
>
> While I'm not going to discount the possibility of the Sandbox having
> issues, I can't reproduce anything right now--
Hi Jeff,
I currently see this on the sandbox for AddCriteria and AddAds.
Here is a SOAP Request that fails:
http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";>
https://adwords.
Hello,
While I'm not going to discount the possibility of the Sandbox having
issues, I can't reproduce anything right now--new client account
creation, campaign creation, and getting client account info all
worked.
What calls were you making when you encountered the error? Can you
reproduce it
I am getting the same error.
On Jan 6, 7:47 pm, Ursula wrote:
> Hello,
> Is there something wrong with the sandbox today? I've been trying to
> run various tests and I am getting this error on every request:
> An internal error has occurred. Please retry your request.
>
> When will this be fi
The refresh just took place and the Sandbox appears fully functional.
Can you give it a try?
Cheers,
-Jeff Posnick, AdWords API Team
On Nov 21, 11:58 am, Tom Guzik <[EMAIL PROTECTED]> wrote:
> When will the servers be refreshed?
>
> On Nov 20, 3:56 pm, AdWords API Advisor <[EMAIL PROTECTED]>
>
When will the servers be refreshed?
On Nov 20, 3:56 pm, AdWords API Advisor <[EMAIL PROTECTED]>
wrote:
> Hello Nick,
>
> I can confirm that the Sandbox is returning "internal error" SOAP
> faults for all requests right now. I've let the engineering team know
> and they're investigating the root
Hello Nick,
I can confirm that the Sandbox is returning "internal error" SOAP
faults for all requests right now. I've let the engineering team know
and they're investigating the root cause.
Cheers,
-Jeff Posnick, AdWords API Team
On Nov 20, 5:36 pm, Nick Retallack <[EMAIL PROTECTED]> wrote:
>
35 matches
Mail list logo