In this case, the error will have been returned to Blizzard's application code following the failure of an API call of some sort. Blizzard are failing to generate the error message. Just sloppy error handling (the "this can never fail" mentality).

I'll find out tonight if this affects me (two of my five actively used machines run Vista with no problems), so thanks very much for posting the heads-up.