PC Review


Reply
Thread Tools Rate Thread

CMD.EXE failed to initialize

 
 
Pekka
Guest
Posts: n/a
 
      29th Jun 2004
Windows 2000 Server SP4
This machine has several (30+) batch-jobs runing scheduled from MS Task Mgr.

Situation:
The server freezes and becomes unresponsive.
Any time of day.

I get several messages like this in the eventlog, leading up to the point of
system freeze.
Event ID: 26
Application popup: cmd.exe - Application Error : The application failed to
initialize properly (0xc0000142). Click on OK to terminate the application.

MS Knowledge Base article 824422 indicates that the "non interactive system
heap" may run out of resources.
I increased this value from 512 to 1024, a week ago. After this , the
frequency of freeze-situations has fallen. Allthough more seldom, it still
occures.

The RegKey "Windows" parameter "Shared Section" has 3 values. (current
value)
1. System wide heap (1024)
2. Per desktop heap (3072)
3. Non interactive desktop heap (1024) (increased from 512)

How high can I go on these values ?
Wich is the most relevant ?
Could I increase the 3. value to 2048 ?

Anybody


 
Reply With Quote
 
 
 
 
Jerold Schulman
Guest
Posts: n/a
 
      29th Jun 2004
On Tue, 29 Jun 2004 08:47:45 GMT, "Pekka" <(E-Mail Removed)> wrote:

>Windows 2000 Server SP4
>This machine has several (30+) batch-jobs runing scheduled from MS Task Mgr.
>
>Situation:
>The server freezes and becomes unresponsive.
>Any time of day.
>
>I get several messages like this in the eventlog, leading up to the point of
>system freeze.
>Event ID: 26
>Application popup: cmd.exe - Application Error : The application failed to
>initialize properly (0xc0000142). Click on OK to terminate the application.
>
>MS Knowledge Base article 824422 indicates that the "non interactive system
>heap" may run out of resources.
>I increased this value from 512 to 1024, a week ago. After this , the
>frequency of freeze-situations has fallen. Allthough more seldom, it still
>occures.
>
>The RegKey "Windows" parameter "Shared Section" has 3 values. (current
>value)
>1. System wide heap (1024)
>2. Per desktop heap (3072)
>3. Non interactive desktop heap (1024) (increased from 512)
>
>How high can I go on these values ?
>Wich is the most relevant ?
>Could I increase the 3. value to 2048 ?
>
>Anybody
>


I would first try adding 512.
If that doesn't work, set the desktop heap from 3072 to 3584.

Finally. increase the third value to 2048.

Jerold Schulman
Windows: General MVP
JSI, Inc.
http://www.jsiinc.com
 
Reply With Quote
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
initialize failed =?Utf-8?B?cXVhbnR1bXRpbWU=?= Windows XP Games 5 31st May 2006 03:03 AM
IIS Snap-in failed to initialize and .NET framework failed to inst =?Utf-8?B?SmVmZnJleQ==?= Windows XP Networking 0 30th Sep 2005 10:46 PM
Rundll32.EXE - DLL INITIALIZATION FAILED The application failed to initialize be J. Myers Windows XP General 2 31st Jul 2004 08:28 PM
AIW 128 Pro AGP TV Application Failed to Initialize the Capture device The TV Player failed to initialize the Video Tony Girgenti ATI Video Cards 9 6th Apr 2004 05:09 AM
IIS install failed: Snap-in failed to initialize: NNTP Protocol Jay Windows XP Networking 0 29th Jul 2003 09:40 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 01:44 PM.