Invalid Namespace Error? Worked fine yesterday!

[hmcclungiii]

My AdWords API software has worked fine for several months now. As a
matter of fact, I just ran it around 5pm yesterday and everything was
fine. All of a sudden, I come into the office this morning, and
nothing works. I keep getting "The request namespace is invalid for
the service URL." error. Nothing has changed!

My first thought was that v3 has went live, so I changed things to
access v3 ... same problem ... nothing works! I've checked the blogs
and the forums and there is nothing posted about any changes. Maybe
the API is down?

Below is just one of the request/response that is occurring. I really
hope someone from Google can respond soon with some advice.

---------------------------------Request
<S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:XS="http://www.w3.org/2001/XMLSchema"
xmlns:XI="http://www.w3.org/2001/XMLSchema-instance"

xmlns:a="https://adwords.google.com/api/adwords/v2/AccountService"><S:Header><email
XI:type="XS:string">em...@comp.com</email><password
XI:type="XS:string">mypassword</password><token
XI:type="XS:string">mytoken</token><useragent
XI:type="XS:string">myuseragent</useragent></S:Header><S:Body><a:getClientAccounts></a:getClientAccounts></S:Body></S:Envelope>

---------------------------------Response
<S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:XS="http://www.w3.org/2001/XMLSchema"
xmlns:XI="http://www.w3.org/2001/XMLSchema-instance"
xmlns:b="https://adwords.google.com/api/adwords/v2"
xmlns:a="https://adwords.google.com/api/adwords/v2/AccountService"><S:Body><S:Fault
XI:type="S:Fault"><faultcode
XI:type="XS:QName">S:Server.userException</faultcode><faultstring
XI:type="XS:string">The request namespace is invalid for the service
URL.</faultstring><detail><b:code
XI:type="XS:string">89</b:code><b:message XI:type="XS:string">The
request namespace is invalid for the service
URL.</b:message><b:trigger
XI:type="XS:string">https://adwords.google.com/api/adwords/v2/AccountService</b:trigger></detail></S:Fault></S:Body></S:Envelope>

[hmcclungiii]

Now it appears that it is working fine again.

Could someone please advise as to what happened?

Thanks,
hmcclungiii

[hmcclungiii]

And it is back down again.

If this weren't my job, I'd probably find it funny :)

[Peer Jakobsen]

Does it only happen on the accountservice?
We rarely use the accountservicen, but for otherservices such as
criterion, campaign and report, which we use heavily we have never seen
errors like this.

Best regards,
Peer Jakobsen

[hmcclungiii]

It is happening for ALL Methods of ALL Services. Is it working for you
at this very moment?

[Patrick Chanezon]

Sorry about this, this is something we mentioned in the release notes for v3, but maybe I should have made it more prominent.
I will post a blog entry about this, because it seems you are not the only one having this problem.

http://www.google.com/apis/adwords/developer/ReleaseNotes.html

• Versioning URLs - Because we introduced versioning, and because the schemas for the payloads are different in the two versions, the URLs used to qualify the AdWords API namespace now matter. For version 2 use https://adwords.google.com/api/adwords/v2, for version 3 use https://adwords.google.com/api/adwords/v3. This should be of no consequence for developers who use a SOAP toolkit to generate their language bindings, since the toolkit will pick up the right namespace URL from the WSDL, but could cause issues for developers who hand craft their XML: we have seen requests coming in with namespaces such as https://adwords.google.com/api/adwords/v2/KeywordService. This used to work before versioning was introduced, but it won't work anymore now.

The versioned codebase now enforces stric namespace checking, so https://adwords.google.com/api/adwords/v2/AccountService that you use in your payload is now considered invalid. You should use https://adwords.google.com/api/adwords/v2

The issue you experience is because we started redeploying the new codebase on some machines.
It is non systematic because sometimes your requests are routed to machines that do not have the new codebase deployed yet.

I hope this helps.

P@

On 2/15/06, hmcclungiii <mcclun...@adelphia.net> wrote:

It is happening for ALL Methods of ALL Services.  Is it working for you
at this very moment?

--
Patrick Chanezon, AdWords API evangelist
http://blog.chanezon.com/
http://www.google.com/apis/adwords/

[hmcclungiii]

Well, it was working long enough to perform one operation. Then when I
went to perform another operation, the same problem resurfaced again.

[hmcclungiii]

Thank you very much Patrick. Seems to have solved the problem, if
anything else happens regarding this, I'll post back here.

Not sure how I missed that :)

Thanks,
hmcclungiii

[Patrick Chanezon]

Great, glad to see that it solved the issue for you.

On 2/15/06, hmcclungiii <mcclun...@adelphia.net > wrote:

Thank you very much Patrick.  Seems to have solved the problem, if
anything else happens regarding this, I'll post back here.

Not sure how I missed that :)

Nobody's perfect:-)

P@

Thanks,
hmcclungiii

[hmcclungiii]

Its happening again, :( even with the modified namespace that I suppose
supports the versioning (It worked fine when I responded to your post
earlier) ... here is the request ...

<S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:XS="http://www.w3.org/2001/XMLSchema"
xmlns:XI="http://www.w3.org/2001/XMLSchema-instance"
xmlns:a="https://adwords.google.com/api/adwords/v2
https://adwords.google.com/api/adwords/v2/AccountService"><S:Header><email

XI:type="XS:string">m...@my.com</email><password

XI:type="XS:string">mypassword</password><token
XI:type="XS:string">mytoken</token><useragent
XI:type="XS:string">myuseragent</useragent></S:Header><S:Body><a:getClientAccounts></a:getClientAccounts></S:Body></S:Envelope>

> ------=_Part_20475_30626828.1140036000723
> Content-Type: text/html; charset=ISO-8859-1
> Content-Transfer-Encoding: quoted-printable
> X-Google-AttachSize: 1073
>
> Great, glad to see that it solved the issue for you.<br><br><div><span class="gmail_quote">On 2/15/06, <b class="gmail_sendername">hmcclungiii</b> &lt;<a href="mailto:mcclun...@adelphia.net">mcclun...@adelphia.net</a>
> &gt; wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>Thank you very much Patrick.&nbsp;&nbsp;Seems to have solved the problem, if<br>
> anything else happens regarding this, I'll post back here.<br><br>Not sure how I missed that :)</blockquote><div><br>Nobody's perfect:-)<br><br>P@ <br></div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Thanks,<br>hmcclungiii<br><br></blockquote></div><br><br clear="all"><br>-- <br>Patrick Chanezon, AdWords API evangelist <br><a href="http://blog.chanezon.com/">http://blog.chanezon.com/</a><br><a href="http://www.google.com/apis/adwords/">
> http://www.google.com/apis/adwords/</a>
>
> ------=_Part_20475_30626828.1140036000723--

[Patrick Chanezon]

What does    xmlns:a="https://adwords.google.com/api/adwords/v2
https://adwords.google.com/api/adwords/v2/AccountService">
mean?

Why don't you have
   xmlns:a="https://adwords.google.com/api/adwords/v2 ">
instead?

P@

http://blog.chanezon.com/
http://www.google.com/apis/adwords/

[hmcclungiii]

" The versioned codebase now enforces stric namespace checking, so
https://adwords.google.com/api/adwords/v2/AccountService that you use
in
your payload is now considered invalid. You should use

https://adwords.google.com/api/adwords/v2<https://adwords.google.com/api/adwords/v2/AccountService>
"

Gave me the impression that that is what should be used. But I see
now, just plain https://adwords.google.com/api/adwords/v2 without the
name of the service, should be used for all services, and works well.