Article ID: 932762
Article Last Modified on 10/12/2007
APPLIES TO
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
SYMPTOMS
The Service Host process (Svchost.exe) that hosts the Computer Browser service and the Server service stops unexpectedly in Microsoft Windows Server 2003. Additionally, if you try to restart the Server service that is hosted by the Service Host, you receive the following error message:
When this problem occurs, the following services also stop:
- Application Experience Lookup Service (AeLookupSvc)
- Automatic Updates (Wuauserv)
- Background Intelligent Transfer Service (BITS)
- COM+ Event System (EventSystem)
- Computer Browser (Browser)
- Cryptographic Services (CryptSvc)
- Distributed Link Tracking Client (TrkWks)
- Help and Support (Helpsvc)
- Logical Disk Manager (Dmserver)
- Network Connections (Netman)
- Network Location Awareness (Nla)
- Remote Access Connection Manager (RasMan)
- Secondary Logon (Seclogon)
- Server (Lanmanserver)
- Shell Hardware Detection (ShellHWDetection)
- System Event Notification (SENS)
- Task Scheduler (Schedule)
- Windows Audio (AudioSrv)
- Windows Firewall/Internet Connection Sharing (SharedAccess)
- Windows Management Instrumentation (Winmgmt)
- Wireless Configuration (WZCSVC)
- Workstation (Lanmanworkstation)
CAUSE
The problem is most likely to occur if some third-party server becomes the master browser. When a Windows-based server is the master browser, it does not let any host that is advertising its share to use a server comment that is larger than 48 bytes. When a third-party server message block (SMB) server becomes the master browser, it lets a host use a server comment that is larger than 48 bytes. In this case, when a Windows Server receives and tries to process the browser list, the Server service crashes. This behavior occurs because there is an overflow that eventually leads to a heap corruption.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003 with Service Pack 1, x86-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Browser.dll | 5.2.3790.2899 | 78,336 | 15-Mar-2007 | 06:15 | x86 | SP1 | SP1QFE |
Windows Server 2003 with Service Pack 2, x86-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Browser.dll | 5.2.3790.4040 | 78,336 | 15-Mar-2007 | 06:24 | x86 | SP2 | SP2QFE |
Windows Server 2003 with Service Pack 1, Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Browser.dll | 5.2.3790.2899 | 205,312 | 14-Mar-2007 | 15:43 | IA-64 | SP1 | SP1QFE |
Wbrowser.dll | 5.2.3790.2899 | 78,336 | 14-Mar-2007 | 15:44 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, Itanium-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Browser.dll | 5.2.3790.4040 | 205,312 | 14-Mar-2007 | 15:48 | IA-64 | SP2 | SP2QFE |
Wbrowser.dll | 5.2.3790.4040 | 78,336 | 14-Mar-2007 | 15:48 | x86 | SP2 | WOW |
Windows Server 2003, x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Browser.dll | 5.2.3790.2899 | 128,512 | 14-Mar-2007 | 15:43 | x64 | SP1 | SP1QFE |
Wbrowser.dll | 5.2.3790.2899 | 78,336 | 14-Mar-2007 | 15:43 | x86 | SP1 | WOW |
Windows Server 2003 with Service Pack 2, x64-based versions
File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
---|---|---|---|---|---|---|---|
Browser.dll | 5.2.3790.4040 | 128,512 | 14-Mar-2007 | 15:48 | x64 | SP2 | SP2QFE |
Wbrowser.dll | 5.2.3790.4040 | 78,336 | 14-Mar-2007 | 15:48 | x86 | SP2 | WOW |
WORKAROUND
To work around this problem, limit the computer description of any third-party server message block server on the network to a maximum of 48 characters.
STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Additional query words: srvcomment server comment SMB crash 48 characters access violation master browser Linux Samba
Keywords: kbbug kbfix kbqfe kbpubtypekc kbexpertiseinter kbhotfixserver kbwinserv2003postsp2fix KB932762