Re: AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
Hah, funny you should mention that Zweitze - that's exactly what I found last night. The AdWords .NET library dev responded in private, offering to help me with my issue. He suggested I enable .NET tracing to log the raw HTTP requests. Once I did that, I found an XML response in the trace file when the errors occurred: - AuthenticationError.OAUTH_TOKEN_INVALID I then realized that I was running into the report download errors a little more than an hour into my sync process - so it seemed like my oauth token was expiring after an hour. I'm syncing a large # of accounts but we were re-using the AdWords user objects, keeping them in memory instead of re-creating them, but I first do all campaigns, then all ad groups, then all ads. This means that each account gets used 1 time, then can wait more than an hour before it's used again for the next type. At any rate, I added code to refresh the AdWords user objects if an error was encountered, getting new tokens, and it seems to have solved my report downloads issue. I forgot to implement it in one part of my sync process, so I didn't get a clean result last night, but expect to on my next run. Marked your reply as the answer. Thanks for your insight. On Wednesday, April 16, 2014 5:15:08 AM UTC-7, Zweitze wrote: > > I understand that you use .NET. > > When you get a WebException with HTTP 400, do download the response: take > WebException.Response, cast it to HttpWebResponse, then call it's > GetResponseStream() method. > You will find some XML with more info on the problem with the request. > > My guess: your code fails about an hour after the AccessToken was > retrieved, and you are using OAuth2. OAuth2 access tokens are only valid > for an hour, after that you should obtain a new AccessToken. > > (Note: I don't use the .NET library for retrieving reports. If you do, the > library should parse the WebException and retrieve the info from the > WebException. But, I believe the library contains an error that expired > AccessTokens will not be renewed automatically.) > > Hope this helps. > > > On Tuesday, April 8, 2014 8:29:59 PM UTC+2, Brett Rogers wrote: >> >> Scenario: >> >> We have a daily task that downloads AdWords AdHoc reports for our MCC >> account's accounts, campaigns, ad groups, and ads to synchronize them with >> our local database. We have multiple accounts in our MCC and each account >> has large quantities of ad groups, so we download quite a bit of data. This >> process worked great until a few weeks ago, when we started the following >> error part of the way through the process: >> >> - The remote server returned an error: (400) Bad Request. >> >> Once this error occurs on the main daily task computer, we see the >> following: >> >> - AdHoc Reports requests initiated from that computer fail after a >> handful of requests >> - AdWords API requests initiated from that computer fail with this error: >> -- An existing connection was forcibly closed by the remote host >> >> BUT, if we then launch this same daily task from another computer, it >> will successfully complete everything and API requests will also work, >> i.e., the same auth credentials work elsewhere, just not from that computer. >> >> Ideas? Are we running into some kind of IP or computer-based quota? >> >> FYI - we're using the latest API version - v201402, but the problem was >> also occurring with v201309 before we recently upgraded. >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
I understand that you use .NET. When you get a WebException with HTTP 400, do download the response: take WebException.Response, cast it to HttpWebResponse, then call it's GetResponseStream() method. You will find some XML with more info on the problem with the request. My guess: your code fails about an hour after the AccessToken was retrieved, and you are using OAuth2. OAuth2 access tokens are only valid for an hour, after that you should obtain a new AccessToken. (Note: I don't use the .NET library for retrieving reports. If you do, the library should parse the WebException and retrieve the info from the WebException. But, I believe the library contains an error that expired AccessTokens will not be renewed automatically.) Hope this helps. On Tuesday, April 8, 2014 8:29:59 PM UTC+2, Brett Rogers wrote: > > Scenario: > > We have a daily task that downloads AdWords AdHoc reports for our MCC > account's accounts, campaigns, ad groups, and ads to synchronize them with > our local database. We have multiple accounts in our MCC and each account > has large quantities of ad groups, so we download quite a bit of data. This > process worked great until a few weeks ago, when we started the following > error part of the way through the process: > > - The remote server returned an error: (400) Bad Request. > > Once this error occurs on the main daily task computer, we see the > following: > > - AdHoc Reports requests initiated from that computer fail after a handful > of requests > - AdWords API requests initiated from that computer fail with this error: > -- An existing connection was forcibly closed by the remote host > > BUT, if we then launch this same daily task from another computer, it will > successfully complete everything and API requests will also work, i.e., the > same auth credentials work elsewhere, just not from that computer. > > Ideas? Are we running into some kind of IP or computer-based quota? > > FYI - we're using the latest API version - v201402, but the problem was > also occurring with v201309 before we recently upgraded. > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
Hello Brett, I'll ask my colleague to suggest here. We is the author of the DotNet library and may have more insights about windows environment. -Danial, AdWords API Team. On Tuesday, April 15, 2014 8:10:10 AM UTC+4, Brett Rogers wrote: > > Danial, > > I disabled ECN on my server but still seeing the same results. I also > tried setting up a brand new machine (VM) and running the task there, but > seeing the same results. > > For now I've tried playing around with retries and delays, but that hasn't > seemed to help much either. > > Very frustrating as it's next to impossible for me to get a complete sync > done. Strange too since it worked so well for so long. > > > On Thursday, April 10, 2014 5:13:33 AM UTC-7, Danial Klimkin wrote: >> >> Hello Brett, >> >> >> There is a known issue with ECN turned on by default. Please try the >> following on your server: >> >> netsh interface tcp set global ecncapability=disabled >> >> as described here: >> >> >> http://social.technet.microsoft.com/wiki/contents/articles/20204.how-to-enable-and-disable-explicit-congestion-notification-in-windows.aspx >> >> Please let us know if this resolves your issue. >> >> >> -Danial, AdWords API Team. >> >> >> On Wednesday, April 9, 2014 10:38:41 PM UTC+4, Brett Rogers wrote: >>> >>> Danial, >>> >>> Yes, we are using Windows (and C#, for what it's worth). >>> >>> I'm pretty confident that it's not a network issue given the fact that >>> this machine runs quite a few different network-involved processes, >>> including hosting a database, and none of those processes have been seen >>> network-related issues. >>> >>> >>> On Wednesday, April 9, 2014 5:46:50 AM UTC-7, Danial Klimkin wrote: Hello Brett, Generally, you should receive a meaningful error from the API for the cases when you are rate limited. Bad Request often means the request was not send in full (unless it was a really malformed request). Most likely this is a network issue. Are you running on a windows platform? -Danial, AdWords API Team. On Tuesday, April 8, 2014 10:29:59 PM UTC+4, Brett Rogers wrote: > > Scenario: > > We have a daily task that downloads AdWords AdHoc reports for our MCC > account's accounts, campaigns, ad groups, and ads to synchronize them > with > our local database. We have multiple accounts in our MCC and each account > has large quantities of ad groups, so we download quite a bit of data. > This > process worked great until a few weeks ago, when we started the following > error part of the way through the process: > > - The remote server returned an error: (400) Bad Request. > > Once this error occurs on the main daily task computer, we see the > following: > > - AdHoc Reports requests initiated from that computer fail after a > handful of requests > - AdWords API requests initiated from that computer fail with this > error: > -- An existing connection was forcibly closed by the remote host > > BUT, if we then launch this same daily task from another computer, it > will successfully complete everything and API requests will also work, > i.e., the same auth credentials work elsewhere, just not from that > computer. > > Ideas? Are we running into some kind of IP or computer-based quota? > > FYI - we're using the latest API version - v201402, but the problem > was also occurring with v201309 before we recently upgraded. > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
Danial, I disabled ECN on my server but still seeing the same results. I also tried setting up a brand new machine (VM) and running the task there, but seeing the same results. For now I've tried playing around with retries and delays, but that hasn't seemed to help much either. Very frustrating as it's next to impossible for me to get a complete sync done. Strange too since it worked so well for so long. On Thursday, April 10, 2014 5:13:33 AM UTC-7, Danial Klimkin wrote: > > Hello Brett, > > > There is a known issue with ECN turned on by default. Please try the > following on your server: > > netsh interface tcp set global ecncapability=disabled > > as described here: > > > http://social.technet.microsoft.com/wiki/contents/articles/20204.how-to-enable-and-disable-explicit-congestion-notification-in-windows.aspx > > Please let us know if this resolves your issue. > > > -Danial, AdWords API Team. > > > On Wednesday, April 9, 2014 10:38:41 PM UTC+4, Brett Rogers wrote: >> >> Danial, >> >> Yes, we are using Windows (and C#, for what it's worth). >> >> I'm pretty confident that it's not a network issue given the fact that >> this machine runs quite a few different network-involved processes, >> including hosting a database, and none of those processes have been seen >> network-related issues. >> >> >> On Wednesday, April 9, 2014 5:46:50 AM UTC-7, Danial Klimkin wrote: >>> >>> Hello Brett, >>> >>> >>> Generally, you should receive a meaningful error from the API for the >>> cases when you are rate limited. >>> >>> Bad Request often means the request was not send in full (unless it was >>> a really malformed request). Most likely this is a network issue. >>> >>> Are you running on a windows platform? >>> >>> >>> -Danial, AdWords API Team. >>> >>> >>> On Tuesday, April 8, 2014 10:29:59 PM UTC+4, Brett Rogers wrote: Scenario: We have a daily task that downloads AdWords AdHoc reports for our MCC account's accounts, campaigns, ad groups, and ads to synchronize them with our local database. We have multiple accounts in our MCC and each account has large quantities of ad groups, so we download quite a bit of data. This process worked great until a few weeks ago, when we started the following error part of the way through the process: - The remote server returned an error: (400) Bad Request. Once this error occurs on the main daily task computer, we see the following: - AdHoc Reports requests initiated from that computer fail after a handful of requests - AdWords API requests initiated from that computer fail with this error: -- An existing connection was forcibly closed by the remote host BUT, if we then launch this same daily task from another computer, it will successfully complete everything and API requests will also work, i.e., the same auth credentials work elsewhere, just not from that computer. Ideas? Are we running into some kind of IP or computer-based quota? FYI - we're using the latest API version - v201402, but the problem was also occurring with v201309 before we recently upgraded. >>> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
Hello Brett, There is a known issue with ECN turned on by default. Please try the following on your server: netsh interface tcp set global ecncapability=disabled as described here: http://social.technet.microsoft.com/wiki/contents/articles/20204.how-to-enable-and-disable-explicit-congestion-notification-in-windows.aspx Please let us know if this resolves your issue. -Danial, AdWords API Team. On Wednesday, April 9, 2014 10:38:41 PM UTC+4, Brett Rogers wrote: > > Danial, > > Yes, we are using Windows (and C#, for what it's worth). > > I'm pretty confident that it's not a network issue given the fact that > this machine runs quite a few different network-involved processes, > including hosting a database, and none of those processes have been seen > network-related issues. > > > On Wednesday, April 9, 2014 5:46:50 AM UTC-7, Danial Klimkin wrote: >> >> Hello Brett, >> >> >> Generally, you should receive a meaningful error from the API for the >> cases when you are rate limited. >> >> Bad Request often means the request was not send in full (unless it was a >> really malformed request). Most likely this is a network issue. >> >> Are you running on a windows platform? >> >> >> -Danial, AdWords API Team. >> >> >> On Tuesday, April 8, 2014 10:29:59 PM UTC+4, Brett Rogers wrote: >>> >>> Scenario: >>> >>> We have a daily task that downloads AdWords AdHoc reports for our MCC >>> account's accounts, campaigns, ad groups, and ads to synchronize them with >>> our local database. We have multiple accounts in our MCC and each account >>> has large quantities of ad groups, so we download quite a bit of data. This >>> process worked great until a few weeks ago, when we started the following >>> error part of the way through the process: >>> >>> - The remote server returned an error: (400) Bad Request. >>> >>> Once this error occurs on the main daily task computer, we see the >>> following: >>> >>> - AdHoc Reports requests initiated from that computer fail after a >>> handful of requests >>> - AdWords API requests initiated from that computer fail with this error: >>> -- An existing connection was forcibly closed by the remote host >>> >>> BUT, if we then launch this same daily task from another computer, it >>> will successfully complete everything and API requests will also work, >>> i.e., the same auth credentials work elsewhere, just not from that computer. >>> >>> Ideas? Are we running into some kind of IP or computer-based quota? >>> >>> FYI - we're using the latest API version - v201402, but the problem was >>> also occurring with v201309 before we recently upgraded. >>> >> -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
Danial, Yes, we are using Windows (and C#, for what it's worth). I'm pretty confident that it's not a network issue given the fact that this machine runs quite a few different network-involved processes, including hosting a database, and none of those processes have been seen network-related issues. On Wednesday, April 9, 2014 5:46:50 AM UTC-7, Danial Klimkin wrote: > > Hello Brett, > > > Generally, you should receive a meaningful error from the API for the > cases when you are rate limited. > > Bad Request often means the request was not send in full (unless it was a > really malformed request). Most likely this is a network issue. > > Are you running on a windows platform? > > > -Danial, AdWords API Team. > > > On Tuesday, April 8, 2014 10:29:59 PM UTC+4, Brett Rogers wrote: >> >> Scenario: >> >> We have a daily task that downloads AdWords AdHoc reports for our MCC >> account's accounts, campaigns, ad groups, and ads to synchronize them with >> our local database. We have multiple accounts in our MCC and each account >> has large quantities of ad groups, so we download quite a bit of data. This >> process worked great until a few weeks ago, when we started the following >> error part of the way through the process: >> >> - The remote server returned an error: (400) Bad Request. >> >> Once this error occurs on the main daily task computer, we see the >> following: >> >> - AdHoc Reports requests initiated from that computer fail after a >> handful of requests >> - AdWords API requests initiated from that computer fail with this error: >> -- An existing connection was forcibly closed by the remote host >> >> BUT, if we then launch this same daily task from another computer, it >> will successfully complete everything and API requests will also work, >> i.e., the same auth credentials work elsewhere, just not from that computer. >> >> Ideas? Are we running into some kind of IP or computer-based quota? >> >> FYI - we're using the latest API version - v201402, but the problem was >> also occurring with v201309 before we recently upgraded. >> > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
Hello Brett, Generally, you should receive a meaningful error from the API for the cases when you are rate limited. Bad Request often means the request was not send in full (unless it was a really malformed request). Most likely this is a network issue. Are you running on a windows platform? -Danial, AdWords API Team. On Tuesday, April 8, 2014 10:29:59 PM UTC+4, Brett Rogers wrote: > > Scenario: > > We have a daily task that downloads AdWords AdHoc reports for our MCC > account's accounts, campaigns, ad groups, and ads to synchronize them with > our local database. We have multiple accounts in our MCC and each account > has large quantities of ad groups, so we download quite a bit of data. This > process worked great until a few weeks ago, when we started the following > error part of the way through the process: > > - The remote server returned an error: (400) Bad Request. > > Once this error occurs on the main daily task computer, we see the > following: > > - AdHoc Reports requests initiated from that computer fail after a handful > of requests > - AdWords API requests initiated from that computer fail with this error: > -- An existing connection was forcibly closed by the remote host > > BUT, if we then launch this same daily task from another computer, it will > successfully complete everything and API requests will also work, i.e., the > same auth credentials work elsewhere, just not from that computer. > > Ideas? Are we running into some kind of IP or computer-based quota? > > FYI - we're using the latest API version - v201402, but the problem was > also occurring with v201309 before we recently upgraded. > -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
AdHoc Reports and API connection issues: 'The remote server returned an error: (400) Bad Request' and 'An existing connection was forcibly closed by the remote host'. Quota problem?
Scenario: We have a daily task that downloads AdWords AdHoc reports for our MCC account's accounts, campaigns, ad groups, and ads to synchronize them with our local database. We have multiple accounts in our MCC and each account has large quantities of ad groups, so we download quite a bit of data. This process worked great until a few weeks ago, when we started the following error part of the way through the process: - The remote server returned an error: (400) Bad Request. Once this error occurs on the main daily task computer, we see the following: - AdHoc Reports requests initiated from that computer fail after a handful of requests - AdWords API requests initiated from that computer fail with this error: -- An existing connection was forcibly closed by the remote host BUT, if we then launch this same daily task from another computer, it will successfully complete everything and API requests will also work, i.e., the same auth credentials work elsewhere, just not from that computer. Ideas? Are we running into some kind of IP or computer-based quota? FYI - we're using the latest API version - v201402, but the problem was also occurring with v201309 before we recently upgraded. -- -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and Google+: https://googleadsdeveloper.blogspot.com/ https://plus.google.com/+GoogleAdsDevelopers/posts =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ 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 unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en --- You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To unsubscribe from this group and stop receiving emails from it, send an email to adwords-api+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
