How to reconfigure the shared memory allocation to allow newly created applications.

Article:TECH10665  |  Created: 2001-01-17  |  Updated: 2013-10-23  |  Article URL http://www.symantec.com/docs/TECH10665
Article Type
Technical Solution


Environment

Issue



How to reconfigure the shared memory allocation to allow newly created applications.

Error



Bpdbm.exe - Application Error
The application failed to initalize properly (0xc0000142). Click on OK to terminate the application.

Solution



The default configuration of WindowsNT 4.0 and Windows 2000 does not always provide enough shared memory for the spawning of new applications.  If enough applications are trying to start at one time, "bpdbm" may fail with the following error: "The application failed to initialize properly (0xc0000142). Click on OK to terminate the application."  This can be resolved by reconfiguring the shared memory allocation so that more memory is available to newly created applications.  This can be done with the following procedure:

  • From the Start menu on the master server, select "RUN"
  • Type regedt32 and press <enter>
  • Select the hive called "HKEY_LOCAL_MACHINE on Local Machine"
  • Open the key "\System\CurrentControlSet\Control\SessionManager\SubSystems\Windows"
      The default data for this value will look something like the following (all on one line):
          
       %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

    In SharedSection=1024,3072, 3072 represents the heap size for desktops associated
    with the interactive Window station. Scan along the line until the
    part that defines the SharedSection values is reached and add ",4096" after the second
    number. This value should now look something like the following:

       %SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,3072,4096 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ProfileControl=Off MaxRequestThreads=16

    Figure 1


    Note: Incorrect use of the Windows registry editor can have disastrous results on a computer operating system. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application.

    Formal Resolution:  This issue has been resolved with patch 341_2.

    http://seer.support.veritas.com/docs/240966.htm


  • Legacy ID



    235978


    Article URL http://www.symantec.com/docs/TECH10665


    Terms of use for this information are found in Legal Notices