RE: [Axapta-Knowledge-Village] Re: Axapta gets hanged !!!
I think this SysUtilElementsLog was related to the hotfix I saw and the fix about switching to temp table was mentioned (disclaimer: this is all from my memory banks which are getting older and more prone to errors!) I would give what Navid says a try since it is easy to make the change (although not sure you have catch 22 that when you try to change system already hang ;) ) Sorry I cannot look for the hotfix now as its 10pm and I am trying to clear 101 things before I then pack my bag to go travel overseas to a customer site tmr From: Axapta-Knowledge-Village@yahoogroups.com [mailto:axapta-knowledge-vill...@yahoogroups.com] On Behalf Of Navid Sent: 21 January 2010 21:19 To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] Re: Axapta gets hanged !!! Hi Anitha, We also had a similar issue when we migrated to Dynamics AX 2009. Our problem was caused by Dynamics logging every item(Form/Report/Table) that is being used by any user. The table SysUtilElementsLog was having locks So we made the table SysUtilElementsLog as temporary and this solved the problem. Please have a look at the SQL Acticity and if this is the case try making the table as temporary. This will stop logging the usage in database and any existing data will also be wiped out. Please try this in your test system before doing it in Production. Hope this will help Navid --- In Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com , Anitha S mail2eani...@... wrote: Yes James.. System gets hanged when the user access the forms also : like posting an invoice, payment etc., I could see only this message in event log : Terminating the session . When the system goes to Not Responding mode, we forcibly close the application. Regards, Anitha On Thu, Jan 21, 2010 at 5:05 PM, James Flavell djf1...@... wrote: Still not clear the issue happens only when you are doing things in the AOT or also when nothing at all is done in the AOT (regardless of the instance)? Example: 2 users login and begin to do their daily work of oopen customer forma nd sales order etc. Does the system slow down? Is there anything in the event logs of the OS at all? *From:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com [mailto: Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com ] *On Behalf Of *Anitha S *Sent:* 21 January 2010 19:31 *To:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com *Subject:* Re: [Axapta-Knowledge-Village] Axapta gets hanged !!! James, We are using 2 Instances. One is Test and Production. Amount of Data in test Instance is same like in Prod.(might be around * less15*% of data than prod). Test instance is used by limited number of users. But after we started using Production instance , we see the Test instance has also slowed down.Be it compilation or posting an invoice ., nothing works.System goes to Not Responding mode. Coming to your question: I had a doubt that our customization could be a reason for hanging problem. To confirm that, I compiled few objets in AOT. Now I m clear that customization is no way related to this issue. Whatever operation we do in Ax, it goes hanging mode. As Mahmoud said, it might be because of SQL Server dynamic memory management problem since both test and production instances are using same the SQL server machine with different DBs and our OS is also x64.We are working on that. Meanwhile any other ideas or suggestion will be appreciated. Regards, Anitha. On Thu, Jan 21, 2010 at 4:11 PM, James Flavell djf1...@... wrote: Sorry just to clarify You mean when you compile a single AOT object then every goes slow (even if say there are only 2 users on the system)? Are there other situations where the it goes slow not related to doing anything in the AOT? The hotfix I vaguely remember seeing was slowness caused when lots of ax user were logging in so nothing related to specific AOT or compile (I believe it was pre RU3 so it is most likely included in this) Thanks James *From:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com [mailto: Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com ] *On Behalf Of *Anitha S *Sent:* 21 January 2010 17:59 *To:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com *Subject:* Re: [Axapta-Knowledge-Village] Axapta gets hanged !!! Hi James, Here are the details. *Kernel Version* : 5.0.1000.52 *Application Version* : 5.0.1001.96 We are using *SQL server 2005 SP2*. AOS and SQL server are in *different*
RE: [Axapta-Knowledge-Village] Re: Axapta gets hanged !!!
Just to update that what Navid talked about is KB 959598 and this is the one I was also referring to. Are you a partner? If so go get the article: https://mbs.microsoft.com/knowledgebase/kbdisplay.aspx?wtntzsmnwukntmmyxupyz qpouxnxspsymmtyvwnzmxqlwyxs If you are a customer go ask your partner to look it up and talk to you (sorry its confidential and so I cannot just give it to you or I may get in trouble with MS). Basically the solution is as per Navid said to change to temp table (AOT object usage is not logged any more - this usage data in theory is useful in an upgrade to help you know objects that have a conflict whether they are ever used by users - that's at least how I understand what it is used for) or apply a hotfix MS issued (is included in RU2) Let us know how things turn out Thanks James From: Axapta-Knowledge-Village@yahoogroups.com [mailto:axapta-knowledge-vill...@yahoogroups.com] On Behalf Of Navid Sent: 21 January 2010 21:19 To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] Re: Axapta gets hanged !!! Hi Anitha, We also had a similar issue when we migrated to Dynamics AX 2009. Our problem was caused by Dynamics logging every item(Form/Report/Table) that is being used by any user. The table SysUtilElementsLog was having locks So we made the table SysUtilElementsLog as temporary and this solved the problem. Please have a look at the SQL Acticity and if this is the case try making the table as temporary. This will stop logging the usage in database and any existing data will also be wiped out. Please try this in your test system before doing it in Production. Hope this will help Navid --- In Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com , Anitha S mail2eani...@... wrote: Yes James.. System gets hanged when the user access the forms also : like posting an invoice, payment etc., I could see only this message in event log : Terminating the session . When the system goes to Not Responding mode, we forcibly close the application. Regards, Anitha On Thu, Jan 21, 2010 at 5:05 PM, James Flavell djf1...@... wrote: Still not clear the issue happens only when you are doing things in the AOT or also when nothing at all is done in the AOT (regardless of the instance)? Example: 2 users login and begin to do their daily work of oopen customer forma nd sales order etc. Does the system slow down? Is there anything in the event logs of the OS at all? *From:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com [mailto: Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com ] *On Behalf Of *Anitha S *Sent:* 21 January 2010 19:31 *To:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com *Subject:* Re: [Axapta-Knowledge-Village] Axapta gets hanged !!! James, We are using 2 Instances. One is Test and Production. Amount of Data in test Instance is same like in Prod.(might be around * less15*% of data than prod). Test instance is used by limited number of users. But after we started using Production instance , we see the Test instance has also slowed down.Be it compilation or posting an invoice ., nothing works.System goes to Not Responding mode. Coming to your question: I had a doubt that our customization could be a reason for hanging problem. To confirm that, I compiled few objets in AOT. Now I m clear that customization is no way related to this issue. Whatever operation we do in Ax, it goes hanging mode. As Mahmoud said, it might be because of SQL Server dynamic memory management problem since both test and production instances are using same the SQL server machine with different DBs and our OS is also x64.We are working on that. Meanwhile any other ideas or suggestion will be appreciated. Regards, Anitha. On Thu, Jan 21, 2010 at 4:11 PM, James Flavell djf1...@... wrote: Sorry just to clarify You mean when you compile a single AOT object then every goes slow (even if say there are only 2 users on the system)? Are there other situations where the it goes slow not related to doing anything in the AOT? The hotfix I vaguely remember seeing was slowness caused when lots of ax user were logging in so nothing related to specific AOT or compile (I believe it was pre RU3 so it is most likely included in this) Thanks James *From:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com [mailto: Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com ] *On Behalf Of *Anitha S *Sent:* 21 January 2010 17:59 *To:* Axapta-Knowledge-Village@yahoogroups.com mailto:Axapta-Knowledge-Village%40yahoogroups.com
