Screensaver crash - user32.dll

[bvautour]

I'm hoping someone has seen this issue before and has some insight. The issue seems to be related to NT and SMS

We are Trying to use the NT Resource Kit's winexit.scr Autologoff Screen Saver in a on shared NT4.0 desktop with roaming profiles, about 1000 PC's.  When the timer expires on the winexit screen, instead of logging out the user, and
error screen pops up with the following message:

"Winexit.scr - DLL Initialization Failed"

"Initailization of the dynamic link library c:\winnt\system32\user32.dll failed.  The process is terminating abnormally."

This error leaves the user logged in, which is my issue.

This error goes away if the user is has Administrative rights. For other reasons, we don't allow our users to be local admins. Also if machine is rebooted, the user can log in for an undetermined number of times and the error may not happen at all.  But at some point the error
does begin to happen, and once it does, it does not stop occuring. Avergae 10 - 30 cycles for it to reoccur.

Things we have tried:

1) Reset permissions in the registry - All permissions to everyone
2) Tried both versions of winexit.scr from NT 4.0 and Win2K Resource kits.
3) We have also tried adjusting registry settings for desktop heap size as
suggested by microsoft KB article Q142676. The recommended configuration
was tried and we have also tried increasing the recommended values
4) Made sure that the SMS services login has administrative rights.
5). The problem recently manifested itself, and we have tried to isolate it
to a specific appliaction. We feel it may be SMS related (see comments below re SMS)

Some Facts:
OS - NT 4.0 Workstation with SP6a installed.
IE 6.0 with SP1 and security hotfixes
MS SMS 2.0 Client installed w/lastest service pack.

Additional Info:
Occurs on multiple machine models.
We tried using both older and newer versions of user32.dll (NT sp5, Win2K)- results here were not good.
If the MS SMS 2.0 services client is turned off, the error will not happen. Once turned on, error returns.
The error occurs when any screen saver tries to execute, not just WINEXIT.SCR.

 

[dhauca]

Did you ever find a resolution for this issue? We are experiencing the same after a SMS sp 5 upgrade of the client

Thanks in advance,

 

[ceigl]

Check this out:

http://www.myitforum.com/forums/tm.asp?m=29973&p=7&tmode=1

Cheers,
Chris

 

[dhauca]

Thanks for the link Chris71,

We contacted the person in the post and they were notified by Microsoft that it is a known bug when installing SMSV2SP5 on NT 4 Workstations and that Microsoft is in the test phase with a priority 1 of developing a fix. They hopefully expect a fix to be available in 2-4 weeks.

 

[bval]

We are experiencing a very similar behaviour and have tried most of the steps you mentioned with similar results. We are on NT4, with SMS SP3. (Intending on moving to SP5, but not ready yet) Although there were some user32.dll problems reported previously, we are only starting to experience them en-mass since deploying IE 6.0.

Has anyone experienced a similar behaviour when installing IE 6.0? We are curious why the IE 6.0 upgrade might trigger this problem when it doesn't seem to touch any of the SMS files mentioned in the recently released MS hot-fix. Also if it was SMS related, you would think that it would be more system wide.

Any assistance would be much appreciated.

Thanks.