![]() ![]() Jeff - thanks for your continued updates. ![]() I get about 15 reports per day - everything in my MCC (so it is not a case of bad report requests). (I get the download URL from the API based on the report ID immediately prior to downloading.) This code has been running fine for months and is now failing intermittently on random reports. I'm using.NET (might be the only one, LOL), and (url, fileName). Even if i grab the download URL and paste it into a browser (firefox), i'm getting failed downloads. Hi, Experiencing similar issues, and have a bit more to add. Cheers, -Jeff Posnick, AdWords API Team On Jun 10, 10:43 am, AdWords API Advisor crosby 12.06.09 10:58. But, to reiterate, we're still actively trying to find the root cause of the specific issues reported here. In the process of this investigation, they have identified a few of our backend servers that are experiencing issues that, while they are probably not the source of this issue, could have a negative effect on the response times for a subset of AdWords API requests. Our internal engineering team has not yet been able to track down a root cause in our logs based on the IP and timestamp information that we have. Hello All, I wanted to provide an update today, as we've heard word from several developers that some of their HTTPS connections are still being closed prematurely or are otherwise unsuccessful. (Note for future readers of this thread that we don't normally check that address for support questions!) Cheers, -Jeff Posnick, AdWords API Team. This isn't the sort of info you'd want to post publicly, so it's probably best to email with that and any other log info you have. In the meantime, I have a feeling that they're going to ask for information about source IP addresses and the timeframes during which this occurred. ![]() I'll see what the core engineering team and our network operations team has to say. Hello All, Given the multiple reports of similar behavior, I'm assuming that this isn't just the normal one-off transient issues inherent in TCP connections. We had similar errors occur last night and this morning for both report downloading and bid uploading on a number of different accounts under a single MCC (using the same API token for all of them). Here is the stack trace our logs are dumping out - 22:28:38,263 ERROR (GoogleBidUploader.java: 202)- : Connection has been shutdown: : : Broken pipe 22:28:46,427 ERROR (GoogleBidUploader.java: 202)- One or more input elements failed validation. Hi, Just checking to see if anyone is experiencing ssl connection failures as well. Connection reset by peer (TLS code: SQUID_ERR_SSL_HANDSHAKE). Squid ssl bump sslv3 enforce to allow old sites. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |