Hello, After Upgrading from OTRS 1.3.1 to 2.0.2 I follow step by step the "$OTRS_HOME/UPGRADING" File. I execute the follwing script and I get this error message for an existing ticket number : $ /usr/local/otrs2/bin/PostMasterPOP3.pl Message 1/1 (support@toto.com) ERROR: OTRS-PM3-10 Perl: 5.8.3 OS: linux Time: Wed Sep 28 13:53:17 2005 Message: Need StateID or State! Traceback (20012): Module: Kernel::System::Ticket::StateSet (v1.184) Line: 2578 Module: Kernel::System::PostMaster::FollowUp::Run (v1.38) Line: 81 Module: Kernel::System::PostMaster::Run (v1.52) Line: 212 Module: main::FetchMail (v1.16) Line: 198 Module: /usr/local/otrs2/bin/PostMasterPOP3.pl (v1.16) Line: 126 --------------- For a non-existing ticket number I get this : ------------- Begin Traceback (20104): Module: Kernel::System::Ticket::PriorityLookup (v1.184) Line: 3009 Module: Kernel::System::Ticket::TicketCreate (v1.184) Line: 339 Module: Kernel::System::PostMaster::NewTicket::Run (v1.52) Line: 162 Module: Kernel::System::PostMaster::Run (v1.52) Line: 239 Module: main::FetchMail (v1.16) Line: 198 Module: ./PostMasterPOP3.pl (v1.16) Line: 126 Use of uninitialized value in concatenation (.) or string at /usr/local/otrs2/Ke rnel/System/Ticket.pm line 362. DBD::mysql::db do failed: You have an error in your SQL syntax near ' 1, 0, 112 7911480, 0, 1, current_timestamp, 1, current_timestamp, 1)' at line 1 at /usr/l ocal/otrs2/Kernel/System/DB.pm line 330. ERROR: OTRS-PM3-10 Perl: 5.8.3 OS: linux Time: Wed Sep 28 14:44:40 2005 Message: You have an error in your SQL syntax near ' 1, 0, 1127911480, 0, 1, current_timestamp, 1, current_timestamp, 1)' at line 1, SQL: 'INSERT INTO ticket (tn, title, create_time_unix, queue_id, ticket_lock_id, user_id, group_id, tic ket_priority_id, ticket_state_id, ticket_answered, escalation_start_time, timeo ut, valid_id, create_time, create_by, change_time, change_by) VALUES ('1001549' , 'Files', 1127911480, 5, 1, 1, 1, , 1, 0, 1127911480, 0, 1, current_timestam p, 1, current_timestamp, 1)' Traceback (20104): Module: Kernel::System::Ticket::TicketCreate (v1.184) Line: 370 Module: Kernel::System::PostMaster::NewTicket::Run (v1.52) Line: 162 Module: Kernel::System::PostMaster::Run (v1.52) Line: 239 Module: main::FetchMail (v1.16) Line: 198 Module: ./PostMasterPOP3.pl (v1.16) Line: 126 ERROR: OTRS-PM3-10 Perl: 5.8.3 OS: linux Time: Wed Sep 28 14:44:41 2005 Message: create db record failed!!! Traceback (20104): Module: Kernel::System::Ticket::TicketCreate (v1.184) Line: 410 Module: Kernel::System::PostMaster::NewTicket::Run (v1.52) Line: 162 Module: Kernel::System::PostMaster::Run (v1.52) Line: 239 Module: main::FetchMail (v1.16) Line: 198 Module: ./PostMasterPOP3.pl (v1.16) Line: 126 ERROR: OTRS-PM3-10 Perl: 5.8.3 OS: linux Time: Wed Sep 28 14:44:41 2005 Message: Need TicketID! Traceback (20104): Module: Kernel::System::Ticket::Article::ArticleCreate (v1.91) Line: 84 Module: Kernel::System::PostMaster::NewTicket::Run (v1.52) Line: 208 Module: Kernel::System::PostMaster::Run (v1.52) Line: 239 Module: main::FetchMail (v1.16) Line: 198 Module: ./PostMasterPOP3.pl (v1.16) Line: 126 ERROR: OTRS-PM3-10 Perl: 5.8.3 OS: linux Time: Wed Sep 28 14:44:41 2005 Message: Need TicketID! Traceback (20104): Module: Kernel::System::Ticket::StateSet (v1.184) Line: 2561 Module: Kernel::System::PostMaster::NewTicket::Run (v1.52) Line: 231 Module: Kernel::System::PostMaster::Run (v1.52) Line: 239 Module: main::FetchMail (v1.16) Line: 198 Module: ./PostMasterPOP3.pl (v1.16) Line: 126 ERROR: OTRS-PM3-10 Perl: 5.8.3 OS: linux Time: Wed Sep 28 14:44:41 2005 Message: Can't process email with MessageID <<000a01c5c429$231e78f0$6504010a@de ll>>! Please create a bug report with this email (var/spool/) on http://bugs.otr s.org/! Traceback (20104): Module: Kernel::System::PostMaster::NewTicket::Run (v1.52) Line: 236 Module: Kernel::System::PostMaster::Run (v1.52) Line: 239 Module: main::FetchMail (v1.16) Line: 198 Module: ./PostMasterPOP3.pl (v1.16) Line: 126 Connection to mail.strasbourg.4js.com closed. ------------- End Connection to mail.toto.com closed. Do you know a solution ? In which documentation section should I check ? What should I do ? Olivier ECKERT