Overcoming User32.dll Initialization Failure Errors

ID: Q142676

The information in this article applies to:

Microsoft Windows NT Workstation version 4.0
Microsoft Windows NT Server version 4.0

SYMPTOMS

When you try to start a service a pop-up dialog box appears with the following message:

<ServiceName> - DLL initialization failure Initialization of the dynamic link library c:\windows\system32\user32.dll failed. The process is terminating abnormally.

CAUSE

The system has run out of memory to create a new desktop heap for the service being started.

RESOLUTION

Fixing this problem requires editing of the Registry and restarting the computer concerned.

WARNING: Using Registry Editor incorrectly can cause serious, system-wide problems that may require you to reinstall Windows NT to correct them. Microsoft cannot guarantee that any problems resulting from the use of Registry Editor can be solved. Use this tool at your own risk.

Run the Registry Editor(Regedt32.exe).

Under the HKEY_LOCAL_MACHINE subtree, go to the following subkey:

\System\CurrentControlSet\Control\Session Manager\ 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

You will need to make the following change to this value:

Scan along the line until you reach the part that defines the SharedSection values and add ",512" after the second number. This value should now look something like the following:


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

After making this change, close Regedt32 and restart the server.

This change will limit the size of desktop heaps created by noninteractive services to 512 KB, which should be ample for most services.

Adding this optional third value defines the desktop heap size for non- interactive desktops (e.g. services) to be 512K. By default they will use the same desktop heap size as interactive desktops which is defined by the second value (3072 which equates to 3MB). The minimum that this third value can be set to is 128. Any attempts to set this value to less that 128 will result in 128 being used. Setting this value to 512 will allow approximately 90 services to be started before this problem reoccurs.

For a fuller definition of what the first two parameters to SharedSection mean, see Article Q126962

STATUS

This behavior is by design. The registry entry allows users to override the default settings.

Additional query words: Exchange SMS SNA SQL Server prodnt stop initialize initialized heap space heapspace winstation desktop

Keywords : kbenv nt32ap ntconfig NTSrvWkst
Version : winnt:4.0
Platform : winnt
Issue type :