Upgraded from 2.0.4 to 2.0.5 now scripts aren't showing

[udfxrookie]

Not sure if there are more problems... I'm sure I'll find out as we go but I did the upgrade from 2.0.4 to 2.0.5 via: http://hemantsharma221.blogspot.com/201 ... grade.html

Everything seemed to work great but I just tried to create a script and save it and it doesn't show an error rather says completed but doesn't show the script.

What's going wrong here and what other potential problems could I be facing but not seeing?



ViciDial VERSION: 2.0.5-173
BUILD: 90320-0424

[udfxrookie]

uhhhh ohhh, lists aren't showing up either.

[williamconley]

When you executed this:

Code: Select all

mysql
use asterisk
\. /usr/src/astguiclient/extras/upgrade_2.0.5.sql
quit

Were there any errors? (If so, lines after the error will not execute and will need to be run!).

If unsure (ie: you closed that window and/or were not capturing your putty screen to disk for later perusal) ...

Check your Admin->System Settings and get your db_schema_version. If it does not match the version at the end of the 2.0.5 sql upgrade script ... you'll need to find it and execute all the sql lines after it to bring it up to the 2.0.5 version.

Make a copy of the file, delete everything before your schema version ... and execute it (and watch for errors this time!).

[udfxrookie]

I get tons of errors:

Code: Select all

ERROR 1060 (42S21): Duplicate column name 'xfercallid'
ERROR 1050 (42S01): Table 'vicidial_user_closer_log' already exists
ERROR 1060 (42S21): Duplicate column name 'qc_enabled'
ERROR 1060 (42S21): Duplicate column name 'qc_user_level'
ERROR 1060 (42S21): Duplicate column name 'qc_pass'
ERROR 1060 (42S21): Duplicate column name 'qc_finish'
ERROR 1060 (42S21): Duplicate column name 'qc_commit'
ERROR 1060 (42S21): Duplicate column name 'qc_allowed_campaigns'
ERROR 1060 (42S21): Duplicate column name 'qc_allowed_inbound_groups'
ERROR 1060 (42S21): Duplicate column name 'db_schema_version'


I thought those just over wrote the old entry

[williamconley]

Check your Admin->System Settings and get your db_schema_version. If it does not match the version at the end of the 2.0.5 sql upgrade script ...

[udfxrookie]

omg, now I'm freaking a bit. I did everything on the new server according to the SVN upgrade viewtopic.php?f=8&t=16326 to get my familiar vicidial back from the 2.2 to 2.4... I ran the scripts and my schema was 1193 so everything was left in the scripts. They ran with no errors, I rebooted and try to log in and see nothing. No users, no scripts... I still see user groups, when I try clicking Admin to rebuild the conf files it says I don't have permission when I click modify... what happened?!?!?

[williamconley]

did you read the upgrade document in your downloaded code?

[udfxrookie]

Will, Thank you, thank you and thank you. Going off those instructions worked like a charm, first shot! The only issue we have now are callbacks are set to be active but when the agent schedules the callback it doesn't show. We also have a problem when transferring the customer from a front campaign to a closer campaign the fronter is staying connected to the call even though their screen shows the disposition screen... On show all calls you can see the fronter too.

[williamconley]

did you verify/confirm that all the sql commands executed without error all the way to the end of the file? does your db_schema in system settings now match the db_schema that is LAST in the sql upgrade script?

[udfxrookie]

Yes to the schema, and i didn't see any errors

[williamconley]

You may want to consider exporting your lists and reinstalling a fresh system and re-uploading the lists into the fresh system. 2.0.4 is freakin' old and if you had anyone modify any of your database tables there could have been a conflict that may take a long time to resolve. Depending on whether you're capable of a reinstall or have another machine you can port this data to and get it "live" before taking this machine down.