A 32-bit process calls the CreateProcess function but does not successfully start another 32-bit process

Article translations Article translations
Article ID: 822961 - View products that this article applies to.
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all

On This Page

SYMPTOMS

When one 32-bit process calls the CreateProcess function to start a second 32-bit process, the second 32-bit process does not start as expected.

If you use Performance Monitor to monitor the Private Bytes, the Virtual Bytes, and the Working Set counters of the 32-bit process that calls the CreateProcess function, you notice that the value of each counter increase over time. However, the Handle count value does not increase.

CAUSE

This problem occurs because, when a 32-bit process calls the CreateProcess function to start another 32-bit process, a memory leak occurs in the 32-bit process that made the CreateProcess call. The second process cannot start because there is not sufficient memory left to run the process.

RESOLUTION

Update information

English

The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download
Download the WindowsServer2003-KB822961-ia64-ENU.exe package now. Release Date: October 22, 2003

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to obtain Microsoft support files from online services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.

Japanese

The following file is available for download from the Microsoft Download Center:
Collapse this imageExpand this image
Download
Download the package now.

French/German

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 Server 2003 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites

No prerequisites are required.

Restart requirement

You must restart you computer after you install this update.

Update replacement information

This update does not replace any other updates.

File information

   Date         Time   Version      Size     File name
   ----------------------------------------------------
   04-Jul-2003  01:54  5.2.3790.67  449,536  Wow64.dll 

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 822961 - Last Review: February 27, 2014 - Revision: 3.9
APPLIES TO
  • Microsoft Windows Server 2003, 64-Bit Datacenter Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows XP 64-Bit Edition Version 2003
Keywords: 
kbnosurvey kbarchive atdownload kbqfe kbbug kbfix kbqfe kbwinserv2003presp1fix KB822961

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