COM+ error since install of power management 1.40

[osaris]

Hello,

I'm running a T60p with XP Pro SP3, since I've upgraded to power management 1.40, my eventlog contains lot of error similar to this one :

"Le système d'événements de COM+ n'a pas pu déclencher la méthode StartShell de l'abonnement {F6FE5592-FCBC-44AD-A836-D37F5085ED5B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. L'abonné a renvoyé HRESULT 80004001."

It happens in many case, when I login (StartShell), when screensaver start (StartScreenSaver), when it stops (StopScreenSaver) etc... If I uninstall power management release 1.40, the problem disappear.

Regards,

Osaris

[bgibney3]

Exact same issue here, T60, Power Manager 1.40 installed:

The COM+ Event System failed to fire the Logon method on subscription {F6FE5592-FCBC-44AD-A836-D37F5085ED5B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.  The subscriber returned HRESULT 80004001

The COM+ Event System failed to fire the StartShell method on subscription {F6FE5592-FCBC-44AD-A836-D37F5085ED5B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.  The subscriber returned HRESULT 80004001

The COM+ Event System failed to fire the DisplayLock method on subscription {F6FE5592-FCBC-44AD-A836-D37F5085ED5B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}

The COM+ Event System failed to fire the DisplayUnlock method on subscription {F6FE5592-FCBC-44AD-A836-D37F5085ED5B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}

etc.

Should add that I'm running XP Pro SP2, not SP3

ThinkPad Power Management Driver v1.44

ThinkPad Power Manager v1.40

Message Edited by bgibney3 on 08-11-2008 11:45 AM

[Jason404]

 

Exact same issue here as well.  At least I know that it has something to do with Power Manager now, having just entered the error into Google search.

I have dozens of these entries in Event Viewer: 

The COM+ Event System failed to fire the StartShell method on subscription {F6FE5592-FCBC-44AD-A836-D37F5085ED5B}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}. The subscriber returned HRESULT 80004001.

Windows XP SP3

ThinkPad Power Management Driver v1.44

ThinkPad Power Manager v1.40

The quality of the dozens of ThinkVantage applications, drivers and services is pretty abysmal now.  Do they only do pre-release testing on Vista now, or what?

[ranjanv]

I have this error as well on my Lenovo X300.  Power Manager 1.40 too!

My laptop rebooted itself suddenly - Could this error have been a possible cause?

[Jason404]

Does your X300 have XP or Vista installed?

I have an X31, so this does not seem to be a problem wit any particular ThinkPads.  It seems to be a problem with Power Manager v1.40.

[ranjanv]

My laptop is on XP....what problems did you face along with this error?

[Jason404]

Everybody in this thread seems to be using XP, so it is probably not a when using Vista.

It does not seem to cause any noticable problems, but obviously something i wrong.  Seeing dozens of these errors in Event Viewer just does not inspire confidence.  I want to be assured that my laptop is running without issues.

[Kaz]

Same here. Installed 1.40 this afternoon and immediately starting seeing the same events. I find it interesting that it is not model dependent. OS dependent, perhaps. I too have Win XP, SP3. This is certainly a frustrating encounter. Surely, Lenovo should have been able to test for this event before rolling out the driver, wouldn't you think? Have not experienced an issue yet; I suppose time will tell. Does anyone else have the Atheros a/b/g/n/ wireless adapter and driver shown below?

Atheros driver 6.0.3.94 (6/26/07) for 11 a/b/g/n Wireless Lan Mini-PCI Express Adapter

[Jason404]

I have Atheros Driver 4.1.2.156 (02/05/07) for 11a/b/g Wireless LAN Mini PCI Adapter.

Why do you ask?  Do you think that this is related to this issue?

[Kaz]

To be honest, after I asked the question, I realized that it did not make sense. Rolling back to the previous software rev. eliminates the event errors so obviously a bug introduced in the latest version. Sorry.

Message Edited by Kaz on 08-16-2008 04:03 PM