Access Violation in Cmd.exe Calling CreateProcess() with Long Path (268722)



The information in this article applies to:

  • Microsoft Windows NT Server 4.0
  • Microsoft Windows NT Server 4.0 SP4
  • Microsoft Windows NT Server 4.0 SP5
  • Microsoft Windows NT Server 4.0 SP6
  • Microsoft Windows NT Server 4.0 SP6a
  • Microsoft Windows NT Workstation 4.0
  • Microsoft Windows NT Workstation 4.0 SP4
  • Microsoft Windows NT Workstation 4.0 SP5
  • Microsoft Windows NT Workstation 4.0 SP6
  • Microsoft Windows NT Workstation 4.0 SP6a

This article was previously published under Q268722

SYMPTOMS

Parent programs that spawn a child program pass an environment block to the spawned child. In cases in which an extremely long path (more than 1,900 bytes) exists in the parent environment, an access violation may occur during the startup of a child process. For example, this might occur when a Setup program (as a parent) starts another program as a child process.

The actual supported length for a path statement is 1,024 characters. Typically, a "Path too long" error message is generated when the path exceeds approximately 1,900 bytes. However, an extremely long path (more than 1,024 bytes but less than the amount that triggers the "Path too long" error message) may still generate an error message when a child process is spawned.

As the parent spawns a child process (calling CreateProcess), a new Cmd.exe session is started and some expansion of the inherited environment block occurs. The following error message may occur when the new environment block is initialized for the child process:
Cmd.exe - Application Error

The instruction at "0x77f64bab" referenced memory at "0x0067006f". The memory could not be "written".
Click on OK to terminate the application.

CAUSE

An incorrect initialization of a buffer is occurring.

RESOLUTION

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, 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 usual 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 should have the following file attributes or later:
   Date        Time    Size     File name  Platform
   ------------------------------------------------
   07/20/2000  03:02p  208,144  Cmd.exe    Intel
				

WORKAROUND

To work around this issue, shorten the path statement length.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Modification Type:MinorLast Reviewed:9/26/2005
Keywords:kbHotfixServer kbQFE kbbug kbfix KB268722