Hallo,

noch mal ich:

Ich habe nun ein weiteres mal folgendes gemacht auf einem blanken System:

- Debian installiert inkl. OTRS 2.0.4 und Datenbank (MySQL)
- alte Datenbank importiert (OTRS 1.3)
- DBUPDATE SQL File 2.0 ausgeführt.

Es klappt soweit alles, bis auf ein paar Sachen:

- Darstellung eigener Queues ist fehlhaft, wenn mehrere Tickets enthalten sind.

- Ich bekomme die Queues zwar namentlich angezeigt, kann sie als ADMIN aber 
nicht ändern, da ihm die Queue ID fehlt.
Mails lassen sich zwar problemlos und auch korrekt ins Ticketsystem schreiben 
via Email, jedoch kann ich keine neuen Tickets aus OTRS heraus erstellen, da 
die Queues fehlen.
Ich vermute die Fehlermeldung die der PostMasterPOP3.pl ausgibt, hängt 
ebenfalls hiermit zusammen:


homer:/usr/share/otrs/bin# ./PostMasterPOP3.pl
Message 1/1 ([EMAIL PROTECTED])
DBD::mysql::db do failed: Unknown column 'queue_id' in 'field list' at 
/usr/share/otrs/Kernel/System/DB.pm line 376, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:27 2006

 Message: Unknown column 'queue_id' in 'field list', SQL: 'INSERT INTO 
ticket_history  (name, history_type_id, ticket_id, article_id, queue_id, 
owner_id,  priority_id, state_id, valid_id,  create_time, create_by, 
change_time, change_by) VALUES ('%%lock', 21, 32786,  NULL, 9, 4, 3,  2, 1,  
current_timestamp, 1, current_timestamp, 1)'

 Traceback (1512): 
   Module: Kernel::System::Ticket::HistoryAdd (v1.194) Line: 3647
   Module: Kernel::System::Ticket::LockSet (v1.194) Line: 2595
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 74
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::db do failed: Unknown column 'queue_id' in 'field list' at 
/usr/share/otrs/Kernel/System/DB.pm line 376, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Unknown column 'queue_id' in 'field list', SQL: 'INSERT INTO 
ticket_history  (name, history_type_id, ticket_id, article_id, queue_id, 
owner_id,  priority_id, state_id, valid_id,  create_time, create_by, 
change_time, change_by) VALUES ('Reset of unlock time.', 29, 32786,  NULL, 9, 
4, 3,  2, 1,  current_timestamp, 1, current_timestamp, 1)'

 Traceback (1512): 
   Module: Kernel::System::Ticket::HistoryAdd (v1.194) Line: 3647
   Module: Kernel::System::Ticket::TicketUnlockTimeoutUpdate (v1.194) Line: 850
   Module: Kernel::System::Ticket::LockSet (v1.194) Line: 2604
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 74
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::db do failed: Unknown column 'queue_id' in 'field list' at 
/usr/share/otrs/Kernel/System/DB.pm line 376, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Unknown column 'queue_id' in 'field list', SQL: 'INSERT INTO 
ticket_history  (name, history_type_id, ticket_id, article_id, queue_id, 
owner_id,  priority_id, state_id, valid_id,  create_time, create_by, 
change_time, change_by) VALUES ('%%closed successful%%open%%', 32, 32786,  
NULL, 9, 4, 3,  4, 1,  current_timestamp, 1, current_timestamp, 1)'

 Traceback (1512): 
   Module: Kernel::System::Ticket::HistoryAdd (v1.194) Line: 3647
   Module: Kernel::System::Ticket::StateSet (v1.194) Line: 2737
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 107
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::db do failed: Unknown column 'queue_id' in 'field list' at 
/usr/share/otrs/Kernel/System/DB.pm line 376, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Unknown column 'queue_id' in 'field list', SQL: 'INSERT INTO 
ticket_history  (name, history_type_id, ticket_id, article_id, queue_id, 
owner_id,  priority_id, state_id, valid_id,  create_time, create_by, 
change_time, change_by) VALUES ('Reset of escalation time.', 29, 32786,  NULL, 
9, 4, 3,  4, 1,  current_timestamp, 1, current_timestamp, 1)'

 Traceback (1512): 
   Module: Kernel::System::Ticket::HistoryAdd (v1.194) Line: 3647
   Module: Kernel::System::Ticket::TicketEscalationStartUpdate (v1.194) Line: 
898
   Module: Kernel::System::Ticket::StateSet (v1.194) Line: 2746
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 107
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::st execute failed: Unknown column 'q.default_sign_key' in 'field 
list' at /usr/share/otrs/Kernel/System/DB.pm line 440, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Unknown column 'q.default_sign_key' in 'field list', SQL: 'SELECT 
q.name, q.group_id, q.unlock_timeout,  q.system_address_id, q.salutation_id, 
q.signature_id, q.comments, q.valid_id,  q.escalation_time, q.follow_up_id, 
q.follow_up_lock, sa.value0, sa.value1, q.id,  q.move_notify, q.state_notify, 
q.lock_notify, q.owner_notify, q.default_sign_key  FROM  queue q, 
system_address sa WHERE  q.system_address_id = sa.id  AND  q.id = 9'

 Traceback (1512): 
   Module: Kernel::System::Queue::QueueGet (v1.57) Line: 796
   Module: Kernel::System::Ticket::Article::ArticleGet (v1.94) Line: 1075
   Module: Kernel::System::Ticket::Article::ArticleLastCustomerArticle (v1.94) 
Line: 741
   Module: Kernel::System::Ticket::Article::SendCustomerNotification (v1.94) 
Line: 1644
   Module: Kernel::System::Ticket::StateSet (v1.194) Line: 2755
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 107
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::st fetchrow_array failed: fetch() without execute() at 
/usr/share/otrs/Kernel/System/DB.pm line 477, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Found no $ID for 9!

 Traceback (1512): 
   Module: Kernel::System::Queue::QueueGet (v1.57) Line: 823
   Module: Kernel::System::Ticket::Article::ArticleGet (v1.94) Line: 1075
   Module: Kernel::System::Ticket::Article::ArticleLastCustomerArticle (v1.94) 
Line: 741
   Module: Kernel::System::Ticket::Article::SendCustomerNotification (v1.94) 
Line: 1644
   Module: Kernel::System::Ticket::StateSet (v1.194) Line: 2755
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 107
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::st execute failed: Unknown column 'q.default_sign_key' in 'field 
list' at /usr/share/otrs/Kernel/System/DB.pm line 440, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Unknown column 'q.default_sign_key' in 'field list', SQL: 'SELECT 
q.name, q.group_id, q.unlock_timeout,  q.system_address_id, q.salutation_id, 
q.signature_id, q.comments, q.valid_id,  q.escalation_time, q.follow_up_id, 
q.follow_up_lock, sa.value0, sa.value1, q.id,  q.move_notify, q.state_notify, 
q.lock_notify, q.owner_notify, q.default_sign_key  FROM  queue q, 
system_address sa WHERE  q.system_address_id = sa.id  AND  q.id = 9'

 Traceback (1512): 
   Module: Kernel::System::Queue::QueueGet (v1.57) Line: 796
   Module: Kernel::System::Ticket::Article::SendCustomerNotification (v1.94) 
Line: 1646
   Module: Kernel::System::Ticket::StateSet (v1.194) Line: 2755
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 107
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::st fetchrow_array failed: fetch() without execute() at 
/usr/share/otrs/Kernel/System/DB.pm line 477, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Found no $ID for 9!

 Traceback (1512): 
   Module: Kernel::System::Queue::QueueGet (v1.57) Line: 823
   Module: Kernel::System::Ticket::Article::SendCustomerNotification (v1.94) 
Line: 1646
   Module: Kernel::System::Ticket::StateSet (v1.194) Line: 2755
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 107
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::db do failed: Unknown column 'queue_id' in 'field list' at 
/usr/share/otrs/Kernel/System/DB.pm line 376, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Unknown column 'queue_id' in 'field list', SQL: 'INSERT INTO 
ticket_history  (name, history_type_id, ticket_id, article_id, queue_id, 
owner_id,  priority_id, state_id, valid_id,  create_time, create_by, 
change_time, change_by) VALUES ('%%6632844%%', 2, 32786,  126583, 9, 4, 3,  4, 
1,  current_timestamp, 1, current_timestamp, 1)'

 Traceback (1512): 
   Module: Kernel::System::Ticket::HistoryAdd (v1.194) Line: 3647
   Module: Kernel::System::Ticket::Article::ArticleCreate (v1.94) Line: 173
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 158
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::st execute failed: Unknown column 'q.default_sign_key' in 'field 
list' at /usr/share/otrs/Kernel/System/DB.pm line 440, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Unknown column 'q.default_sign_key' in 'field list', SQL: 'SELECT 
q.name, q.group_id, q.unlock_timeout,  q.system_address_id, q.salutation_id, 
q.signature_id, q.comments, q.valid_id,  q.escalation_time, q.follow_up_id, 
q.follow_up_lock, sa.value0, sa.value1, q.id,  q.move_notify, q.state_notify, 
q.lock_notify, q.owner_notify, q.default_sign_key  FROM  queue q, 
system_address sa WHERE  q.system_address_id = sa.id  AND  q.id = 9'

 Traceback (1512): 
   Module: Kernel::System::Queue::QueueGet (v1.57) Line: 796
   Module: Kernel::System::Ticket::GetSubscribedUserIDsByQueueID (v1.194) Line: 
1741
   Module: Kernel::System::Ticket::Article::ArticleCreate (v1.94) Line: 370
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 158
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126

DBD::mysql::st fetchrow_array failed: fetch() without execute() at 
/usr/share/otrs/Kernel/System/DB.pm line 477, <PRODUCT> line 4.
ERROR: OTRS-PM3-66 Perl: 5.8.8 OS: linux Time: Fri Mar 17 18:27:28 2006

 Message: Found no $ID for 9!

 Traceback (1512): 
   Module: Kernel::System::Queue::QueueGet (v1.57) Line: 823
   Module: Kernel::System::Ticket::GetSubscribedUserIDsByQueueID (v1.194) Line: 
1741
   Module: Kernel::System::Ticket::Article::ArticleCreate (v1.94) Line: 370
   Module: Kernel::System::PostMaster::FollowUp::Run (v1.40) Line: 158
   Module: Kernel::System::PostMaster::Run (v1.52) Line: 212
   Module: main::FetchMail (v1.17) Line: 198
   Module: ./PostMasterPOP3.pl (v1.17) Line: 126


Connection to 198.xxx.xxx.xxx closed.

Natürlich ist DBD-MySQL-perl installiert. Hat jemand noch eine Idee wie ich die 
Zuordnung zu den Queues wieder herstellen kann?

mit freundlichen Grüßen
 
Robert Simon
 
----------------------------------------------------------------------------
[netclusive] internet broadcasting GmbH
Robert-Bosch-Str. 10, Haus I                                      
D-56410 Montabaur               
phone: +49 (0) 2602 / 94 708 - 0
fax: +49 (0) 2602 / 94 708 - 299                        
http://www.netclusive.de
----------------------------------------------------------------------------
 
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen. 
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten 
haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail. 
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht 
gestattet.
 
This e-mail may contain confidential and/or privileged information. If you are 
not the intended recipient (or have received this e-mail in error) please 
notify the sender immediately and destroy this e-mail. Any unauthorised 
copying, disclosure or distribution of the material in this e-mail is strictly 
forbidden. 

-----Ursprüngliche Nachricht-----
Von: Konrad Beyer [mailto:[EMAIL PROTECTED] 
Gesendet: Freitag, 17. März 2006 11:55
An: 'User questions and discussions about OTRS.org in German'
Betreff: RE: [otrs-de] Fehler nach "Update" von OTRS

 
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hallo,

> es gibt eine Datei die die letzte Ticketnummer enthält. 

die Ticketnummer wird in
[otrs-root]/var/log/TicketCounter.log
gespeichert. Dort die aktuelle Ticketnummer eintragen.


Mit freundlichen Grüßen

Konrad Beyer
Consultant

************************************************
avus Services GmbH
Industriestrasse 28
70565 Stuttgart

Telefon:           +49-711-22062-124
Fax:               +49-711-22062-110
e-mail:            [EMAIL PROTECTED]
Internet:          www.avus-services.de
************************************************

-----BEGIN PGP SIGNATURE-----
Version: PGP 7.1

iQA/AwUBRBqVAGBmCMMyecP5EQJvggCfVwz8R15nDdY5O/vFB3e1FZF3A0oAoLo8
cWzMs7wo6cVfC271U2lHyaWr
=Rc9G
-----END PGP SIGNATURE-----
_______________________________________________
OTRS Mailingliste: otrs-de - Webpage: http://otrs.org/
Archiv: http://lists.otrs.org/pipermail/otrs-de/
Listenabo verwalten: http://lists.otrs.org/cgi-bin/listinfo/otrs-de/
Support oder Consulting fuer Ihr OTRS System?
=http://www.otrs.de/





_______________________________________________
OTRS Mailingliste: otrs-de - Webpage: http://otrs.org/
Archiv: http://lists.otrs.org/pipermail/otrs-de/
Listenabo verwalten: http://lists.otrs.org/cgi-bin/listinfo/otrs-de/
Support oder Consulting fuer Ihr OTRS System?
=> http://www.otrs.de/

Antwort per Email an