Hi James, There are a couple of different ways of handling the restart of the batch server. The best way is to get an extra batch server license and have a AOS service running on the batch server and have the batch client connect to it's on AOS service. This way users can't mess with the batch AOS and the batch AOS can't mess with the users.
Before we had the separate batch AOS service, we ran one script on the batch server to reboot the batch server at the same time as the other script was stopping the AOS service on the AOS server. We have a specific ax client configuration file on the batch server with the batch parameter in the 'command to run at application startup' Then as a startup task we have a script that starts the ax client: Run "C:\Program Files\Microsoft Dynamics AX\40_sp2\Client\AX40_Batch.axc" From: James Flavell Sent: Monday, May 31, 2010 12:59 AM 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? 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] [Non-text portions of this message have been removed]
