Curiously, after installing 2.0.3, OAuth linking to Analytics and going to the Dashboard full of anticipation and joy, I was most saddened to see the above error message displaying in my Chrome browser.
Had a quick look at the configs, couldn't see anything obviously amiss, but found the following on the console;
http://xxxx.xxxxxxxx.co.uk/wp-admin/admin-ajax.php?action=gad_fill_dp&cookie=PageLinesTabCookie%3D14%3B%20__utma%3D114918549.513756219.1331051515.1331051515.1331051515.1%3B%20__utmz%3D114918549.1331051515.1.1.utmccn%3D(direct)%7Cutmcsr%3D(direct)%7Cutmcmd%3D(none)%3B%20PHPSESSID%3D101138adaced6379249c4899cf1f9c96%3B%20wordpress_test_cookie%3DWP%2BCookie%2Bcheck%3B%20wp-settings-1%3Dalign%253Dright%2526hidetb%253D1%2526editor%253Dtinymce%3B%20wp-settings-time-1%3D1335345660%3B%20__utma%3D47385204.840065060.1335346041.1335346041.1335353733.2%3B%20__utmc%3D47385204%3B%20__utmz%3D47385204.1335346041.1.1.utmcsr%3D(direct)%7Cutmccn%3D(direct)%7Cutmcmd%3D(none)%3B%20__utmv%3D47385204.%7C1%3Dlogged-in%3Dadministrator%3D1&rndval=1335514112163Failed to load resource: the server responded with a status of 404 (Not Found)
Thinking all was lost, I filled in the feedback to say it wasn't working for me. The story doesn't end there though - it turns out that if I open the dashboard in any other browser session in any browser (Chrome, Firefox, IE) it works perfectly! It would seem that the reason it isn't working in my original Chrome session is that I am already logged in to an Analytics session in another tab; that's as much as I can tell you at the moment. If any more info would help, let me know.