Microsoft KB Archive/324939

= List of Base Operating System Fixes in Windows 2000 Service Pack 3 =

Article ID: 324939

Article Last Modified on 10/30/2006

-

APPLIES TO


 * Microsoft Windows 2000 Service Pack 3
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Service Pack 3

-



This article was previously published under Q324939



SUMMARY
Windows 2000 Service Pack 3 (SP3) addresses the following base operating system bugs and update scenarios:  Memory Leak in NeoMagic 5 and Yamaha OPL3 Drivers

Under heavy use, a memory pool leak occurs when Windows unloads the Swmidi.sys audio filter driver. Unsuccessful I/O Request Packet Not Marked as Pending When Retried

This update marks unsuccessful I/O Request Packet (IRP) requests that are retried by the Classpnp component as pending. User Receives an Error Accessing a Network Share After a Previous User Releases that Share

This issue typically occurs when a program holds a file open for a long time (in shared mode) but does not access the file frequently. This update permits a mini-redirector to mark a File Control Block (FCB) so that it will be orphaned when it is accessed later. This prevents file &quot;opens&quot; that follow from being blocked by the original cache manager &quot;open&quot; operation. Resources Assigned to a PCI-PCI Bridge Are Assigned to Any Child Devices

This update provides support for the use of the base address register (BAR) in the PCI bridge. Nonadministrator User Can Acquire a Volume Handle for the FILE_EXECUTE Function

The potential exists for nonadministrator users to obtain a Direct Access Storage Device (DASD) handle to a volume and perform operations that should be restricted to an administrator, such as volume dismounting. This update restricts DASD handles to administrators and to users with explicit permissions. Buffer Overrun in Control.exe

When between 300 and 400 characters are passed to the NTDS Control.exe command line, this overflows the buffer in Control.exe, causing stack corruption. Panning and Volume Controls Respond Slowly

When you load a large audio file into memory, the panning and volume controls may stop responding, or may respond very slowly. This issue is most noticeable on a computer that does not have a large amount of physical RAM installed.</li> Hard Error Request Causes Windows to Stop Responding

The NTFS files system does not reference the issuing thread when posting a hard error request. As a result, Windows may stop responding if the thread is ended before the error is processed. This update causes NTFS to reference the issuing thread before posting a hard error, and to unreference it when the request is complete.</li> Multiple Perflib Errors in the Application Log After You Install Small Business Server 2000

After you install Windows 2000 Server, promote it to an Active Directory domain controller, and then install Microsoft Small Business Server 2000 (installing all components), the application event log may be filled with multiple events similar to the following:

Type: Error

Source: NTFRSPerf

Category: None

Event ID: 13537

Date:

Time:

User: N/A Computer:

Description:

The call to the Registry failed in the Open function of the FileReplicaSet Object. The counter data for this object will not be available. The FileReplicaSet object contains the performance counters of the Replica sets whose files are being replicated by the File Replication Service.

-and-

Type: Error

Source: Perflib

Category: None

Event ID: 1008

Date:

Time:

User: N/A

Computer:

Description:

The Open Procedure for service &quot;FileReplicaSet&quot; in DLL &quot; :\WINNT\system32\NTFRSPRF.dll&quot; failed. Performance data for this service will not be available. Status code returned is data DWORD 0.

Data: 0000: 02 00 00 00 ...

</li> Initiator ID  Registry Keys Are Not Created When SCSI Miniport Driver InitiatorBusId Is Set to Greater Than 0x7f

In this scenario, the Initiator Bus ID array is declared to be a CCHAR (signed char). However, it should actually be declared to be UCHAR (unsigned char). Because of this, setting the Initiator ID to greater than 0x7F causes sign-extension problems.</li> HTTP Error 414 Is Not Returned in Response to an Overly Long CGI Request

After you submit a CGI request of anywhere from 70,000 to 90,000 characters in length, the expected &quot;HTTP Error 414: Request URI Too Long&quot; error message is not returned. Additionally, the CGI environment becomes corrupted after completing the request.</li> Unauthorized SMB Service Computer Causes a Windows 2000 Client to Stop Responding

A modified SMB Service computer may cause a Windows 2000 client to stop responding when accessing it. The SMB Service computer causes the Windows 2000 client to try to release an unallocated buffer.</li> RxCeCompleteConnectRequest Routine Uses a Freed I/O Request Packet Address

A race condition exists where the RxCeCompleteConnectRequest routine can call the address of an I/O Request Packet (IRP) that has been freed.</li> Exchange 2000 Server Setup Is Turned Off on Windows-Powered Devices

This update adds a setting to the Apcompat.inf file to prevent the installation of Microsoft Exchange 2000 Server on Windows-powered devices.</li> File Replication Service (FRS) Event ID 13506 and ID 13555

An assert may occur when a local create change order (CO) is sent to an outbound partner. In this case, not all outbound partners are available, and therefore the staging file remains in the staging table. This outbound member is later removed and re-added to the replica set. At this time, it receives the same CO from its inbound partner. This new member has a new originator globally unique identifier (GUID), and therefore the CO is not dampened. This CO is treated as a remote CO, but because it was already in the staging table, it is picked up with the old flags. The following events are logged when this error occurs:

Event ID: 13506

Description:

The File Replication Service failed a consistency check ((Flags & STAGE_FLAG_INSTALLING) && (Flags & STAGE_FLAG_CREATED)) in &quot;StuExecuteInstall:&quot; at line 1324. The File Replication Service will restart automatically at a later time. If this problem persists, a subsequent entry in this event log describes the recovery procedure. For more information about the automatic restart right-click on My Computer and then click on Manage, System Tools, Services, File Replication Service, and Recovery.

-and-

Event ID: 13555

Description:

The File Replication Service is in an error state. Files will not replicate to or from one or all of the replica sets on his computer until the following recovery steps are performed:

Recovery Steps:

[1] The error state may clear itself if you stop and restart the FRS service. This can be done by performing the following in a command window:

net stop ntfrs

net start ntfrs

</li> Windows Backup Copies Registry Hive File to the Documents and Settings Folder

After you use Windows Backup to back up a server on which roaming user profiles are stored, one or more registry hive files similar to the following are created in the Documents and Settings folder:

REG00XXX

</li> Access Violation When You Install a Driver for the Floppy Disk Controller

A buffer overrun occurs when you install a floppy disk controller driver with a name that is 256 characters or more in length.</li> Update to Include All International Files in the System File Protection List

The System File Protection DLL file (Sfcfiles.dll) is updated to include additional protected international operating system files.</li> Human Interface Device Service Ignores Usage Page Information

This update causes the Human Interface Device Service (Hidserv.exe) to read the usage page for all devices, except for those devices whose vendor ID and product ID are stored in a registry key.</li> Computer Stops Responding When You Connect IEEE 1394 Device

On a dual-CPU Windows 2000-based computer, Windows stops responding (hangs) when you connect the eighth device to the IEEE 1394 (FireWire) port.</li> Windows Does Not Recognize Partition Size Greater Than 120 GB

When you install Windows 2000 Professional, the text mode portion of Setup permits you to create a hard-disk partition of greater than 120 gigabytes (GB). However, after Windows is installed, only the first 120 GB are available.</li> Error 59 Occurs During Attempts to Write to a Mailslot

When multiple users perform mailslot operations, and one of the programs quits, the virtual network root for the mailslot is deleted. As a result, the File Control Block (FCB) is marked as orphaned, causing operations that follow to be unsuccessful.</li> Cannot Safely Unplug IEEE 1394 Hard Disk

After you delete files from a hard disk connected to an IEEE 1394 (FireWire) port, and then you try to safely disconnect the device, you are warned that you cannot safely disconnect the device.</li> <li>Kernel Memory Dump Contains Unnecessary Information

Kernel memory dump contains pages that should not be included in the dump. This causes incorrect results during analysis. This behavior occurs because of a code misinterpretation of a value to be counted in bytes instead of in pages.</li> <li>Create Partition Wizard Permits Incorrect Partition Size

When you try to specify an incorrect partition size in the Create Partition Wizard, the Next button is unavailable (dimmed). However, if you click Back, and then click Next, the Next button becomes available, permitting you continue after you specify an incorrect partition size.</li></ul>

Additional query words: kbBaseOS list kbWin2000sp3fixlist

Keywords: kbinfo kbwin2000sp3fix kboswin2000fix kbpending KB324939

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.