Windows Forum

Ask something
Discussion Locked

NT Server Problem

0 helpful
9 replies

by cstaetsch

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am running an NT server on a small network. After 3-4 days I get the following message when I attempt to fun any program
Initialization of the dynamic link library c:\winnt\system32\user32.dll failed. I have run the latest service pack and sameproblem. Nothing in event viewer indicates the problem

9 replies

by dmiles

Sounds like a problem of services being loaded,and the command strings have become corrupt,check Microsoft knowledgebase article for specific service that is causing the problem
Reference the following sites
1)http://robert.grefstad.com/win/winnt/

by mckaytech

This sort of thing sounds vaguely familiar to me. Do I understand correctly that this occurs every 3-4 days and can I assume that re-booting the computer clears it up?

If so, can you let us know what other programs are running on this server (is it just file and printer sharing or is it also a Web server, etc.).

It seems to me that last time I saw this problem, it turned out to be one of the applications but I can't recall which one. I could probably find it on Microsoft's Technet site but it appears to be down at the moment.

paul

by joseph moore

I found TechNet article Q142676 that says "The system has run out of memory to create a new desktop heap for the service being started."
The solution is to open the Registry, go to HKEY_LOCAL_MACHINE\Systemem\CurrentControlSet\Control\Session Manager\ SubSystems\Windows
And modify the SharedSection entry.

Please read the article for instructions on what to do. It does sound like it will help your problem.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q142676
(please remove anyspaces)

Hope this helps.

by bkinsey1

Sounds like something is leaking memory so that after a few days, the system runs out of memory to start new programs. Check Task manager when you get the error and look at the memory usage by all running processes. Look for extrememly large numbers that look out of place, and check that process name against TechNet for a known issue with memory leaks. Could be that an update to one of the apps you're running could solve the problem.

This discussion is closed to new replies.