AW: [development-axapta] AX4.0 how to know batch process is running
Hi James, We are solving that problem for a customer at the moment. You could check if the batch user is logged on to the SQL server, only that will not give you the answer you are looking for. The user can be logged on, and the batch process has crashed, or the user is not logged on, but the batch process is running - but Idle. We decided to introduce a heartbeat to the batch process. After execution on the batch process we write a XML file with an execution log. The heartbeat is monitored a BizTalk server starting a workflow if the batch process has not been executed the last 10 minutes. Mit freundlichen Grüßen / Best regards / Med venlig hilsen Jesper Jørgensen / Abt. NMT-XD Senior Product Manager arvato systems | Technologies GmbH An der Autobahn 18 33311 Gütersloh jesper.joergen...@bertelsmann.deblocked::blocked::blocked::mailto:jesper.joergen...@bertelsmann.de Phone: +49 5242 / 40 80 54 Fax: +49 5242 / 40 80 40 Mobile: +49 172 / 571 03 34 http://www.as-T.deblocked::blocked::http://www.as-t.biz/ arvato systems | Technologies GmbH Joachim-Jungius-Str. 9, 18059 Rostock Geschäftsführung: Erwin Pietz, Matthias Moeller Amtsgericht Rostock - HRB 7497 Der Inhalt dieser Nachricht oder eventueller Anlagen ist vertraulich und ausschließlich für den bezeichneten Adressaten bestimmt. Bitte stellen Sie sicher, dass die Information in dieser Nachricht ausschließlich an die adressierten Personen gelangt. Sollte diese Nachricht versehentlich an Sie gesendet worden sein, dann informieren Sie bitte umgehend den Absender und löschen Sie die Nachricht. Vielen Dank. The information in this e-mail and any attachments is confidential. The information must only be held in areas that have controlled and limited access to the addressed persons. If this e-mail has been sent to you in error, please immediately notify the sender and delete the e-mail. Thanks. Von: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] Im Auftrag von James Flavell Gesendet: Donnerstag, 13. Mai 2010 10:24 An: development-axapta@yahoogroups.com Betreff: [development-axapta] AX4.0 how to know batch process is running Hi everyone, I am not sure if this has been asked in the group before but if yes please help direct me to the posting I want to setup some way to alert me if the batch process (or batch user login) has failed or not been started in AX4.0. Basically I have several companies and about 5 batch groups in each so that is 10 batch processes that need to be running. I just want a simple way to get an email notification if the batch process is not running Usually the problem is the batch user session is terminated for various reason such as hardware problem So I was thinking is there some SQL script I can make to check the batch user is logged in or somehow from outside AX query what batch groups or processes are currently running in AX? Thanks in advance for your help James [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
RE: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas?
Thanks Mike J I don't believe we have any 3rd party apps that connect via business connector so it must be one of the normal clients L The only external party I can think of is the SQL OLAP being accessed via the AX client Pivot View analysis (or the pushing of data to the SQL OLAP during the cube processing) but I don't think this use business connector right? For stopping and starting since this is AX4.0 do you have any suggestions for getting the batch client running again? I believe I have to do something about the startup class or the like and then have a batch file that starts a client with some startup parameter or something right? Thanks again for your great help, much appreciated J James From: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] On Behalf Of Mike Sent: 28 May 2010 20:52 To: development-axapta@yahoogroups.com Subject: Re: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas? I would focus on whatever 3rd party apps you have on that AOS that connect via the business connector. That's going to be the source of an RPC error on the AOS. Yes, the AOS service crashes when it runs out of memory and it runs slow as it approaches the upper limits. You should restart the aos service periodically to prevent this from happening. pick a time of day when it affects the least amount of people. you could even create 2 .bat files with 'net stop AOS$03' and 'net start AOS$03' and schedule them to run 2 minutes apart at a time when no one is on the system. From: James Flavell Sent: Tuesday, May 25, 2010 8:18 AM To: development-axapta@yahoogroups.com mailto:development-axapta%40yahoogroups.com Subject: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas? Hi everyone We have an AX4.0 SP2 with kernel 4.0.2503.953 Today the user reported very slow performance and the AOS crashed later on When we looked in the event viewer there was an error: Object Server 01: RPC error: RPC exception 14 occurred in session 3 This was logged maybe 50 to 100 times in a single second every second!!! I searched but could find no mention of RCP 14 error anywhere (including partner source) Does anyone have any idea what can cause this error or similar kind of mass logging in the event viewer every second? Also I heard the Ax4.0 AOS is likely to crash when the Ax32Serv.exe process reaches around the 2GB limit. Has anyone heard about this? Thanks James [Non-text portions of this message have been removed] [Non-text portions of this message have been removed] [Non-text portions of this message have been removed]
RE: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas?
Hi James The AX AOS will crash as it approaches 2GB of memory use and its likely that performance would degrade as it nears this upper limit. It could be that you have uncovered a memory leak in AX which might account for this but it could also be that you just have too many users that run memory hungry processes at the same time and simply need another AOS to spread the load. You could use performance monitor to track memory use over time to see if you can get a better handle on whther it is a leak or you could simply grab a new kernel (there are some memory leak fixes in newer kernels as I've been dealing with a leak problem for one of my clients over the last couple of months and the signs are good that the latest kernel has resolved the problem for them. Regards Malcolm Burtt Product Development Manager Touchstone Ltd From: development-axapta@yahoogroups.com [development-axa...@yahoogroups.com] On Behalf Of James Flavell [djf1...@gmail.com] Sent: 25 May 2010 13:18 To: development-axapta@yahoogroups.com Subject: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas? Hi everyone We have an AX4.0 SP2 with kernel 4.0.2503.953 Today the user reported very slow performance and the AOS crashed later on When we looked in the event viewer there was an error: Object Server 01: RPC error: RPC exception 14 occurred in session 3 This was logged maybe 50 to 100 times in a single second every second!!! I searched but could find no mention of RCP 14 error anywhere (including partner source) Does anyone have any idea what can cause this error or similar kind of mass logging in the event viewer every second? Also I heard the Ax4.0 AOS is likely to crash when the Ax32Serv.exe process reaches around the 2GB limit. Has anyone heard about this? Thanks James [Non-text portions of this message have been removed] Yahoo! Groups Links * To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ * Your email settings: Individual Email | Traditional * To change settings online go to: http://groups.yahoo.com/group/development-axapta/join (Yahoo! ID required) * To change settings via email: development-axapta-dig...@yahoogroups.com development-axapta-fullfeatu...@yahoogroups.com * To unsubscribe from this group, send an email to: development-axapta-unsubscr...@yahoogroups.com * Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
RE: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas?
Thanks Martin We upgraded the kernel to solve unstable problems of user sessions crashing or getting message about 'not enough resources so your session will be terminated' and I agreed it has helped a lot as the whole thing was stable for almost 2 months (rather than the usual few days) :) But then this one happened and I guess it was the 2GB limit. They are only 20+ users so we will just have to try to setup a start and stop routine (the main challenge to this is restarting the batch client which I asked about in previous postings in this group) Thanks again James -Original Message- From: development-axapta@yahoogroups.com [mailto:development-axa...@yahoogroups.com] On Behalf Of Malcolm Burtt Sent: 30 May 2010 01:56 To: development-axapta@yahoogroups.com Subject: RE: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas? Hi James The AX AOS will crash as it approaches 2GB of memory use and its likely that performance would degrade as it nears this upper limit. It could be that you have uncovered a memory leak in AX which might account for this but it could also be that you just have too many users that run memory hungry processes at the same time and simply need another AOS to spread the load. You could use performance monitor to track memory use over time to see if you can get a better handle on whther it is a leak or you could simply grab a new kernel (there are some memory leak fixes in newer kernels as I've been dealing with a leak problem for one of my clients over the last couple of months and the signs are good that the latest kernel has resolved the problem for them. Regards Malcolm Burtt Product Development Manager Touchstone Ltd From: development-axapta@yahoogroups.com [development-axa...@yahoogroups.com] On Behalf Of James Flavell [djf1...@gmail.com] Sent: 25 May 2010 13:18 To: development-axapta@yahoogroups.com Subject: [development-axapta] Live AOS failure RPC exception 14 reported in event log many many times per second - any ideas? Hi everyone We have an AX4.0 SP2 with kernel 4.0.2503.953 Today the user reported very slow performance and the AOS crashed later on When we looked in the event viewer there was an error: Object Server 01: RPC error: RPC exception 14 occurred in session 3 This was logged maybe 50 to 100 times in a single second every second!!! I searched but could find no mention of RCP 14 error anywhere (including partner source) Does anyone have any idea what can cause this error or similar kind of mass logging in the event viewer every second? Also I heard the Ax4.0 AOS is likely to crash when the Ax32Serv.exe process reaches around the 2GB limit. Has anyone heard about this? Thanks James [Non-text portions of this message have been removed] Yahoo! Groups Links
