Forum Moderators: martinibuster

Message Too Old, No Replies

Google 414. That's an error.

"Too large to process"

         

Sally Stitts

7:59 pm on Apr 19, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



Google 414. That's an error.
The requested URL /adsense/v3/login2... is too large to process. That’s all we know.

I get these errors all the time now, right next to a drawing of a broken robot.

They occur when I change the date range.
They occur when I hit refresh.
Clearly, my requests are NOT "too large to process".
They are very small requests.

The work-around? Start over again, from scratch.
Annoying.
.

netmeg

8:12 pm on Apr 19, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



What were you doing when it occurred? Trying to run a report?

I haven't seen them myself.

Lame_Wolf

8:15 pm on Apr 19, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



[google.com...]

Sally Stitts

9:16 pm on Apr 19, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



What were you doing when it occurred? Trying to run a report?

Yes. Sorry I wasn't clear.
I was using Firefox 3.6.27 on an old PPC Mac running OS 10.4.11.
Also occurs on PC - Windows and Linux.

Excellent link above from Lame_Wolf.
It indicates that MANY various Google circumstances produce this error, not just AdSense reports.
---> AdSense sign-in, AdSense reports, calendar, gmail, wallet, etc.

It appears to be the new catch-all "error du jour".
.

lucy24

1:37 am on Apr 20, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



It appears to be the new catch-all "error du jour".

Yes, I saw the subject header and thought for a moment I was in the wrong forum. Just a week or two back, the w3c html validator was throwing a painfully similar "too large" error-- in response to 50K files. (If you tried a really big file, it would invent an entirely different error.)

Well, it never hurts to empty your browser cache ;)