Check existing framework tables fail after update to 3.1

[NickGnd]

Hi everybody,
Yesterday i updated from OTRS 3.0 to OTRS 3.1 and now in ADMIN -> Support Assessment i've got this error:

Check existing framework tables.

virtual_fs[Operation failed] virtual_fs_preferences[Operation failed] virtual_fs_db[Operation failed]

OTRS doesn't find three tables and infact in the db there aren't these tables.

Why? Someone can help me please?

Thanks.

Nico

[sarioto]

I've encountered this problem as well.

This is due to
1. when you updated to 3.0 from 2.*
2. This Script was supposed to be executed 'sudo ./DBUpdate-to-3.0.pl' (in /otrs/scripts folders)
3. This Script creates these TABLES
4. you can run the script again to create these Tables and fix you problem

Problems:
You dont or shouldnt have the Theme Table in the Database no longer, which the script will look for and fail..
You will have to comment out some Line in the script, then run it..

script version 1.5
Find the Bellow and comment then out as shown

Code: Select all

    print "\nMigration started...\n\n";

    # create common objects
    my $CommonObject = _CommonObjectsBase();

    print "Step 1 of 5: Refresh configuration cache... ";
#    RebuildConfig($CommonObject);
    print "done.\n\n";

    # create common objects with new default config
#    $CommonObject = _CommonObjectsBase();

    print "Step 2 of 5: Migrating theme configuration... ";
#    MigrateThemes($CommonObject);
    print "done.\n\n";

    # create common objects with new default config
#    $CommonObject = _CommonObjectsBase();

    print "Step 3 of 5: Cleaning up the permission table... ";
    PermissionTableCleanup($CommonObject);
    print "done.\n\n";

Run script sudo ./DBUpdate-to-3.0.pl

Migration started...

Step 1 of 5: Refresh configuration cache... done.

Step 2 of 5: Migrating theme configuration... done.

Step 3 of 5: Cleaning up the permission table... done.

Step 4 of 5: Cleanup pending time of tickets without pending state-type... done.

Step 5 of 5: Creating VirtualFS tables (if necessary)... done. <<<<-------See here

Migration completed!

Verified Mysql Tables

| valid |
| virtual_fs |
| virtual_fs_db |
| virtual_fs_preferences |
| web_upload_cache |
| xml_storage |
+------------------------------+
73 rows in set (0.00 sec)

Problem Fixed - Error gone

This is what happened to me, and how i went around fixing the error