Hi! I´m testing OTRS 1.1.2 on Suse Linux 8.2 Prof. In the customer interface, the following error occours while creating a new ticket (via customer-login): Fehler: Need TicketID! /tmp/otrs.log: [Error] [Kernel::System::Ticket::State::StateLookup] [74] No StateID for new found! [Error] [Kernel::System::Ticket::CreateTicketDB] [189] No StateID!!! Regards Guenther
Hi Guenther, On Wed, Jul 02, 2003 at 08:37:07AM +0200, Guenther Rasch wrote:
I´m testing OTRS 1.1.2 on Suse Linux 8.2 Prof. In the customer interface, the following error occours while creating a new ticket (via customer-login):
Fehler: Need TicketID!
/tmp/otrs.log:
[Error] [Kernel::System::Ticket::State::StateLookup] [74] No StateID for new found! [Error] [Kernel::System::Ticket::CreateTicketDB] [189] No StateID!!!
It looks like your database setup is corrupt. Try to setup your OTRS database new and it will work.
Guenther
-Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ --
Hi Martin, Martin Edenhofer schrieb:
Hi Guenther,
On Wed, Jul 02, 2003 at 08:37:07AM +0200, Guenther Rasch wrote:
I´m testing OTRS 1.1.2 on Suse Linux 8.2 Prof. In the customer interface, the following error occours while creating a new ticket (via customer-login):
Fehler: Need TicketID!
/tmp/otrs.log:
[Error] [Kernel::System::Ticket::State::StateLookup] [74] No StateID for new found! [Error] [Kernel::System::Ticket::CreateTicketDB] [189] No StateID!!!
It looks like your database setup is corrupt.
Try to setup your OTRS database new and it will work.
did it and it works. It seems there´s a problem changing the status (admin screen) - after changing it, the some error occours again.... Guenther
-Martin
-- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ --
_______________________________________________ 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
Hi Guenther, On Thu, Jul 03, 2003 at 07:30:37PM +0200, Guenther Rasch wrote:
[...] It looks like your database setup is corrupt.
Try to setup your OTRS database new and it will work.
did it and it works. It seems there´s a problem changing the status (admin screen) - after changing it, the some error occours again....
Oh... if you change the default states, also update the default states in your Kernel/Config.pm For details: http://doc.otrs.org/1.1/html/state.html And it will work again! :)
Guenther
-Martin -- Martin Edenhofer - <martin at edenhofer.de> - http://martin.edenhofer.de/ --
participants (2)
-
Guenther Rasch -
Martin Edenhofer