View ProjeQtOr On SourceForge.net
ProjeQtOr - Project Management Tool
Support us on Capterra
OIN - Open Invention Network
ProjeQtOr free project management software - [SOLVED] Error while saving details to workelement table for a Ticket workflow - ProjeQtOr
 
 

[SOLVED] Error while saving details to workelement table for a Ticket workflow

More
02 Aug 2016 14:15 #1 by sagar.toshniwal
V 5.4.2. I am getting an unusual error. The red-colored error pop-up does not have any text message! But the log file has captured error stack trace which I reproduce below.

Origin of error: I have customized a workflow for Tickets, along with certain actors at each stage. On one approval stage for this Ticket, I get this error.

Note: The only way I can move forward in my workflow is by deleting this particular row from the workelement database table. This obviously is not the solution. So please help!!

Log file contents:
2016-08-02 17:40:51.810 ***** ERROR ***** Exception-[23000] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Ticket-16' for key 'workelementReference'
2016-08-02 17:40:51.810 ***** ERROR *****    For query : insert into workelement ( refType , refId , idProject , refName , idUser , ongoing , done , idle ) values ('Ticket', '16', '12', 'Request #3 raised by Samish on 0208', '24', '0', '0', '0')
2016-08-02 17:40:51.810 ***** ERROR *****    Strack trace :
2016-08-02 17:40:51.810 ***** ERROR *****    #0 Sql->query called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:823]
2016-08-02 17:40:51.810 ***** ERROR *****    #1 SqlElement->insertSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:630]
2016-08-02 17:40:51.810 ***** ERROR *****    #2 SqlElement->saveSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:478]
2016-08-02 17:40:51.810 ***** ERROR *****    #3 SqlElement->save called at [C:\wamp\www\projeqtorV5.4.2\model\WorkElementMain.php:175]
2016-08-02 17:40:51.810 ***** ERROR *****    #4 WorkElementMain->save called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:1107]
2016-08-02 17:40:51.810 ***** ERROR *****    #5 SqlElement->saveDependantObjects called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:1065]
2016-08-02 17:40:51.826 ***** ERROR *****    #6 SqlElement->updateSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:624]
2016-08-02 17:40:51.826 ***** ERROR *****    #7 SqlElement->saveSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:478]
2016-08-02 17:40:51.826 ***** ERROR *****    #8 SqlElement->save called at [C:\wamp\www\projeqtorV5.4.2\model\custom\TicketMain.php:475]
2016-08-02 17:40:51.826 ***** ERROR *****    #9 TicketMain->save called at [C:\wamp\www\projeqtorV5.4.2\tool\saveObject.php:77]
2016-08-02 17:40:51.967 ***** ERROR ***** Exception-[23000] SQLSTATE[23000]: Integrity constraint violation: 1062 Duplicate entry 'Ticket-16' for key 'workelementReference'
2016-08-02 17:40:51.967 ***** ERROR *****    For query : insert into workelement ( refType , refId , idProject , refName , realCost , idUser , ongoing , done , idle ) values ('Ticket', '16', '12', 'Request #3 raised by Samish on 0208', '172042.22', '24', '0', '0', '0')
2016-08-02 17:40:51.967 ***** ERROR *****    Strack trace :
2016-08-02 17:40:51.967 ***** ERROR *****    #0 Sql->query called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:823]
2016-08-02 17:40:51.967 ***** ERROR *****    #1 SqlElement->insertSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:630]
2016-08-02 17:40:51.967 ***** ERROR *****    #2 SqlElement->saveSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:478]
2016-08-02 17:40:51.967 ***** ERROR *****    #3 SqlElement->save called at [C:\wamp\www\projeqtorV5.4.2\model\WorkElementMain.php:175]
2016-08-02 17:40:51.967 ***** ERROR *****    #4 WorkElementMain->save called at [C:\wamp\www\projeqtorV5.4.2\model\WorkElementMain.php:295]
2016-08-02 17:40:51.967 ***** ERROR *****    #5 WorkElementMain->save called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:1107]
2016-08-02 17:40:51.967 ***** ERROR *****    #6 SqlElement->saveDependantObjects called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:1065]
2016-08-02 17:40:51.967 ***** ERROR *****    #7 SqlElement->updateSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:624]
2016-08-02 17:40:51.967 ***** ERROR *****    #8 SqlElement->saveSqlElement called at [C:\wamp\www\projeqtorV5.4.2\model\persistence\SqlElement.php:478]
2016-08-02 17:40:51.967 ***** ERROR *****    #9 SqlElement->save called at [C:\wamp\www\projeqtorV5.4.2\model\custom\TicketMain.php:475]
2016-08-02 17:40:51.967 ***** ERROR *****    #10 TicketMain->save called at [C:\wamp\www\projeqtorV5.4.2\tool\saveObject.php:77]

I am an Eagle. On a mission to help those who want to help themselves...

Please Log in or Create an account to join the conversation.

More
02 Aug 2016 14:28 #2 by babynus
Can you check that is is produced for users who don't see work on tickets.
It it is the case, this issue is solved on V5.4.3.

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
11 Aug 2016 09:24 #3 by sagar.toshniwal
I have used 5.4.3 and I am still getting the same error. Tried to find out why, but no success. :unsure:
Please help!

I am an Eagle. On a mission to help those who want to help themselves...

Please Log in or Create an account to join the conversation.

More
11 Aug 2016 09:33 #4 by babynus
Czn you please give more hint.
For instance, about "approval stage" that leads to error : does the approval is done by user with specific access rights ?
Does this user see "work" data on the tickets ?
Does the "approval stage" lead to email sending ?

What you can do to help investigate : if approval profile is specific, try and change to use another one and tell us if it changes things. If so, give as amny information about profile as you can (access rights, specific access rights,...)
Also try and disable email sending and tell us if it changes things.

Regards.

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

More
11 Aug 2016 11:16 #5 by sagar.toshniwal

babynus wrote: Czn you please give more hint.
For instance, about "approval stage" that leads to error : does the approval is done by user with specific access rights ?
Does this user see "work" data on the tickets ?
Does the "approval stage" lead to email sending ?

What you can do to help investigate : if approval profile is specific, try and change to use another one and tell us if it changes things. If so, give as amny information about profile as you can (access rights, specific access rights,...)

I have created a few user id's with different access rights. In my workflow, specific users can take certain actions. An administrator can take all the actions. In this particular case of error, the ticket is created by Guest and the Administrator is trying to Cancel the ticket. That's the point when I get this error.

babynus wrote: Also try and disable email sending and tell us if it changes things.

I am not sure about this. I will try that and will let you know if it improves things in any way.

I am an Eagle. On a mission to help those who want to help themselves...

Please Log in or Create an account to join the conversation.

More
11 Aug 2016 11:50 #6 by babynus

the ticket is created by Guest and the Administrator is trying to Cancel the ticket

Does the admionistrator see "work" data on the tickets ?

Babynus
Administrator of ProjeQtOr web site

Please Log in or Create an account to join the conversation.

Moderators: babynusprotion
Time to create page: 0.033 seconds

Cookies settings

×

Functional Cookies

Ce site utilise des cookies pour assurer son bon fonctionnement et ne peuvent pas être désactivés de nos systèmes. Nous ne les utilisons pas à des fins publicitaires. Si ces cookies sont bloqués, certaines parties du site ne pourront pas fonctionner.

Session

Please login to see yours activities!

Other cookies

Ce site web utilise un certain nombre de cookies pour gérer, par exemple, les sessions utilisateurs.