I was getting that too. Considering it's a database error I figured it was site wide, but for fun I tried in private mode and it works. that's weird. how would a database issue only affect certain situations? It's either the database works or it doesn't. I guess it might be a generic error and it's actually something it sees in user cookies it does not like. Seems to me there should be a better way to handle a situation like that though, such as expiring invalid cookies. (ex: if session Id is not matching up or something)