Re: [otrs] TaskID Error

I had to manually reload the database from a prior dump. I have not made any additions/changes to the code. Everything is working except for this error. Any idea on how I can troubleshoot this? On 9/27/2016 5:09 PM, Carlos Rodríguez wrote:

Hi Kent,

This should only happens if you call TaskLock() without the TaskID parameter, have you change or installed something in your system?

((enjoy))

Carlos Rodríguez

...

On Sep 27, 2016, at 3:16 PM, Kent Kollasch mailto:kent@artsway-mfg.com> wrote:

Has anyone seen the following error or know how to fix it?

{Error][Kernel ::System::Daemon::SchedulerDB::TaskLock][459] Need TaskID!

It's filling up my log file..

-- Kent C. Kollaschmailto:Kent.Kollasch@artsway-mfg.com Director of Information Technology Art's-Way Manufacturing Co., Inc. Phone: (712) 864-0025 Fax: (712) 864-3154

This message may contain information that is confidential and subject to privilege. If you are not the intended recipient and have received this e-mail in error, please disregard and do not open attachments, if any. Please note that the view or opinions presented in this e-mail are solely those of the author. --------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs

--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs

-- Kent C. Kollasch mailto:Kent.Kollasch@artsway-mfg.com Director of Information Technology Art's-Way Manufacturing Co., Inc. Phone: (712) 864-0025 Fax: (712) 864-3154 This message may contain information that is confidential and subject to privilege. If you are not the intended recipient and have received this e-mail in error, please disregard and do not open attachments, if any. Please note that the view or opinions presented in this e-mail are solely those of the author.