Frank Wakelin wrote:
Actually, after using the "force" option (sorry, missed that) I can see the tickets again. However I received a number of errors while runningthe upgrade script still - are these normal?ERROR 1050 (42S01) at line 15: Table 'customer_company' already exists ERROR 1050 (42S01) at line 49: Table 'ticket_type' already exists ERROR 1062 (23000) at line 60: Duplicate entry 'default' for key 2 ERROR 1050 (42S01) at line 107: Table 'service' already exists ERROR 1050 (42S01) at line 125: Table 'service_customer_user' already exists ERROR 1050 (42S01) at line 138: Table 'sla' already exists Are these normal, or can I expect other problems?
What installation method do you use? RPM? If so, I believe the postinstall scriplet already performs the database schema update, so if you run it again you can expect those 'already exists' messages.
Nils Breunese.
PGP.sig
Description: Dit deel van het bericht is digitaal ondertekend
_______________________________________________ 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 Support or consulting for your OTRS system? => http://www.otrs.com/
