Sorry for the slow responses, but I am out with a really nasty cold/flu bug.

Yes - some of you have seen your 11008 Errors convert to 11009 Errors. In the patch deployed over the weekend (actually it was Monday I think), the new code moved authentication calls to a different event, as there are multiple systems making auth calls and it was thought that they might be conflicting with one another.

The expectation was that this might resolve the issue, but if not that we would have more specific error handling (new error 11009 rather than the generic 11008). Three different dev and release teams spent the past few days further dissecting what is happening in the various systems when the 11009 error occurs, and as of this morning it looks like they may have a breakthrough on the cause and fix.

I know they are checking out a few more issues with implementation of the fix. I expect another update later today as to the actions and timing.

11/17/09 UPDATE: Configuration changes and code updated have been implemented and we believe this issue is now resolved. There are currently only 20 of the 11009 errors logged from a single server (we are rechecking this server) where we did have about 5600 11009 errors across all servers prior to the code and config updates. 

If you were receiving the 11008 error and it converted to 11009 errors, can you check again and let me know if you are now able to access (either by posting on the blog or emailing me through the blogs contact us link.

THANKS!