Hi Michael, Thanks for the reply. The server has 8GB, but mirrored for redundancy, so 4GB essentially. Boot.ini:
C:\>type boot.ini [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows Server 2003, Enterprise" /3GB /noexecute=optout /fastdetect /SOS /USERVA=3030 /BASEVIDEO Going back through the event logs suggests this has been a problem for around 4 weeks, nothing happened on that date so it's a mystery as to what really caused this to start. Cheers Richard From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael B. Smith Sent: 09 December 2008 13:38 To: MS-Exchange Admin Issues Subject: RE: IIS / EAS problem on backend Sounds like you are out of memory. Error 10055 is "An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full." Have you looked at the HTTP.SYS error files? How much memory is on that computer and what are the boot.ini settings? Regards, Michael B. Smith, MCITP:SA,EMA/MCSE/Exchange MVP My blog: http://TheEssentialExchange.com/blogs/michael I'll be at TEC'2009! http://www.tec2009.com/vegas/index.php From: Sobey, Richard A [mailto:[EMAIL PROTECTED] Sent: Tuesday, December 09, 2008 6:17 AM To: MS-Exchange Admin Issues Subject: IIS / EAS problem on backend Hi all, Our environment is currently mixed with Exchange 2003 backends and Exchange 2007 CAS / HT / Mailbox servers. The error below (Event ID 3027, source Server ActiveSync) is in the application log, extremely frequently, on one of my 2003 backend servers. An error occurred on the socket that is used to process AUTD notifications. The error code is [10055]. As a result, AUTD has been uninitialized, but it will be reinitialized upon receipt of the next Ping request. If you continue to see this message, restart IIS. Followed by: (in separate logged events) IP-based AUTD has been uninitialized. And IP-based AUTD has been initialized. Sometimes the AUTD uninitialized (Event ID 3026) and initialize (3025) events will occur without the socket error. The server is standalone Exchange 2003 EE SP2 (Windows Server 2003 EE SP2) and Symantec Mail Security. No other application runs on the server. The error seems to cause OWA to throw a "500 Server error" VERY occasionally. I've been able to reproduce it once with a test account, and only a handful of users have actually reported a problem. Of course, there may be an entirely separate reason for this, but since AUTD is tied in with IIS and therefore OWA, I'm hedging my bets. Does anyone have a clue how to proceed before I open a PSS case? IIS has been restarted, and the entire server was bounced four days ago. Thanks Richard ~ Ninja Email Security with Cloudmark Spam Engine Gets Image Spam ~ ~ http://www.sunbeltsoftware.com/Ninja ~
