Not sure if this applies, but there's a known issue with a concurrency exception which will give the same "Invalid object name Message" message, even when not using localization. As Charles said, running the scripts is a work around.

Maybe it's fixed in today's release?

Mike