Upgrading Custom Vocab module: Table already exists error message

I’m wondering if anyone else came across an error when upgrading their Custom Vocab module to version 2.0.1 that states a table already exists in the database so the module couldn’t be installed?

Once I went into the database and deleted the “custom_vocab” table in our test database, the module installed successfully. However, this is not good when you have existing vocabularies that need to be re-added manually back into the admin.

Any insights would be helpful to prevent this from happening.

CustomVocab’s upgrade process never tries to create any tables. You used the word “install” so, maybe you had CustomVocab previously marked as not installed and you were actually installing and not upgrading it?