try to runa a rebiuld index cron job manually Ciao AleX Tosi Alessio Sistemi Informativi OKI Systems (Italia) S.p.A. Tel. +39 0290026812 Mob. +39 3486024492 Any opinions expressed in this email are those of the individual and not necessarily of the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company are confidential and solely for the use of the intended recipient. It may contain material protected by legal privilege. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. Please notify the sender immediately of the error and delete any copies of this message Warning: The Company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments. -----Original Message----- From: Graham Leggett [mailto:minfrin@sharp.fm] Sent: Friday, April 18, 2008 1:32 AM To: otrs@otrs.org Subject: [otrs] Upgrade to 2.2.6 fails: Can't use an undefined value as a HASH reference at ../..//Kernel/System/Ticket/Article.pm line 1409. Hi all, After upgrading OTRS v2.0.4 to v2.2.6 using the instructions in UPGRADING, my OTRS fails with the following error: Can't use an undefined value as a HASH reference at ../..//Kernel/System/Ticket/Article.pm line 1409. Google leads me to the following FAQ entry, which suggests this problem occurs after an upgrade to v2.2.2: http://faq.otrs.org/otrs/public.pl?Action=PublicFAQ&ItemID=192 It suggests that I run the following sql to fix this: ALTER TABLE ticket ADD escalation_response_time INTEGER; ALTER TABLE ticket ADD escalation_solution_time INTEGER; This fails, because the columns have already been added by the DB migration script. Does anyone have any further reasons why this error should occur, apart from the missing columns referred to in the FAQ, which in this case are not missing? Regards, Graham --