Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.When the module is Enabled and database Connections are inserted properly in settings page . The error comes as shown below
* user warning: Table 'techamor_drpl3.usergroup' doesn't exist query: SELECT usergroupid, title FROM usergroup in /home/techamor/public_html/includes/database.mysql.inc on line 128.
* user warning: Table 'techamor_drpl3.setting' doesn't exist query: SELECT varname, value FROM setting in /home/techamor/public_html/sites/all/modules/drupalvb/drupalvb.inc.php on line 268.
This Error then keeps showing on every page.
Comments
Comment #1
iVaibhav commentedComment #2
sophrinix commentedThis isn't a problem with the module, this is a failure of the module connecting to your vbforums database.
Try this:
*Deploy a new instance of drupal.
*Download a fresh copy of this module
*Point this module to the vbulletin database.
Watch this issue not show up.
Once this issue does not show up, do the same thing with your production side. Make sure that your database connection to vbulletin is there!
If it does show up, make sure you have the user on the vbulletin fourm database set up to allow the connection to happen (especially if this is a remote connection)
Make sure the password and username are correctly entered on the config for this module.
Make sure you are pointing to the correct database name.
If all of these steps are done and you are still having a problem. Check for firewalls.
This works fine for me, and I have done quiet a bit to my drupal and vbulletin setup that is not stock.
It also works perfect for me when stock.
I ran into this issue of the usergroup table not recognizing as well. The solution was to make sure that the remote database connection is really happening.
Happy Hacking.
Comment #3
Griffin80 commentedDid u ever fix this problem because im getting it as well?
Comment #4
mattwmc commented3 years later, but what worked for me was putting the following in the Table Prefix at the Datebase Settings (admin/settings/drupalvb/database):