user32.dll errors.

[mnewell]

Hello,
I have an NT 4.0 bdc that gets user32.dll initialization errors when opening programs. (Explorer, WINS mngr, etc). The only fix I saw was a reg hack to limit the amount of ram a desktop heap can get but it didn't fix the errors.

Has anyone ever seen this before?

Thank you,
Mike.

 

[jake2k2]

does this error also come up when the screen saver kick in ?
(ie. when you set it to activate after 5 min)
if so I think I seem it before, I also have tried the reg hack, it didn't work

if all else fail, try to re apply the service pack see if it help

 

[jake2k2]

does this error also come up when the screen saver kick in ?
(ie. when you set it to activate after 5 min)
if so I think I seem it before, I also have tried the reg hack, it didn't work, so I just disabled the screen saver

if all else fail, try to re apply the service pack see if it help

 

[mnewell]

Hey Jake,
No screen saver. I get the error when I try and run anything like explorer or my computer. The server is mainly a file server and in functioning fine on the network but I can't do anything on the server itself.

Any other ideas?

Thanks again,
Mike.

 

[JUJUSHADOWN]

Are you using roaming profiles? If so it may be corrupt, we had a similiar problem, we had to delete the roaming profile and rebuild it.

The registry hack only worked for us on screen savers.

 

[mnewell]

Hey JUJUSHADOWN,
No roaming profiles. It also happens no matter who is logged in on the server.

The drag is that it's the last 4.0 BDC in my 2K domain and I need to go to native mode for an Exchange 2K upgrade and I can't upgrade that server to 2K until I can get these errors cleared up.

Thanks again,
Mike

 

[VIRoots]

Im going through the same thing.. if anyone knows what the issue is please let me know

 

[mnewell]

In my scenerio, it was a fax program installed on the server causing a memory leak.

Any software on that system other than Windows? Fax, AV, etc?

Start by disabling all services and software not needed for the server to run and see if you still get the error after a few days. Then add the programs back one by one to see which one is causing the error.

That's how I ended up fixing this on my server.

HTH,
Mike