The Service Host process may stop unexpectedly in Windows Server 2003

Article translations Article translations
Article ID: 932762 - View products that this article applies to.
Expand all | Collapse all

On This Page

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:
Could not start the Server service on Local Computer.
Error 5: Access is denied.
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

Update information

To resolve this problem, install one of the following updates, as appropriate for your situation.

Update for Windows Server 2003

http://www.microsoft.com/downloads/details.aspx?FamilyId=0D8E8225-096D-49F8-879A-F75D53BE3A8F

Update for Windows Server 2003 for Itanium-based Systems

http://www.microsoft.com/downloads/details.aspx?FamilyId=81A066DD-84E4-46B8-BA17-5CB88C2BD23C

Update for Windows Server 2003 x64 Edition

http://www.microsoft.com/downloads/details.aspx?FamilyId=C174BA3C-8C6E-4798-B9F9-27276028F274

Update for Windows XP x64 Edition

http://www.microsoft.com/downloads/details.aspx?FamilyId=D8925E0E-70F9-4A8F-9FB1-AA9D0E8A1D41

Hotfix information

A supported hotfix is 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 software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if 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. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

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
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Browser.dll5.2.3790.289978,33615-Mar-200706:15x86SP1SP1QFE
Windows Server 2003 with Service Pack 2, x86-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Browser.dll5.2.3790.404078,33615-Mar-200706:24x86SP2SP2QFE
Windows Server 2003 with Service Pack 1, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Browser.dll5.2.3790.2899205,31214-Mar-200715:43IA-64SP1SP1QFE
Wbrowser.dll5.2.3790.289978,33614-Mar-200715:44x86SP1WOW
Windows Server 2003 with Service Pack 2, Itanium-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Browser.dll5.2.3790.4040205,31214-Mar-200715:48IA-64SP2SP2QFE
Wbrowser.dll5.2.3790.404078,33614-Mar-200715:48x86SP2WOW
Windows Server 2003, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Browser.dll5.2.3790.2899128,51214-Mar-200715:43x64SP1SP1QFE
Wbrowser.dll5.2.3790.289978,33614-Mar-200715:43x86SP1WOW
Windows Server 2003 with Service Pack 2, x64-based versions
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Browser.dll5.2.3790.4040128,51214-Mar-200715:48x64SP2SP2QFE
Wbrowser.dll5.2.3790.404078,33614-Mar-200715:48x86SP2WOW

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

Properties

Article ID: 932762 - Last Review: June 21, 2014 - Revision: 7.0
Applies to
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • 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
Keywords: 
kbautohotfix kbexpertiseinter kbwinserv2003postsp2fix kbbug kbfix kbhotfixserver kbqfe KB932762

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com