Hi Michiel, thanks! It looks like this problem only exists in the 2.2 -> 2.3 upgrade when using a 3.0 OTRS. The problem I'm having is that I am on Windows (I know don't get me started). I'm guessing that unzipping the tarball and using the Kernel directory should work as well. Thanks, Arnold. Op 21-6-2011 16:17, Michiel Beijen schreef:

Hi Arnold,

If upgrading from 2.2 or earlier you'll have to take an extra step, see http://bugs.otrs.org/show_bug.cgi?id=6798

(it's referred to in UPGRADING: http://source.otrs.org/viewvc.cgi/otrs/UPGRADING?revision=1.49.2.3&view=co)

-- Michiel

On Tue, Jun 21, 2011 at 15:35, wrote:

...

Hi,

I'm currently upgrading a system from 2.2.7 to 3.0.8. When I run the mysql upgrade scripts automatically not all commands are executed, but if I run the commands manually then the database seems to update fine. The perl update scripts however generate a lot of errors (unknow column st.archive_flag and 'need id or name'). This is the upgrade from 2.2 to 2.3 running the DBUpdate-to-3.0.pl script.

It seems the errors are related to the otrs/Kernel/System/Ticket.pm and DB.pm. These are of course version 3.0.8 already as I installed 3.0.8 on the new server. Should these files also be 2.3 or can I ignore the errors?

In other words: when I upgrade the db over multiple versions do I also need to install the complete otrs versions or will running the upgrade scripts from the newest version work as well? It's a 14Gb database, so near impossible to manually check if all upgrades succeeded.

Regards, Arnold. --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs