Re: Is there any explanation for Canceled filter processing due to error?
One additional information: user does not even receive any error or warning. On Oct 1, 3:25 am, LJ LongWing lj.longw...@gmail.com wrote: But there is WAY too little time between the select and the rollback to have requested user feedback and have received ittalking less than a tenth of a second. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W Sent: Thursday, September 30, 2010 6:01 PM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? The snippet tells the whole story... Select C6 ... The Last Modified Date has changed from when the record was pulled at the start of the transaction. A user should have received the This record has been updated by another user since you retrieved it. error (Error 1203) and the user chose not to save the record. Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ LongWing Sent: Thursday, September 30, 2010 9:16 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? With the snipit you provided, I cannot see it, but it's obvious that somewhere earlier in your process something caused the DB to issue a rollback...you just need to find the 'what' -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Thursday, September 30, 2010 2:04 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? Thanks for the feedback, I have had faced with a similar issue - a completely different one but identical to your example : - A script does a Push Fields to a form, but gets ARERR 382. - However, the Submit filters are executed after the operation as regular. - At the end of Phase, Canceled filter processing due to error appears. The .log file has the line /* UPDATE xxx SET ... /* /* ROLLBACK This totally seems to be okay, and supports your example. On the other hand, the current case has all queries seem to be executed successfully - ending with /* OK. So I cannot see why or which statement fails at all. BR, Koray On Sep 29, 5:57 pm, LJ LongWing lj.longw...@gmail.com wrote: Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled
Re: Is there any explanation for Canceled filter processing due to error?
The interaction is that the user gets an ERROR indicating that there was a conflict and then they get the choice. If they say to continue, the operation is performed again. If they cancel it is not performed again. So, the time is immediate -- error on the conflict (and a rollback) and then the user gets the option to continue and override the error by applying again or to cancel. Doug -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ LongWing Sent: Thursday, September 30, 2010 5:26 PM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? But there is WAY too little time between the select and the rollback to have requested user feedback and have received ittalking less than a tenth of a second. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W Sent: Thursday, September 30, 2010 6:01 PM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? The snippet tells the whole story... Select C6 ... The Last Modified Date has changed from when the record was pulled at the start of the transaction. A user should have received the This record has been updated by another user since you retrieved it. error (Error 1203) and the user chose not to save the record. Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ LongWing Sent: Thursday, September 30, 2010 9:16 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? With the snipit you provided, I cannot see it, but it's obvious that somewhere earlier in your process something caused the DB to issue a rollback...you just need to find the 'what' -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Thursday, September 30, 2010 2:04 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? Thanks for the feedback, I have had faced with a similar issue - a completely different one but identical to your example : - A script does a Push Fields to a form, but gets ARERR 382. - However, the Submit filters are executed after the operation as regular. - At the end of Phase, Canceled filter processing due to error appears. The .log file has the line /* UPDATE xxx SET ... /* /* ROLLBACK This totally seems to be okay, and supports your example. On the other hand, the current case has all queries seem to be executed successfully - ending with /* OK. So I cannot see why or which statement fails at all. BR, Koray On Sep 29, 5:57 pm, LJ LongWing lj.longw...@gmail.com wrote: Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY
Re: Is there any explanation for Canceled filter processing due to error?
Thanks for the feedback, I have had faced with a similar issue - a completely different one but identical to your example : - A script does a Push Fields to a form, but gets ARERR 382. - However, the Submit filters are executed after the operation as regular. - At the end of Phase, Canceled filter processing due to error appears. The .log file has the line /* UPDATE xxx SET ... /* /* ROLLBACK This totally seems to be okay, and supports your example. On the other hand, the current case has all queries seem to be executed successfully - ending with /* OK. So I cannot see why or which statement fails at all. BR, Koray On Sep 29, 5:57 pm, LJ LongWing lj.longw...@gmail.com wrote: Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details for it. The whole event restarts after a delay of 2- to-9 seconds, as seen in this example it was only 2. My question would be, In which circumstances this message would appear? Best Regards, Koray ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist:Where the Answers Are ___ _ ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Is there any explanation for Canceled filter processing due to error?
Hi, From a SQL standpoint, an update against a non-existing record would be wrong. Searching for something that does not exist is OK, but may stop the AR processing. The following select is probably done to retrieve value(s) needed in the Run-If-qualification of the filters in the SET-operation. SELECT C6 FROM T904 WHERE C1 = '1308884' In other words, the AR Server figures out that something is wrong before the actual SQL update is done. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. Thanks for the feedback, I have had faced with a similar issue - a completely different one but identical to your example : - A script does a Push Fields to a form, but gets ARERR 382. - However, the Submit filters are executed after the operation as regular. - At the end of Phase, Canceled filter processing due to error appears. The .log file has the line /* UPDATE xxx SET ... /* /* ROLLBACK This totally seems to be okay, and supports your example. On the other hand, the current case has all queries seem to be executed successfully - ending with /* OK. So I cannot see why or which statement fails at all. BR, Koray On Sep 29, 5:57 pm, LJ LongWing lj.longw...@gmail.com wrote: Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details for it. The whole event restarts after a delay of 2- to-9 seconds, as seen in this example it was only 2. My question would be, In which circumstances this message would appear? Best Regards, Koray ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist:Where the Answers Are ___ _ ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist
Re: Is there any explanation for Canceled filter processing due to error?
With the snipit you provided, I cannot see it, but it's obvious that somewhere earlier in your process something caused the DB to issue a rollback...you just need to find the 'what' -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Thursday, September 30, 2010 2:04 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? Thanks for the feedback, I have had faced with a similar issue - a completely different one but identical to your example : - A script does a Push Fields to a form, but gets ARERR 382. - However, the Submit filters are executed after the operation as regular. - At the end of Phase, Canceled filter processing due to error appears. The .log file has the line /* UPDATE xxx SET ... /* /* ROLLBACK This totally seems to be okay, and supports your example. On the other hand, the current case has all queries seem to be executed successfully - ending with /* OK. So I cannot see why or which statement fails at all. BR, Koray On Sep 29, 5:57 pm, LJ LongWing lj.longw...@gmail.com wrote: Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details for it. The whole event restarts after a delay of 2- to-9 seconds, as seen in this example it was only 2. My question would be, In which circumstances this message would appear? Best Regards, Koray ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist:Where the Answers Are ___ _ ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers
Re: Is there any explanation for Canceled filter processing due to error?
The snippet tells the whole story... Select C6 ... The Last Modified Date has changed from when the record was pulled at the start of the transaction. A user should have received the This record has been updated by another user since you retrieved it. error (Error 1203) and the user chose not to save the record. Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ LongWing Sent: Thursday, September 30, 2010 9:16 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? With the snipit you provided, I cannot see it, but it's obvious that somewhere earlier in your process something caused the DB to issue a rollback...you just need to find the 'what' -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Thursday, September 30, 2010 2:04 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? Thanks for the feedback, I have had faced with a similar issue - a completely different one but identical to your example : - A script does a Push Fields to a form, but gets ARERR 382. - However, the Submit filters are executed after the operation as regular. - At the end of Phase, Canceled filter processing due to error appears. The .log file has the line /* UPDATE xxx SET ... /* /* ROLLBACK This totally seems to be okay, and supports your example. On the other hand, the current case has all queries seem to be executed successfully - ending with /* OK. So I cannot see why or which statement fails at all. BR, Koray On Sep 29, 5:57 pm, LJ LongWing lj.longw...@gmail.com wrote: Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details for it. The whole event restarts after a delay of 2- to-9 seconds, as seen in this example it was only 2. My question would be, In which circumstances this message would appear? Best Regards, Koray ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Is there any explanation for Canceled filter processing due to error?
But there is WAY too little time between the select and the rollback to have requested user feedback and have received ittalking less than a tenth of a second. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W Sent: Thursday, September 30, 2010 6:01 PM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? The snippet tells the whole story... Select C6 ... The Last Modified Date has changed from when the record was pulled at the start of the transaction. A user should have received the This record has been updated by another user since you retrieved it. error (Error 1203) and the user chose not to save the record. Fred -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of LJ LongWing Sent: Thursday, September 30, 2010 9:16 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? With the snipit you provided, I cannot see it, but it's obvious that somewhere earlier in your process something caused the DB to issue a rollback...you just need to find the 'what' -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Thursday, September 30, 2010 2:04 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? Thanks for the feedback, I have had faced with a similar issue - a completely different one but identical to your example : - A script does a Push Fields to a form, but gets ARERR 382. - However, the Submit filters are executed after the operation as regular. - At the end of Phase, Canceled filter processing due to error appears. The .log file has the line /* UPDATE xxx SET ... /* /* ROLLBACK This totally seems to be okay, and supports your example. On the other hand, the current case has all queries seem to be executed successfully - ending with /* OK. So I cannot see why or which statement fails at all. BR, Koray On Sep 29, 5:57 pm, LJ LongWing lj.longw...@gmail.com wrote: Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arsl...@arslist.org Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details
Is there any explanation for Canceled filter processing due to error?
Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details for it. The whole event restarts after a delay of 2- to-9 seconds, as seen in this example it was only 2. My question would be, In which circumstances this message would appear? Best Regards, Koray ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Is there any explanation for Canceled filter processing due to error?
And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details for it. The whole event restarts after a delay of 2- to-9 seconds, as seen in this example it was only 2. My question would be, In which circumstances this message would appear? Best Regards, Koray ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Is there any explanation for Canceled filter processing due to error?
Koray, You have your answer right thereor more than likely, somewhere earlier upbut the result is right there. /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK I experience this type of scenario when I issue an out of phase delete of a record that I'm updating...here is my typical scenario I want to delete a recordthe easiest way to do a delete is to push to that record and set a 'delete' field to 'yes', and have a filter on that form do a record delete if that flag is yes Well...if that filter does an out of phase delete (phase 1), when phase 2 goes through and tries to update the last mod by and last mod date on the record, that record doesn't exist, and as such, the db throws an error and causes a rollback... I don't know what your scenario is, but something in your processing is causing the db to throw and error and rollback the transaction. -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of koray Sent: Wednesday, September 29, 2010 1:47 AM To: arslist@ARSLIST.ORG Subject: Re: Is there any explanation for Canceled filter processing due to error? And here is the SQL .log file corresponding to the same process : /* Tue Sep 28 2010 12:24:43.4296 */SELECT C6 FROM T904 WHERE C1 = '1308884' /* Tue Sep 28 2010 12:24:43.4317 */OK /* Tue Sep 28 2010 12:24:43.4319 */ROLLBACK WORK /* Tue Sep 28 2010 12:24:43.4697 */COMMIT WORK /* Tue Sep 28 2010 12:24:43.4705 */COMMIT WORK /* Tue Sep 28 2010 12:24:45.3386 */SELECT C1,C2,C3,C4,C5,C6,C7,C8,C112,... /* Tue Sep 28 2010 12:24:45.3738 */OK On Sep 29, 10:03 am, koray ko...@alkankoray.net wrote: Hello all, I have a weird issue that seems to be happening continously. Below is a portion from server-side filter .log file that took my attention: /* Tue Sep 28 2010 12:24:43.4127 */ End of filter processing (phase 1) -- Operation - SET on ZZZ - AD01589874 /* Tue Sep 28 2010 12:24:43.4130 */ Restart of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4159 */ Filter Level:0 Number Of Filters:404 Checking IMSA:MAIN:TASK:Task:Get WIP Task 0: Push Fields - IMSA:MAIN:Automated Pending:Task deferred from filter IMSA:MAIN:TASK:Task:Get WIP Task /* Tue Sep 28 2010 12:24:43.4189 */ End of filter processing (phase 2) -- Operation - SET on YYY - 1308884 /* Tue Sep 28 2010 12:24:43.4710 */Canceled filter processing due to error /* Tue Sep 28 2010 12:24:45.2824 */ Start filter processing (phase 1) -- Operation - SET on XXX - 1308884 The message Canceled filter processing due to error occurs but there are no details for it. The whole event restarts after a delay of 2- to-9 seconds, as seen in this example it was only 2. My question would be, In which circumstances this message would appear? Best Regards, Koray ___ UNSUBSCRIBE or access ARSlist Archives atwww.arslist.org attend wwrug10www.wwrug.comARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
