I'm actually not seeing it now.  I looked into it briefly before and oddly enough the error was happening in a legacy portion of the code about "personal" permissions settings.  It's crap code that shouldn't be there, and I could certainly clean it up (though it will all get wiped soon anyway so I'd rather not put special attention on it).  The weird part is, what the heck is special about this card to trigger that?  Real problem is likely elsewhere.