Win2000 fails to logoff

M

Matt

Hi

My computer was recently running very slowly due to the
patch 835732 being installed. I uninstalled it and it
worked fine until now. I've realised since I removed
835732 that an event has been recored in the application
log.

Details are:
Event Type: Warning
Event Source: EventSystem
Event Category: Firing Agent
Event ID: 4098
Date: (date)
Time: (time)
User: N/A
Computer: (computer name)
Description:
The COM+ Event System failed to fire the Logoff method on
subscription {113197E3-4575-4711-BB92-5994E4CF5956}. The
subscriber returned HRESULT 800706BA.

What is happening is I go through the standard shut down
procedure and it hangs on "Saving your settings..." and
I've even waited 5 whole minutes and it still doesn't shut
down. The blue bar under the win 2000 logo keeps moving
though.

I eventually just press the reset power button and have to
shut down from the windows logon screen.

This doesn't happen EVERY time but probably 1 in 2 which
is still annoying.

I can't reinstall KB835732. The computer just drags on WAY
TOO SLOWLY. *835732 is a prevention for the sasser virus.
I have a good enough firewall and never get viruses*

My computer is Windows 2000 Professional Service Pack 3
with Internet Explorer 6.0. I also have Visual Studio.NET
2003 which I think has something to do with the
COM+ 'thingy(!)'

I also have a program called 'User Profile Hive CleanUp
Service' (or something like that) which closes non
responsive processes at shut down. I've tried reinstalling
it and the problem still persists.

*I am NOT reinstalling 835732!!!*


Thanks to anyone who can help :)
 
J

Jason Hall [MSFT]

--------------------
From: "Matt" <[email protected]>
Subject: Win2000 fails to logoff
Date: Sun, 30 May 2004 21:30:46 -0700

Anyone???
----------------------

I would recommend the following steps:

1. Re-apply COM+ by going to Start > Settings > Control Panel > Add/Remove
Programs > Add/Remove Windows Components > Next > [Next] > Finish
If this does not resolve the issue,
2. Run SFC /SCANNOW from the CMD prompt
If this does not help...
3. Repair Windows, or install hotfix 835732 and try to figure out why it
makes your particular machine run slow

Please let me know if any of the above helps.

--
~~ JASON HALL ~~
~ Performance Support Specialist,
~ Microsoft Enterprise Platforms Support
~ This posting is provided "AS IS" with no warranties, and confers no
rights.
~ Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
~ Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
 
M

Matt

I didn't need to try that, but thanks for posting it :)

It ended up being something starting at startup in the RUN
key in the registry. It was being executed through
rundll32.exe. Can't remember the exact name, but problem
solved :)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top