Have you checked permissions on the table? I ran into this error yesterday and it was due to the fact that the SQL user we use to connect to the database for reports didn't have permissions to the view the new report was based on. Once I added the permissions, everything worked fine.