Everything was working fine under 3.3 and yesterday after i upgrade from 3.3 to 4, I am getting below error logs and not receiving automated emails now.
Wed Nov 26 13:57:28 2014 error OTRS-CGI-00 Invalid UserSendNewTicketNotification option '1' for user 'boda.badru'
Wed Nov 26 13:57:28 2014 error OTRS-CGI-00 Invalid UserSendNewTicketNotification option '1' for user 'ravikrishna'
Wed Nov 26 13:57:28 2014 error OTRS-CGI-00 Invalid UserSendNewTicketNotification option '1' for user 'mahesh.s'
Wed Nov 26 13:57:28 2014 error OTRS-CGI-00 Invalid UserSendNewTicketNotification option '1' for user 'ramesh.junuvala'
Wed Nov 26 13:57:28 2014 error OTRS-CGI-00 Invalid UserSendNewTicketNotification option '1' for user 'krishnakumar.singh'
Wed Nov 26 13:57:28 2014 error OTRS-CGI-00 Invalid UserSendNewTicketNotification option '1' for user 'tpraveen.kumar'
Error after Upgrade from 3.3 to 4
Moderator: crythias
Re: Error after Upgrade from 3.3 to 4
review the settings for these users and set them new
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 76
- Joined: 01 Sep 2012, 09:51
- Znuny Version: 5.0.16
- Real Name: Vinesh Narayanan
- Company: NTS
Re: Error after Upgrade from 3.3 to 4
Hi Jojo thanks for your quick reply...before upgrade from 3.3 to 4 everything was working perfectly...issue is after upgrade and this users are agents and get all notifications while creating and closing tickets.
i did not get you "review the settings for these users and set them new" can you please be clear. Thanks.
i did not get you "review the settings for these users and set them new" can you please be clear. Thanks.
Re: Error after Upgrade from 3.3 to 4
set the New Ticket Notification for each user in the admin interface to a new value.
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 76
- Joined: 01 Sep 2012, 09:51
- Znuny Version: 5.0.16
- Real Name: Vinesh Narayanan
- Company: NTS
Re: Error after Upgrade from 3.3 to 4
It is already set for all agents as shown in the screenshot....
You do not have the required permissions to view the files attached to this post.
Re: Error after Upgrade from 3.3 to 4
please set it to another value so the database is updated
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
-
- Znuny newbie
- Posts: 76
- Joined: 01 Sep 2012, 09:51
- Znuny Version: 5.0.16
- Real Name: Vinesh Narayanan
- Company: NTS
Re: Error after Upgrade from 3.3 to 4
My issue resolved after deleting all Process Management events and did DBUpdate-to-4.pl which was giving error if the Process Management events are available. Thanks.
Re: Error after Upgrade from 3.3 to 4
Hello,
the workarounds described don't work for me. I tested setting the value to "no" and back to "yes" again, but still the same problem. I also deleted the useraccount and created a new one, the problem is the same. The Process Management Tables are empty.
Does anyone have an idea what could additionally be checked?
the workarounds described don't work for me. I tested setting the value to "no" and back to "yes" again, but still the same problem. I also deleted the useraccount and created a new one, the problem is the same. The Process Management Tables are empty.
Does anyone have an idea what could additionally be checked?
Ticket-System
- VMware ESX 6.02 --> virtuelle Maschine
- CentOS 6.6
- OTRS 5 Patch12
- ITSM 5 Patch 12
- VMware ESX 6.02 --> virtuelle Maschine
- CentOS 6.6
- OTRS 5 Patch12
- ITSM 5 Patch 12