Hi,
That was actually my original configuration and doesn't help much, because during the day, there is always at least one user logged in so the AOS will hardly shut down, and even if it did - it would not shut down the service but only the instance. In the mean time i have found out that socket error 10054 probably refers to lost packets on the network. That is why I am now experimenting with the follwing way: I have assigned a specific port number to the AOS and have the clients (especially those that connect through a ISDN-router) connect directly to this port via the command line option. This eliminates the initial UDP communication between clients and server, as my impression was that the AOS "crash" alway occured when an ISDN client initially tried to connect and some packets seemed to be lost. Regards Stefan Osterburg Malcolm Burtt schrieb: > > Hi > > We've experienced an identical problem at one of our clients. We got around > the problem by setting an idle timeout on the AOS instance and setting it up > to start on demand. > > Regards > > Malcolm Burtt > Global IT Group > "Business Solutions designed for YOUR business processes" > Global IT Group is the trading name of Touchstone Global Business Solutions > Ltd. and is part of the Touchstone Group PLC. > > > > -----Original Message----- > From: Stefan Osterburg [mailto:[EMAIL PROTECTED] > Sent: 06 April 2005 13:14 > To: development-axapta@yahoogroups.com > Subject: [development-axapta] AOS network problems > > > > > Hello, > > I have the following problem with my AOS server: > > It runs fine (users can connect and work normally) up to some point. > Then I get the following message from the AOS server in the event log: > > "Server Manager: Fatal socket error 10054 occured while receiving > service requests from clients." > > Afterwards no new users can connect to the AOS ("No AOS could be > found with the current configuration"). Users still connected to the > AOS can continue to work normally. > > To fix the problem I have to restart the AOS service (restarting only > the AOS instance is not enough). > > Does anyone know what causes this problem, and how to prevent it from > happening? > > Regards > Stefan Osterburg > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/development-axapta/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
