Microsoft KB Archive/328055

From BetaArchive Wiki

Article ID: 328055

Article Last Modified on 2/1/2007



APPLIES TO

  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Service Pack 1
  • Microsoft Windows 2000 Service Pack 3
  • Microsoft Windows 2000 Service Pack 2
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Advanced Server



This article was previously published under Q328055

SYMPTOMS

If you are using a program that uses many sharable resources (for example, shared memory, file mappings, or common DLLs that are large), if these resources are shared by other programs, the server may stop responding (hang).

For example, if a Systems Management Server (SMS) child site server is receiving the updates from the SMS parent site server, when SMS Distribution Manager expands the received package to deploy it to either itself or to other distribution points, the server stops responding.

CAUSE

This problem is caused by a design issue in Windows 2000 memory. This problem is time dependent and not deterministic.

RESOLUTION

Service Pack Information

To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

260910 How to Obtain the Latest Windows 2000 Service Pack


Hotfix Information

A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows 2000 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this fix has the file attributes (or later) 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 tool in Control Panel.

   Date         Time     Version        Size        File name
   --------------------------------------------------------------
   17-Sep-2002  18:48   5.0.2195.5265     42,256   Basesrv.dll
   17-Sep-2002  18:48   5.0.2195.6011    708,880   Kernel32.dll
   17-Sep-2002  18:48   5.0.2195.6060  1,688,768   Ntkrnlmp.exe
   17-Sep-2002  18:48   5.0.2195.6060  1,688,448   Ntkrnlpa.exe
   17-Sep-2002  18:48   5.0.2195.6060  1,709,056   Ntkrpamp.exe
   17-Sep-2002  18:48   5.0.2195.6060  1,666,496   Ntoskrnl.exe
                



STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Windows 2000 Service Pack 4.

MORE INFORMATION

This problem has been reported on servers that are running both SMS and Lotus Notes. When large SMS packages are deployed to all the site servers at the same time, you may notice that some receiving servers become unresponsive. You may have to restart all unresponsive servers to recover. This problem has frequently been reported on site servers that are running both SMS and Lotus Notes on the same Windows 2000-based server. Sites that have dedicated Lotus Notes servers may not experience this problem. The smaller SMS deployments (four or less site servers at a time) may not exhibit these symptoms.

For additional information about how to obtain a hotfix for Windows 2000 Datacenter Server, click the article number below to view the article in the Microsoft Knowledge Base:

265173 The Datacenter Program and Windows 2000 Datacenter Server Product


Keywords: kbbug kbfix kbwin2000presp4fix kbqfe kboswin2000fix kbwin2ksp4fix kbhotfixserver KB328055