Well, seems to be working now. I'm guessing there was just a hiccup in the database earlier that has since sorted itself out.

EDIT: Nevermind...you seem to still be getting the error. I can't duplicate it, though. I'll keep checking into it.