Re: 7.6.4 Upgrade
Really? Thanks I have officially reported to BMC and am waiting for them to reply whether or not they can duplicate and bug it. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Saturday, April 09, 2011 5:17 PM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** Rafael, I saw a note just the other day about itunknown if it's officially been reported to BMC though. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Saturday, April 09, 2011 10:26 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** I believe I found the problem. I can duplicate this 100% of the time. If a notification filter has any data in the following fields it times out: 1) From: 2) Reply To: 3) Cc: 4) Bcc: NOTE: If Mailbox Name, Header Template, Content Template, or Footer Template are used the system works perfectly fine. It only hangs if any of the above 4 fields are used. We have many of our filters and escalations coded this way as it the way we allow users to be able to reply back to a request. [cid:image001.png@01CBF823.73527A40] Rafael This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"<>
Re: 7.6.4 Upgrade
Rafael, I saw a note just the other day about it..unknown if it's officially been reported to BMC though. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Saturday, April 09, 2011 10:26 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** I believe I found the problem. I can duplicate this 100% of the time. If a notification filter has any data in the following fields it times out: 1) From: 2) Reply To: 3) Cc: 4) Bcc: NOTE: If Mailbox Name, Header Template, Content Template, or Footer Template are used the system works perfectly fine. It only hangs if any of the above 4 fields are used. We have many of our filters and escalations coded this way as it the way we allow users to be able to reply back to a request. Rafael This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" <>
Re: 7.6.4 Upgrade
I believe I found the problem. I can duplicate this 100% of the time. If a notification filter has any data in the following fields it times out: 1) From: 2) Reply To: 3) Cc: 4) Bcc: NOTE: If Mailbox Name, Header Template, Content Template, or Footer Template are used the system works perfectly fine. It only hangs if any of the above 4 fields are used. We have many of our filters and escalations coded this way as it the way we allow users to be able to reply back to a request. [cid:image001.png@01CBF6B1.3E87E9D0] Rafael This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"<>
Re: 7.6.4 Upgrade
OK so here is the latest, It appears that any notification filter/escalation action is causing the server fast thread to die and restart itself causing timeouts. Has anyone experienced this in 7.6.4? Rafael This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
Thanks Joe, I already have narrowed this down to the Email Message form. When sending an outgoing message it times out. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Thursday, April 07, 2011 12:44 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** It just may be possible that when a notification is created, that process runs a search over some form that is timed out?? I would take a workflow log and a SQL log when reproducing the condition that leads to this time out which may give you a clue to what search operation times out. Joe From: Rodriguez, Rafael J x23718<mailto:rafael.rodrig...@broadridge.com> Sent: Wednesday, April 06, 2011 2:11 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: 7.6.4 Upgrade Thanks Joe, I have checked this already and we have enough space available. In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. So it appears that for some reason after the upgrade the system crashes when trying to send out notification. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Wednesday, April 06, 2011 12:44 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** First and foremost check your log files to see what may be going on.. Having said that here are a few tips to check certain things that could reduce your performance to the level its at.. Check the size of the transaction log file, and flush it. SQL server 2000 onwards does manage it automatically, with auto growth enabled, but maybe something is choking it? Make sure the disks where the log and data files of the AR System database reside have a healthy amount of free space.. Also check your disk space on the AR Server, sometimes log files if enabled and left enabled can grow large enough to fill up the disk, and this can choke the AR Server as it does require a significant of free disk space to run.. Hope this helps.. Cheers Joe From: LJ LongWing<mailto:lj.longw...@gmail.com> Sent: Tuesday, April 05, 2011 9:55 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: 7.6.4 Upgrade ** Rafael, I recommend turning on API/Filter/SQL logging on the server and analyzing the timings of each call with something like AR Workflow Analyzer…it’ll tell you what api/sql calls took the longest and you can analyze from there to find out why…..the message in general just means that the client asked for a process and the server took longer than 2 min’s to respond….that’s ALL it means…it’s up to you to figure out why it took so long. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Tuesday, April 05, 2011 7:14 AM To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade ** Hello list, I have recently upgraded to 7.6.4 from 7.5 Patch 7. Now when I try to submit I get the following timeout message: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully NOTE: The request does get created but I keep getting this. Has anyone experience this? ARS: 7.6.4 Server: Win 2008 DB: SQL 2008 Rafael _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Re: 7.6.4 Upgrade
I tried this as well and it did not come up for me. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Jason Miller Sent: Wednesday, April 06, 2011 5:20 PM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** I had to remove "KB" and only search by the numbers. On Apr 6, 2011 12:58 PM, "Rodriguez, Rafael J x23718" mailto:rafael.rodrig...@broadridge.com>> wrote: > Thanks Patrick but I can seem to pull up this KB. Do you happen to have the > details on this? > > Rafael > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of patrick > zandi > Sent: Wednesday, April 06, 2011 2:15 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > Subject: Re: 7.6.4 Upgrade > > ** Check with BMC on KB20035088_Fix > I think this is your issue... as of 7.5.03 there are 4 possible filters that > need to be modified.. They did not tell anyone, but if you call and press > hard enough or get the correct person, it might be the issue... Sounds just > like it.. > On Wed, Apr 6, 2011 at 2:10 PM, Rodriguez, Rafael J x23718 > mailto:rafael.rodrig...@broadridge.com><mailto:rafael.rodrig...@broadridge.com<mailto:rafael.rodrig...@broadridge.com>>> > wrote: > James thanks for your response. I do not have development cache mode enabled > on this server. > > In working with BMC it appears that the AR Server is terminating while trying > to do a filter notify action. > > Interesting if I disable filter that is trying to send notification the > timeout issue is resolved. I tried creating a brand new notify filter and > timeout is back. > > So it appears that for some reason after the upgrade the system crashes when > trying to send out notification. > > Rafael > > > From: Action Request System discussion list(ARSList) > [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG><mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>>] > On Behalf Of jham36 > Sent: Tuesday, April 05, 2011 3:26 PM > To: > arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG><mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>> > > Subject: Re: 7.6.4 Upgrade > > ** Make sure dev cache mode is turned off if this is your production > environment. > > James > _attend WWRUG11 www.wwrug.com<http://www.wwrug.com><http://www.wwrug.com> > ARSlist: "Where the Answers Are"_ > > This message and any attachments are intended only for the use of the > addressee and > > may contain information that is privileged and confidential. If the reader of > the > > message is not the intended recipient or an authorized representative of the > > intended recipient, you are hereby notified that any dissemination of this > > communication is strictly prohibited. If you have received this communication > in > > error, please notify us immediately by e-mail and delete the message and any > > attachments from your system. > > > > > > -- > Patrick Zandi > _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the > Answers Are"_ > > This message and any attachments are intended only for the use of the > addressee and > may contain information that is privileged and confidential. If the reader of > the > message is not the intended recipient or an authorized representative of the > intended recipient, you are hereby notified that any dissemination of this > communication is strictly prohibited. If you have received this communication > in > error, please notify us immediately by e-mail and delete the message and any > attachments from your system. > > > ___ > UNSUBSCRIBE or access ARSlist Archives at > www.arslist.org<http://www.arslist.org> > attend wwrug11 www.wwrug.com<http://www.wwrug.com> ARSList: "Where the > Answers Are" _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
It just may be possible that when a notification is created, that process runs a search over some form that is timed out?? I would take a workflow log and a SQL log when reproducing the condition that leads to this time out which may give you a clue to what search operation times out. Joe From: Rodriguez, Rafael J x23718 Sent: Wednesday, April 06, 2011 2:11 PM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade Thanks Joe, I have checked this already and we have enough space available. In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. So it appears that for some reason after the upgrade the system crashes when trying to send out notification. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Wednesday, April 06, 2011 12:44 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** First and foremost check your log files to see what may be going on.. Having said that here are a few tips to check certain things that could reduce your performance to the level its at.. Check the size of the transaction log file, and flush it. SQL server 2000 onwards does manage it automatically, with auto growth enabled, but maybe something is choking it? Make sure the disks where the log and data files of the AR System database reside have a healthy amount of free space.. Also check your disk space on the AR Server, sometimes log files if enabled and left enabled can grow large enough to fill up the disk, and this can choke the AR Server as it does require a significant of free disk space to run.. Hope this helps.. Cheers Joe From: LJ LongWing Sent: Tuesday, April 05, 2011 9:55 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** Rafael, I recommend turning on API/Filter/SQL logging on the server and analyzing the timings of each call with something like AR Workflow Analyzer…it’ll tell you what api/sql calls took the longest and you can analyze from there to find out why…..the message in general just means that the client asked for a process and the server took longer than 2 min’s to respond….that’s ALL it means…it’s up to you to figure out why it took so long. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Tuesday, April 05, 2011 7:14 AM To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade ** Hello list, I have recently upgraded to 7.6.4 from 7.5 Patch 7. Now when I try to submit I get the following timeout message: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully NOTE: The request does get created but I keep getting this. Has anyone experience this? ARS: 7.6.4 Server: Win 2008 DB: SQL 2008 Rafael ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
I had to remove "KB" and only search by the numbers. On Apr 6, 2011 12:58 PM, "Rodriguez, Rafael J x23718" < rafael.rodrig...@broadridge.com> wrote: > Thanks Patrick but I can seem to pull up this KB. Do you happen to have the details on this? > > Rafael > > From: Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG] On Behalf Of patrick zandi > Sent: Wednesday, April 06, 2011 2:15 PM > To: arslist@ARSLIST.ORG > Subject: Re: 7.6.4 Upgrade > > ** Check with BMC on KB20035088_Fix > I think this is your issue... as of 7.5.03 there are 4 possible filters that need to be modified.. They did not tell anyone, but if you call and press hard enough or get the correct person, it might be the issue... Sounds just like it.. > On Wed, Apr 6, 2011 at 2:10 PM, Rodriguez, Rafael J x23718 < rafael.rodrig...@broadridge.com<mailto:rafael.rodrig...@broadridge.com>> wrote: > James thanks for your response. I do not have development cache mode enabled on this server. > > In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. > > Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. > > So it appears that for some reason after the upgrade the system crashes when trying to send out notification. > > Rafael > > > From: Action Request System discussion list(ARSList) [mailto: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of jham36 > Sent: Tuesday, April 05, 2011 3:26 PM > To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> > > Subject: Re: 7.6.4 Upgrade > > ** Make sure dev cache mode is turned off if this is your production environment. > > James > _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ > > This message and any attachments are intended only for the use of the addressee and > > may contain information that is privileged and confidential. If the reader of the > > message is not the intended recipient or an authorized representative of the > > intended recipient, you are hereby notified that any dissemination of this > > communication is strictly prohibited. If you have received this communication in > > error, please notify us immediately by e-mail and delete the message and any > > attachments from your system. > > > > > > -- > Patrick Zandi > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > This message and any attachments are intended only for the use of the addressee and > may contain information that is privileged and confidential. If the reader of the > message is not the intended recipient or an authorized representative of the > intended recipient, you are hereby notified that any dissemination of this > communication is strictly prohibited. If you have received this communication in > error, please notify us immediately by e-mail and delete the message and any > attachments from your system. > > > ___ > UNSUBSCRIBE or access ARSlist Archives at www.arslist.org > attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
BMC provided it to us.. so it must be inside... On Wed, Apr 6, 2011 at 3:57 PM, Rodriguez, Rafael J x23718 < rafael.rodrig...@broadridge.com> wrote: > ** > > Thanks Patrick but I can seem to pull up this KB. Do you happen to have the > details on this? > > > > Rafael > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *patrick zandi > *Sent:* Wednesday, April 06, 2011 2:15 PM > > *To:* arslist@ARSLIST.ORG > *Subject:* Re: 7.6.4 Upgrade > > > > ** Check with BMC on KB20035088_Fix > > I think this is your issue... as of 7.5.03 there are 4 possible filters > that need to be modified.. They did not tell anyone, but if you call and > press hard enough or get the correct person, it might be the issue... Sounds > just like it.. > > On Wed, Apr 6, 2011 at 2:10 PM, Rodriguez, Rafael J x23718 < > rafael.rodrig...@broadridge.com> wrote: > > James thanks for your response. I do not have development cache mode > enabled on this server. > > > > In working with BMC it appears that the AR Server is terminating while > trying to do a filter notify action. > > > > Interesting if I disable filter that is trying to send notification the > timeout issue is resolved. I tried creating a brand new notify filter and > timeout is back. > > > > So it appears that for some reason after the upgrade the system crashes > when trying to send out notification. > > > > Rafael > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *jham36 > *Sent:* Tuesday, April 05, 2011 3:26 PM > *To:* arslist@ARSLIST.ORG > > > *Subject:* Re: 7.6.4 Upgrade > > > > ** Make sure dev cache mode is turned off if this is your production > environment. > > > > James > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > This message and any attachments are intended only for the use of the > addressee and > > may contain information that is privileged and confidential. If the reader of > the > > message is not the intended recipient or an authorized representative of the > > intended recipient, you are hereby notified that any dissemination of this > > communication is strictly prohibited. If you have received this communication > in > > error, please notify us immediately by e-mail and delete the message and any > > attachments from your system. > > > > > > > -- > Patrick Zandi > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > This message and any attachments are intended only for the use of the > addressee and > may contain information that is privileged and confidential. If the reader of > the > message is not the intended recipient or an authorized representative of the > intended recipient, you are hereby notified that any dissemination of this > communication is strictly prohibited. If you have received this communication > in > error, please notify us immediately by e-mail and delete the message and any > attachments from your system. > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > -- Patrick Zandi ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
Thanks Patrick but I can seem to pull up this KB. Do you happen to have the details on this? Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of patrick zandi Sent: Wednesday, April 06, 2011 2:15 PM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** Check with BMC on KB20035088_Fix I think this is your issue... as of 7.5.03 there are 4 possible filters that need to be modified.. They did not tell anyone, but if you call and press hard enough or get the correct person, it might be the issue... Sounds just like it.. On Wed, Apr 6, 2011 at 2:10 PM, Rodriguez, Rafael J x23718 mailto:rafael.rodrig...@broadridge.com>> wrote: James thanks for your response. I do not have development cache mode enabled on this server. In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. So it appears that for some reason after the upgrade the system crashes when trying to send out notification. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of jham36 Sent: Tuesday, April 05, 2011 3:26 PM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: 7.6.4 Upgrade ** Make sure dev cache mode is turned off if this is your production environment. James _attend WWRUG11 www.wwrug.com<http://www.wwrug.com> ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. -- Patrick Zandi _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
Check with BMC on KB20035088_Fix I think this is your issue... as of 7.5.03 there are 4 possible filters that need to be modified.. They did not tell anyone, but if you call and press hard enough or get the correct person, it might be the issue... Sounds just like it.. On Wed, Apr 6, 2011 at 2:10 PM, Rodriguez, Rafael J x23718 < rafael.rodrig...@broadridge.com> wrote: > James thanks for your response. I do not have development cache mode > enabled on this server. > > > > In working with BMC it appears that the AR Server is terminating while > trying to do a filter notify action. > > > > Interesting if I disable filter that is trying to send notification the > timeout issue is resolved. I tried creating a brand new notify filter and > timeout is back. > > > > So it appears that for some reason after the upgrade the system crashes > when trying to send out notification. > > > > Rafael > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *jham36 > *Sent:* Tuesday, April 05, 2011 3:26 PM > *To:* arslist@ARSLIST.ORG > > *Subject:* Re: 7.6.4 Upgrade > > > > ** Make sure dev cache mode is turned off if this is your production > environment. > > > > James > > _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ > > This message and any attachments are intended only for the use of the > addressee and > may contain information that is privileged and confidential. If the reader of > the > message is not the intended recipient or an authorized representative of the > intended recipient, you are hereby notified that any dissemination of this > communication is strictly prohibited. If you have received this communication > in > error, please notify us immediately by e-mail and delete the message and any > attachments from your system. > > > -- Patrick Zandi ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
Thanks Joe, I have checked this already and we have enough space available. In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. So it appears that for some reason after the upgrade the system crashes when trying to send out notification. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Wednesday, April 06, 2011 12:44 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** First and foremost check your log files to see what may be going on.. Having said that here are a few tips to check certain things that could reduce your performance to the level its at.. Check the size of the transaction log file, and flush it. SQL server 2000 onwards does manage it automatically, with auto growth enabled, but maybe something is choking it? Make sure the disks where the log and data files of the AR System database reside have a healthy amount of free space.. Also check your disk space on the AR Server, sometimes log files if enabled and left enabled can grow large enough to fill up the disk, and this can choke the AR Server as it does require a significant of free disk space to run.. Hope this helps.. Cheers Joe From: LJ LongWing<mailto:lj.longw...@gmail.com> Sent: Tuesday, April 05, 2011 9:55 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: 7.6.4 Upgrade ** Rafael, I recommend turning on API/Filter/SQL logging on the server and analyzing the timings of each call with something like AR Workflow Analyzer…it’ll tell you what api/sql calls took the longest and you can analyze from there to find out why…..the message in general just means that the client asked for a process and the server took longer than 2 min’s to respond….that’s ALL it means…it’s up to you to figure out why it took so long. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Tuesday, April 05, 2011 7:14 AM To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade ** Hello list, I have recently upgraded to 7.6.4 from 7.5 Patch 7. Now when I try to submit I get the following timeout message: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully NOTE: The request does get created but I keep getting this. Has anyone experience this? ARS: 7.6.4 Server: Win 2008 DB: SQL 2008 Rafael _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Re: 7.6.4 Upgrade
James thanks for your response. I do not have development cache mode enabled on this server. In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. So it appears that for some reason after the upgrade the system crashes when trying to send out notification. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of jham36 Sent: Tuesday, April 05, 2011 3:26 PM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** Make sure dev cache mode is turned off if this is your production environment. James _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
Re: 7.6.4 Upgrade
Thanks LJ for your quick response. I have done this and from the analysis it still not really clear what is going on. In working with BMC it appears that the AR Server is terminating while trying to do a filter notify action. Interesting if I disable filter that is trying to send notification the timeout issue is resolved. I tried creating a brand new notify filter and timeout is back. So it appears that for some reason after the upgrade the system crashes when trying to send out notification. Rafael From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Tuesday, April 05, 2011 9:56 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** Rafael, I recommend turning on API/Filter/SQL logging on the server and analyzing the timings of each call with something like AR Workflow Analyzer...it'll tell you what api/sql calls took the longest and you can analyze from there to find out why.the message in general just means that the client asked for a process and the server took longer than 2 min's to respondthat's ALL it means...it's up to you to figure out why it took so long. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Tuesday, April 05, 2011 7:14 AM To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade ** Hello list, I have recently upgraded to 7.6.4 from 7.5 Patch 7. Now when I try to submit I get the following timeout message: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully NOTE: The request does get created but I keep getting this. Has anyone experience this? ARS: 7.6.4 Server: Win 2008 DB: SQL 2008 Rafael This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
To the best of my knowledge, all that the installer does when you choose that check box, for Unicode, is set the flag in the ar.conf (ar.cfg in case of windows) file that the character set is UTF-8. This tells the arserverd process that the database it is trying to connect to is a Unicode database so it starts up correctly. It does not do a conversion.. The issue you are facing is probably that this flag has been set, the AR Server tries to start up during the install, and cannot start because it expects a Unicode underlying database and its not.. Joe -Original Message- From: Daniel Condrea Sent: Wednesday, April 06, 2011 7:02 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade Hi Joe, Thank you for your answer. There is no need to convert anything at the database level. Migration from ARS 6.3 to 7.1 allows choosing UNICODE versus nonUNICODE upgrade even if the underlying database is UNICODE. No we are in a position where we have to migrate from 7.1 to 7.6.04. The installer detects that the underlying database is UNICODE and the actual migration process is trying to upgrade a nonUNICODE ARS on an UNICODE database and it stops the upgrade process. So far I am sure that: - We have to install a fresh copy for ARS server - There are some character functions that has to be changed Is there anything else that has to be taken care of? Daniel -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Wednesday, April 06, 2011 8:13 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade If you want to upgrade from a non-UNICODE ARS database to a UNICODE database, your DBA has got a few nails to bang before you can begin. You need to do a table structure and data conversion to alter the database from the current state to convert it to a UNICODE database.. Before you attempt this, it would be safe to have a backup of your database in its current state, so you have a recovery point.. Joe -Original Message- From: Daniel Condrea Sent: Wednesday, April 06, 2011 1:01 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade Hello All, We use ARS in custom mode and, so far, there is no need for UNICODE. The migration from 6.3 to 7.1 let us upgrade ARS server on UNICODE Oracle 10g. Consequently we have a ARS server that is nonUNICODE an Oracle that is UNICODE. Now we have to migrate ARS server from version 7.1 to 7.6.04. The installer does not let us upgrade to version 7.6.04 because the Oracle is UNICODE. Do you have a document that details the steps that have to be taken to upgrade a nonUNICODE ARS server from 7.1 to an UNICODE ARS server of version 7.6.04? Thank you, Daniel IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message
Re: 7.6.4 Upgrade
Hi Joe, Thank you for your answer. There is no need to convert anything at the database level. Migration from ARS 6.3 to 7.1 allows choosing UNICODE versus nonUNICODE upgrade even if the underlying database is UNICODE. No we are in a position where we have to migrate from 7.1 to 7.6.04. The installer detects that the underlying database is UNICODE and the actual migration process is trying to upgrade a nonUNICODE ARS on an UNICODE database and it stops the upgrade process. So far I am sure that: - We have to install a fresh copy for ARS server - There are some character functions that has to be changed Is there anything else that has to be taken care of? Daniel -Original Message- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Joe Martin D'Souza Sent: Wednesday, April 06, 2011 8:13 AM To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade If you want to upgrade from a non-UNICODE ARS database to a UNICODE database, your DBA has got a few nails to bang before you can begin. You need to do a table structure and data conversion to alter the database from the current state to convert it to a UNICODE database.. Before you attempt this, it would be safe to have a backup of your database in its current state, so you have a recovery point.. Joe -Original Message- From: Daniel Condrea Sent: Wednesday, April 06, 2011 1:01 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade Hello All, We use ARS in custom mode and, so far, there is no need for UNICODE. The migration from 6.3 to 7.1 let us upgrade ARS server on UNICODE Oracle 10g. Consequently we have a ARS server that is nonUNICODE an Oracle that is UNICODE. Now we have to migrate ARS server from version 7.1 to 7.6.04. The installer does not let us upgrade to version 7.6.04 because the Oracle is UNICODE. Do you have a document that details the steps that have to be taken to upgrade a nonUNICODE ARS server from 7.1 to an UNICODE ARS server of version 7.6.04? Thank you, Daniel IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error,
Re: 7.6.4 Upgrade
If you want to upgrade from a non-UNICODE ARS database to a UNICODE database, your DBA has got a few nails to bang before you can begin. You need to do a table structure and data conversion to alter the database from the current state to convert it to a UNICODE database.. Before you attempt this, it would be safe to have a backup of your database in its current state, so you have a recovery point.. Joe -Original Message- From: Daniel Condrea Sent: Wednesday, April 06, 2011 1:01 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade Hello All, We use ARS in custom mode and, so far, there is no need for UNICODE. The migration from 6.3 to 7.1 let us upgrade ARS server on UNICODE Oracle 10g. Consequently we have a ARS server that is nonUNICODE an Oracle that is UNICODE. Now we have to migrate ARS server from version 7.1 to 7.6.04. The installer does not let us upgrade to version 7.6.04 because the Oracle is UNICODE. Do you have a document that details the steps that have to be taken to upgrade a nonUNICODE ARS server from 7.1 to an UNICODE ARS server of version 7.6.04? Thank you, Daniel IMPORTANT.Les informations contenues dans ce message electronique y compris les fichiers attaches sont strictement confidentielles et peuvent etre protegees par la loi. Ce message electronique est destine exclusivement au(x) destinataire(s) mentionne(s) ci-dessus. Si vous avez recu ce message par erreur ou s il ne vous est pas destine, veuillez immediatement le signaler a l expediteur et effacer ce message et tous les fichiers eventuellement attaches. Toute lecture, exploitation ou transmission des informations contenues dans ce message est interdite. Tout message electronique est susceptible d alteration. A ce titre, le Groupe France Telecom decline toute responsabilite notamment s il a ete altere, deforme ou falsifie. De meme, il appartient au destinataire de s assurer de l absence de tout virus. IMPORTANT.This e-mail message and any attachments are strictly confidential and may be protected by law. This message is intended only for the named recipient(s) above. If you have received this message in error, or are not the named recipient(s), please immediately notify the sender and delete this e-mail message. Any unauthorized view, usage or disclosure ofthis message is prohibited. Since e-mail messages may not be reliable, France Telecom Group shall not be liable for any message if modified, changed or falsified. Additionally the recipient should ensure they are actually virus free. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
First and foremost check your log files to see what may be going on.. Having said that here are a few tips to check certain things that could reduce your performance to the level its at.. Check the size of the transaction log file, and flush it. SQL server 2000 onwards does manage it automatically, with auto growth enabled, but maybe something is choking it? Make sure the disks where the log and data files of the AR System database reside have a healthy amount of free space.. Also check your disk space on the AR Server, sometimes log files if enabled and left enabled can grow large enough to fill up the disk, and this can choke the AR Server as it does require a significant of free disk space to run.. Hope this helps.. Cheers Joe From: LJ LongWing Sent: Tuesday, April 05, 2011 9:55 AM Newsgroups: public.remedy.arsystem.general To: arslist@ARSLIST.ORG Subject: Re: 7.6.4 Upgrade ** Rafael, I recommend turning on API/Filter/SQL logging on the server and analyzing the timings of each call with something like AR Workflow Analyzer…it’ll tell you what api/sql calls took the longest and you can analyze from there to find out why…..the message in general just means that the client asked for a process and the server took longer than 2 min’s to respond….that’s ALL it means…it’s up to you to figure out why it took so long. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Tuesday, April 05, 2011 7:14 AM To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade ** Hello list, I have recently upgraded to 7.6.4 from 7.5 Patch 7. Now when I try to submit I get the following timeout message: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully NOTE: The request does get created but I keep getting this. Has anyone experience this? ARS: 7.6.4 Server: Win 2008 DB: SQL 2008 Rafael ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
Make sure dev cache mode is turned off if this is your production environment. James ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
Re: 7.6.4 Upgrade
Rafael, I recommend turning on API/Filter/SQL logging on the server and analyzing the timings of each call with something like AR Workflow Analyzer.it'll tell you what api/sql calls took the longest and you can analyze from there to find out why...the message in general just means that the client asked for a process and the server took longer than 2 min's to respond..that's ALL it means.it's up to you to figure out why it took so long. From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Rodriguez, Rafael J x23718 Sent: Tuesday, April 05, 2011 7:14 AM To: arslist@ARSLIST.ORG Subject: 7.6.4 Upgrade ** Hello list, I have recently upgraded to 7.6.4 from 7.5 Patch 7. Now when I try to submit I get the following timeout message: ARERR [92] Timeout during database update -- the operation has been accepted by the server and will usually complete successfully NOTE: The request does get created but I keep getting this. Has anyone experience this? ARS: 7.6.4 Server: Win 2008 DB: SQL 2008 Rafael This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. _attend WWRUG11 www.wwrug.com ARSlist: "Where the Answers Are"_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
