Hi If the machine is blue screening then it’s unlikely to be an issue with the Ax application and your assumption that its broken hardware seems like a reasonable one. There is no way that it is your X++ code that is doing this.
In order to get the online users reset you need to shut down all object servers that remain active then delete the axdat.udb file form the Ax appl/standard directory (or whatever your application directory is called). Regards Malcolm Burtt Touchstone Group People - Partnership - Solutions From: Axapta-Knowledge-Village@yahoogroups.com [mailto:axapta-knowledge-vill...@yahoogroups.com] On Behalf Of asit nayak Sent: 29 April 2010 22:02 To: Axapta-Knowledge-Village@yahoogroups.com Subject: [Axapta-Knowledge-Village] AOS crash Hi All, We are facing AOS crash issue with one of our client because of hardware failure on one of the AOS. Here is configuration: 1. 2 AOS - AOS1 and AOS2(batch server) 2. Users have config file for connecting to AOS1 and then AOS2. 3. Client 53 user license and all licenses are fully used most of the time Problem: 1. AOS1 does down periodically for some reason– goes into hardware blue screen. (Most likely it is hardware, memory or nick card is bad). 2. Because of AOS1 goes down – it loses network connection too. Resulting into leaving all user sessions as open as online users in AX DB 3. When users tries to reconnect – AOS 2 is up but Online user sessions are not released because db still doesn’t know that AOS1 is down. Hence users get error – Maximum licenses are consumed. Solution we are looking for: 1. Any reason by any chance take AOS server itself down? (Just to make sure this is not code issue. Code will generally take AOS Service down) 2. How can we release open user sessions from AOS1 when it goes down? So at least users can connect from AOS2. Thanks Asit
