ReportDefinitionService SET operation (Update existing report) InternalApiError.UNEXPECTED_INTERNAL_API_ERROR

2011-01-21 Thread Rohit Dantas
Hi, I'm working on the adwords api and have encountered the infamous "InternalApiError.UNEXPECTED_INTERNAL_API_ERROR" whilst trying to update an existing ReportDefinition. The report is of type [ReportDefinitionReportType.AD_PERFORMANCE_REPORT] with a date-range- type set to [ReportDefinitionDate

Re: ReportDefinitionService SET operation (Update existing report) InternalApiError.UNEXPECTED_INTERNAL_API_ERROR

2011-01-24 Thread Rohit Dantas
InternalApiError.UNEXPECTED_INTERNAL_API_ERROR InternalApiError UNEXPECTED_INTERNAL_API_ERROR In case that helps speed up the error

Re: ReportDefinitionService SET operation (Update existing report) InternalApiError.UNEXPECTED_INTERNAL_API_ERROR

2011-01-26 Thread Rohit Dantas
sue where the update will fail if the > reportType field isn't included in the request.  In this case it would > be best if you sent the entire ReportDefinition in the request instead > of just the fields you want to change. > > Best, > - Eric Koleda, AdWords API Team > &g

Re: custom time range not saved in ReportDefinition

2011-02-14 Thread Rohit Dantas
Hi Eric, Sorry for the late reply, but I only just noticed your reply to the above issue as I was on holiday when Johannes wrote the above bug report. We have been subject to the same problem multiple times over the past 2 weeks, but quite sporadically. It will work without a hitch for a few da

Re: custom time range not saved in ReportDefinition

2011-02-15 Thread Rohit Dantas
Hi, the two reportIDs we use for which this error occurs are: 1. 11931386 2. 11940986 As mentioned previously, the date update on the second report failed repeatedly yesterday. On the other hand it seems to work fine today. Cheers, Rohit -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

Re: custom time range not saved in ReportDefinition

2011-02-21 Thread Rohit Dantas
Hi Eric, Sorry about the confusion, I misread the 'request ID' as 'report ID' for some reason. The report failed again and in the soap_xml.log the request ID saved was *652b5a957c66dd412fa722032004ffbf* Hope that helps with identifying the error. Cheers, Rohit -- =~=~=~=~=~=~=~=~=~=~=~=~=~=

Re: custom time range not saved in ReportDefinition

2011-02-22 Thread Rohit Dantas
Hi, The problem persists today. Request IDs that did not work: - 3649d0052b00bc0bec61e789f0e0f5cf - 832441e21fd0d8b11d674a2017264583 - bc50230be7212c4f45efd2db254a9aee - c33c811451740b61a5f3c41dfd43b871 Request IDs that worked: - 2741005e8ff23ed765d91d0f4344 - a4678d0e

Re: custom time range not saved in ReportDefinition

2011-03-23 Thread Rohit Dantas
Hi, I'll look into it, atm we've built an automatic retry system as a workaround to the issue. I'll try to get the latest failure data as soon as possible. It might take a short while. Cheers, Rohit -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion gr

DatabaseError.CONCURRENT_MODIFICATION on large keyword bids update query

2011-04-04 Thread Rohit Dantas
Hi i was updating ~4552 keyword bids today and received the following error, even though no-one else was using our account to modify keywords, nor was any other API process try to do the same. The next attempt to do the same worked without a problem. Do you know what could be the issue? Should