Sorry Eric,
I contacted server side,again found same issue of date..
working fine now.
On Monday, August 27, 2012 9:29:20 AM UTC+5:30, Chirag wrote:
>
> Hello Eric,
>
> I am again facing this issue "!!!2|||-1||| title='AuthServer User Error OAUTH_TOKEN_HEADER_INVALID'/>
> AuthenticationError.OAU
Hello Eric,
I am again facing this issue "!!!2|||-1|||
AuthenticationError.OAUTH_TOKEN_HEADER_INVALID @ "
Please find the attached report.
XML Report is as below..
[Aug 27 2012 04:40:05.00 - ERROR] POST
/api/adwords/reportdownload/v201109 HTTP/1.1
User-Agent: curl, gzip
Host: adwords.goog
Great, glad you got it working!
- Eric
On Sat, Jul 7, 2012 at 3:38 AM, Chirag wrote:
> Hi Eric,
>
> Yes, i am successfully able to use Report Download Request from command
> line on both server.
> When i set date_default_timezone_set('Asia/Calcutta'); That PHP warning
> also gone.
>
> Please l
Hi Eric,
Yes, i am successfully able to use Report Download Request from command
line on both server.
When i set date_default_timezone_set('Asia/Calcutta'); That PHP warning
also gone.
Please look at final result:
OAuth authorization successful.
Report with name 'Criteria performance report #4
Hi Chirag,
I would encourage you to set the timezone on that server in the php.ini
file, to ensure the timestamps are accurate. Can you try replacing the
CampaignService.get() call in the UseOAuth.php example with a report
download request, and then run that on both servers?
Best,
- Eric
On Tue,
Hello Eric,
Sorry for late reply.
Finally i got access from server to run command line example "UseOAuth.php".
Yes on both server it works fine, but on server where adhoc report is not
working there i got php warning for date.
PHP Warning: date(): It is not safe to rely on the system's timezone
Hi Chirag,
Certainly a tricky problem. As a baseline, can you try running the command
line example "UseOAuth.php" on both servers, to see if that works?
- Eric
On Mon, Jun 4, 2012 at 12:28 PM, Chirag wrote:
> Hi Eric,
>
> Are these new OAuth tokens or are you using the same token on both serve
Hi Eric,
Are these new OAuth tokens or are you using the same token on both servers?
I am using same Oauth tokens for both servers.
Can you double check that you are using the same consumer key and secret on
both servers?
Yes, I am using same consumer key and secret.
Thanks,
chirag
On Monday,
Hi Chirag,
I didn't see any problems or noticeable differences with the broken
request. Are these new OAuth tokens or are you using the same token on both
servers? Can you double check that you are using the same consumer key and
secret on both servers?
- Eric
On Mon, Jun 4, 2012 at 7:23 AM, Chi
Hi Eric,
Sorry for late reply.
Please find both server's response.
Thanks,
chirag
On Friday, June 1, 2012 11:56:15 PM UTC+5:30, Eric Koleda wrote:
>
> My apologies again, I was parsing it as milliseconds and not seconds. That
> does appear to be correct.
>
> Regarding my other point, it would b
My apologies again, I was parsing it as milliseconds and not seconds. That
does appear to be correct.
Regarding my other point, it would be helpful to compare the Authorization
header from the server that is working with the one from the server that is
not working. Can you post the sanitized versi
Hello Eric,
I think timestamp is correct.
oauth_timestamp="1338338512" is refers to the Wed, 30 May 2012 00:41:52 GMT
What are the timestamps like for working requests?
I am not getting this. I am working with timezone 'Asia/Calcutta'.
Thanks,
Chirag
On Friday, June 1, 2012 10:19:58 PM UTC+5:3
Hi Chirag,
My apologies, I forgot this was for report downloads, so you should only
get a log with the report request. For report requests the OAuth parameters
are passed in the Authorization header. The value of the timestamp used
seems to be wrong:
oauth_timestamp="1338338512"
This correspond
Hello Eric,
Thanks for reply.
Yes i will look into date and time suggestion you mentioned.
But,for logging, I have $user->LogAll(); is set.
but i am not getting any log. I just got logs for reporting and it is
attached.
Thanks,
chirag
On Friday, June 1, 2012 9:37:09 PM UTC+5:30, Eric Koleda w
Hi Chirag,
It's strange that the error is only appearing on specific server
environments. The next step in debugging this issue would be to take a look
at the URL the SOAP request is being made to, since the PHP client library
appends the OAuth parameters to the URL. If you enable SOAP XML log
Hello Danial,
Any update i am waiting for your reply otherwise i need to change server
configuration from centOS to Ubuntu one.
Please note that i am using PHP client library.
Thanks,
chirag
On Monday, May 28, 2012 9:02:43 PM UTC+5:30, Danial Klimkin wrote:
>
> Hello Chirag,
>
>
> Are you using
Hello Danial,
I am using PHP Client library.
On Monday, May 28, 2012 9:02:43 PM UTC+5:30, Danial Klimkin wrote:
>
> Hello Chirag,
>
>
> Are you using any of our client libraries?
>
>
> -Danial, AdWords API Team.
>
>
> On Thursday, May 24, 2012 4:52:20 PM UTC+4, Chirag wrote:
>>
>> Hello All,
>>
Hello Chirag,
Are you using any of our client libraries?
-Danial, AdWords API Team.
On Thursday, May 24, 2012 4:52:20 PM UTC+4, Chirag wrote:
>
> Hello All,
>
> Any special configuration required for Running OAuth 1.0a running
> succesfully?
> I am trying to run one of my report download cod
Hello All,
Any update why I am not able to use Adhoc service from this centOS 5.5
server?
My code is working good on my local setup and also on ubuntu 10.10 server.
Thanks,
chirag
On Thursday, May 24, 2012 6:22:20 PM UTC+5:30, Chirag wrote:
>
> Hello All,
>
> Any special configuration required
Hello All,
Any special configuration required for Running OAuth 1.0a running
succesfully?
I am trying to run one of my report download code, but it is giving error :
*Error Message:
AuthenticationError.OAUTH_TOKEN_HEADER_INVALID @ ; trigger:'';
errorDetails:message=Invalid Header Service[Repo
20 matches
Mail list logo
