Syncronous report found, use DownloadReport() instead. Cross Client Reporting

98 views
Skip to first unread message

BeUp NL

unread,
Apr 28, 2011, 8:57:48 AM4/28/11
to adwor...@googlegroups.com
Hi,

After all the Quota Exceeded problems I installed the latest PHP client library branch and used the provided example: AddCrossClientReportDefinition.php to create a Cross Client Report. The report is shown in my MCC reporting page and is working fine when used in the MCC interface.

When I try to download it using the provided example: DownloadCrossClientReport.php I get an error: Syncronous report found, use DownloadReport() instead.
I get the same error if I specify a report ID that is unexisting...

Any help is welcome.

Jan

BeUp NL

unread,
Apr 28, 2011, 9:36:53 AM4/28/11
to adwor...@googlegroups.com
When I try using the normal DownloadReport() I get this: "Asyncronous report found, use RunAsyncReport() instead."

Ahhhhhhhhhhhhh....

Anash P. Oommen

unread,
May 2, 2011, 6:50:10 AM5/2/11
to adwor...@googlegroups.com
Hi,

I replied on the other thread, but the summary is that v201101 cross-client reports aren't available right now, so DownloadCrossClientReports.php won't work until the feature is available on the servers.

Cheers,
Anash P. Oommen,
AdWords API Advisor.

BeUp NL

unread,
May 5, 2011, 6:10:45 AM5/5/11
to adwor...@googlegroups.com
Hi Anash,
 
Any idea about the delay? We are realy stuck on this one.
 
Thnx,
Jan

Eric Koleda

unread,
May 6, 2011, 11:18:47 AM5/6/11
to adwor...@googlegroups.com
Hi Jan,

We're still working on getting the backend ready, and we hope to have it released by the end of the month.  We apologize for the delay.

Best,
- Eric Koleda, AdWords API Team

DungCoi

unread,
Jun 19, 2011, 10:30:58 PM6/19/11
to adwor...@googlegroups.com
but when i used DownloadReport() in DownloadReport.php file then i still get same message.

Eric Koleda

unread,
Jun 22, 2011, 2:36:37 PM6/22/11
to adwor...@googlegroups.com
Hi,

There is an issue with small reports being interpreted incorrectly.


This problem is fixed in trunk, and will be part of the next release.

Best,
- Eric
Reply all
Reply to author
Forward
0 new messages