In my situation, we had a linked server that was accessed from the reports. The database had the correct permission through a linked server, the account that the reports used had the right permission, but the linked server was not setup to allow the report account through (the linked server). Once that account was added with impersonation to the linked server, the error went away.