TimRegester
Technical User
I installed a brand new Fujitsu Siemens server with Windows Server 2003 Std Edition in January 2004. Apart from one power down the server has worked seemingly faultlessly since. But I was shocked to find it had run out of memory last week and had to reboot the server.
This server is acting as Domain controller, DNS Server, DHCP Server as well as file and print. It has 512MB of physical memory and serves a network of 26 PCs all running XP Pro. There are two non-MS services running, one for the UPS monitoring software and one for Sophos EM library.
I checked the task manager before rebooting LSASS.exe was the most memory hungry service and the total of the rest of the services including that did not match the amount of physical memory in use. All PCs were logged out at this point.
I guess I have (in time honoured fashion) a memory leak. My research on microsoft.com and on google reveals a known issue with LSASS.exe there is apparantly a hotfix for a known issue, kb 829993 which states as the cause:
"This problem occurs because of a memory leak that is associated with the Lsass.exe process. The rate of the leak depends on the number of groups and of group members that exist in the domain, and on the number of group-related queries"
I have one OU with three groups and one GPO within AD, the text above makes it unclear whether my server setup meets the criteria for this problem and hotfix, I am loathe to ring Microsoft especially as they charge so much and I am also only on site once a week ( the network works quite happily without any support and has done for months) so cannot provide the data they may request until I am onsite.
The workaround of a scheduled weekly reboot is ok for now but I need a fix.
Has anyone any suggestions/advice or similar experience that could shed some light on this issue.
Thanks in advance
Tim
This server is acting as Domain controller, DNS Server, DHCP Server as well as file and print. It has 512MB of physical memory and serves a network of 26 PCs all running XP Pro. There are two non-MS services running, one for the UPS monitoring software and one for Sophos EM library.
I checked the task manager before rebooting LSASS.exe was the most memory hungry service and the total of the rest of the services including that did not match the amount of physical memory in use. All PCs were logged out at this point.
I guess I have (in time honoured fashion) a memory leak. My research on microsoft.com and on google reveals a known issue with LSASS.exe there is apparantly a hotfix for a known issue, kb 829993 which states as the cause:
"This problem occurs because of a memory leak that is associated with the Lsass.exe process. The rate of the leak depends on the number of groups and of group members that exist in the domain, and on the number of group-related queries"
I have one OU with three groups and one GPO within AD, the text above makes it unclear whether my server setup meets the criteria for this problem and hotfix, I am loathe to ring Microsoft especially as they charge so much and I am also only on site once a week ( the network works quite happily without any support and has done for months) so cannot provide the data they may request until I am onsite.
The workaround of a scheduled weekly reboot is ok for now but I need a fix.
Has anyone any suggestions/advice or similar experience that could shed some light on this issue.
Thanks in advance
Tim
