The context of the problem obviously helps here. I'd verify the privileges assigned to the user you are scanning with. Probably does not have access to the information_schema table in the first place, which is causing the problem. Or it needs to be qualified in such a way that's not set up in the sql scanning configuration file (which is modifiable, by the way, so you can "customize" that query used to select the tables that should be scanned).
I'm guessing it's the permissions though. Log in through SQL with that user and try to select on that table to verify.