Invalid version format (non-numeric data) at C:/HelpDesk/OTR

[abar43]

Hello Admin,


I am in a bit of a bind. I am getting this error whenever I try to perform any type of activity on a ticket. I read through the forum, but all the references
I see are either in German or they don't have much information regarding a fix. I am running OTRS 3.0 ON A Windows box.
Please advise. Could you please help me fix it?

Software error:

Invalid version format (non-numeric data) at C:/HelpDesk/OTRS/OTRS//Kernel/System/Log.pm line 160.

For help, please send mail to the webmaster (webmaster@somenet.com), giving this error message and the time and date of the error.

[crythias]

resolution: ticket_type table did not have an entry for id=1. Added it via sql and this resolved the issue.

[GKramer]

I have the same problem. How can I add this entry?

Thanks for help!

[crythias]

You should use an insert statement. If you install MySQL WorkBench, you can do it via gui. Otherwise, you'll need to do it via command line.

Theoretically, it'd be mysql -u otrsdbusername -p otrsdbpassword otrsdbname
and then apply an insert statement to ticket_type.

INSERT INTO `ticket_type` (`id`, `name`, `valid_id`, `create_time`, `create_by`, `change_time`, `change_by`) VALUES
(1, 'default1', 1, '2010-09-17 23:20:33', 1, '2010-09-17 23:20:33', 1);

Your results may vary. Back up db first. This may not be your issue. If your otrs logs don't indicate a ticket type id=1 problem, this won't fix your problem. otrs db connection information should exist in Config.pm

[GKramer]

I found the following error in the otrs.log

[Tue Aug 16 11:34:15 2011][Error][Kernel::System::Ticket::HistoryAdd][6792] Duplicate entry '1684667' for key 'PRIMARY', SQL: 'INSERT INTO ticket_history (name, history_type_id, ticket_id, article_id, queue_id, owner_id, priority_id, state_id, type_id, valid_id, create_time, create_by, change_time, change_by) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, current_timestamp, ?, current_timestamp, ?)'

I was able to repair the table "ticket_history"with SQLyog. Now, OTRS works fine without any errors.

[HervE]

Hello GKramer,

It seems I have exactly the same problem as you.
I'm afraid my table "ticket_history" became corrupted for some reason.

What did you do to repair it?
(I'm downloading SQLyog at the moment.)

Edited:
OK, I found how to do it with SQLyog.
1. Menu Tools > Table Diagnostics... > Check...
=> It showed that the table was corrupted as I guessed.
2. Menu Tools > Table Diagnostics... > Repair...
=> Everything works fine again.

Regards,
HervE