Hi David,
(I edited this after posting it for clarity - see marked paragraph)
This looks like an issue with your server. Please read the following article on the mysql docs site:
http://dev.mysql.com/doc/refman/5.0/en/innodb-troubleshooting-datadict.html
It looks like your data dictionary is out of sync. Specifically you have a .frm file that exists in your schema for wfHoover but there is no corresponding data dictionary in the InnoDB file. (read the article to understand how mysql maintains two separate dictionaries)
Edit: (adding this for clarity) Please note that we don't control how frm files are created or deleted or the integrity of the InnoDB and mysql data dictionary so this really can't be our fault. We just run standard SQL create/delete statements and don't even force a specific table type - we just use the default. And we're using InnoDB on our own servers so there's no known incompatibility there.
So I think there are a few possibilities:
1. You ran out of disk space and an frm file was created but the server could not update the innodb dictionary during update.
2. You have disk corruption and the innodb file was not updated or the frm was not deleted during plugin installation or deinstallation respectively.
3. You changed your storage engine from MyISAM to InnoDB and frm files were left behind that is confusing mysql.
4. Your server crashed, was suddenly rebooted or you had a memory or other issue that caused corruption in the innodb table file.
We have had no other reports of this, so for now please unmark our plugin as broken until you can either confirm that it is our plugin causing this or we figure out that it's something else.
Let me know if you think it may be one of the above. Also let me know if you're using the "innodb_file_per_table = 1" option in your my.cnf which will result in each table having it's own file in innodb or whether you have one monolithic innodb file (the default).
Mark.