vicidial.org

Hi,

We are running vicibox 5.0.3 32 bit on an IBM HS21 2 X Dual Core Xeon 3.0 GHz with 8GB of RAM and 72 GB of functional hard drive. This is a small setup meant for around 10 agents. The server runs the database, the dialer, the webserver, etc.

We upgraded from vicibox 3.1.15 to vicibox 5.0.3 by using the upgrade scripts and instructions. It has been working with no difficulties except when we added some new lists with custom fields the database does not seem to be creating the custom_xxx table associated with the lists. I manually copied the structure from another custom list to create the necessary tables but I get this error when I make any changes to the lists: "Could not execute: No database selectedSUCCESS: Custom Field Modified"

Despite the errors, the changes I am requesting on the custom fields page are being made. Not sure why the custom fields function is not working correctly but would love to see a resolution as this system uses them pretty extensively and manually creating the tables each time is a bit bothersome.

It's most likely a database permissions issue. I haven't tested that specifically coming from vicibox 3, but that could be the issue. You should make sure that your mysql database user table has a "custom" user in it, and if not, follow the SCRATCH_INSTALL.txt doc instructions for adding one "GRANT ...."

The upgrade script does not upgrade you to ViciBox v.5.0.3. It only updates your database schema, SVN version on disk, and create a compatible ViciBox v.4+ table in the database. Unless you re-installed the operating system you are still running ViciBox v.3. You need to go through the ViciBox upgrade threads as well as the UPGRADE document located at /usr/src/astguiclient/trunk to make sure you have the right stuff in place. You are probably also going to be missing some perl modules for some functionality like email, etc.

More then likely you need to add the custom user and password. Assuming it's the default, you can add them by running the following SQL query: grant create,alter to 'custom'@'%' identified by 'custom1234';

Kumba, yeah, I upgraded the existing machine, then build a new one on 5.0.3 and restored the database from the old one to the new one. I think the issue is with the custom user not existing or not having permissions to the new database as Matt indicated.

Thanks guys!