N
needlove
Here's the event:
Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4354
Date: 2/25/2006
Time: 10:42:05 AM
User: N/A
Computer: OWNER
Description:
The COM+ Event System failed to fire the DisplayLock method on subscription
{B6EEAA4F-D713-4CF2-B798-4D03E8B8FE59}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.
The subscriber returned HRESULT 80004001.
B6EEAA4F-D713-4CF2-B798-4D03E8B8FE59 is Boink software that manages various
scientific projects that use my spare CPU processing capabilities. It runs
24/7. Nothing stood out in the boink logs that corresponded with the times
of the events. Event occurs 2-3 times a day.
I recenty started with the BBC climate prediction project, using their
version of Boink, and transfering my other projects to the new client. The
new boink client offered a screensaver option but I chose "no" when it was
installing. I recently updated from windows update. The error started
recently.
I have tried the reinstalling windows components method with no luck.
I'll stop the download of new work units and finish off the old ones then
reinstall the client unless somebody has a better idea.
Event Type: Warning
Event Source: EventSystem
Event Category: (52)
Event ID: 4354
Date: 2/25/2006
Time: 10:42:05 AM
User: N/A
Computer: OWNER
Description:
The COM+ Event System failed to fire the DisplayLock method on subscription
{B6EEAA4F-D713-4CF2-B798-4D03E8B8FE59}-{00000000-0000-0000-0000-000000000000}-{00000000-0000-0000-0000-000000000000}.
The subscriber returned HRESULT 80004001.
B6EEAA4F-D713-4CF2-B798-4D03E8B8FE59 is Boink software that manages various
scientific projects that use my spare CPU processing capabilities. It runs
24/7. Nothing stood out in the boink logs that corresponded with the times
of the events. Event occurs 2-3 times a day.
I recenty started with the BBC climate prediction project, using their
version of Boink, and transfering my other projects to the new client. The
new boink client offered a screensaver option but I chose "no" when it was
installing. I recently updated from windows update. The error started
recently.
I have tried the reinstalling windows components method with no luck.
I'll stop the download of new work units and finish off the old ones then
reinstall the client unless somebody has a better idea.