Home > Event Id > Event Id 4609 Eventsystemobj.cpp

Event Id 4609 Eventsystemobj.cpp

HRESULT was 8007043c from line 45 of d:\rtm\com\complus\src\events\tier1\eventsystemobj.cpp. Well, I tried this when the first error occured, but it was no help... Please contact Microsoft Product Support Services to report this error. The COM+ Events service maintains the list of interested subscribers who receive the calls and directs those calls without requiring the knowledge of the publisher. Check This Out

These errors are getting more frequent. Stats Reported 7 years ago 0 Comments 12,880 Views Other sources for 4609 Microsoft-Windows-EventSystem Others from EventSystem 4356 4627 4354 4625 4614 4622 4097 4621 See More IT's easier with help Options are narrowing. 01-05-2012, 03:03 AM #14 kortmann Registered Member Join Date: Mar 2011 Location: E. The content you requested has been removed.

so can i proceed in the procedure ? Did run the Mini Tool Box once before and I think I posted it above. Starting Norton Ghost 2003 resulted in a dialog box with the message: "Couldn't contact Ghost Start Agent. (0x80070005)". Thanks, Barb Reinhardt Barb Reinhardt, Aug 10, 2006 #1 Advertisements R.

  • Let us know.
  • No such interface supported # ---------------------------------- # Interface IP Configuration # ---------------------------------- pushd interface ip # Interface IP Configuration for "Wireless Network Connection 11" set address name="Wireless Network Connection 11"
  • To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.
  • THe support center isn't helping. >>> >>> Thanks, >>> >>> Barb Reinhardt Wesley Vogel, Aug 11, 2006 #7 Advertisements Show Ignored Content Want to reply to this thread or ask
  • HRESULT was 8007043c from line 45 of d:\vista_gdr\com\complus\src\events\tier1\eventsystemobj.cpp.
  • It started when a scanner popped up and kindly offered to find and delete viruses on my computer.
  • Username Forum Password I've forgotten my password Remember me This is not recommended for shared computers Sign in anonymously Don't add me to the active users list Privacy Policy
  • I bought a 2 year extended warranty,so I guess that is OK, but it's a lot of hassle, especially if it turnsout that the problem -is- the Windows installation....Cheers,Geoff-- barrow_52 AnonymousJul
  • Call it solved (knock on wood).
  • Please contact Microsoft Product Support Services to report this error.
  • Error: (12/24/2013 08:53:30 AM) (Source: DCOM) (User: ACI) Description: The server {0002DF01-0000-0000-C000-000000000046} did not register with DCOM within the required timeout. Back to top Page 1 of 3 1 2 3 Next Back to Windows XP Home and Professional 0 user(s) are reading this topic 0 members, 0 guests, 0 anonymous users Already had a while some problems updating when my 2K server was not freshly restarted. the computer is an older dell optiplex.

    To do this, on each policy, remove one of the entries (“SERVICE” is probably the best to remove), then press OK to save the changes, and then go back in and Old technology imo. For information about how to contact CSS, see Enterprise Support (http://go.microsoft.com/fwlink/?LinkId=52267). http://www.eventid.net/display-eventid-4609-source-EventSystem-eventno-1993-phase-1.htm Apparently it is a driver issue that doesn't work correctly after SP1 has been installed so I'm guessing that you have SP1 for Vista installed correct?If that is the case open

    this series of BSOD's is occuring on a Windows XP laptop.. To locate your application, click Component Services, click Computers, click My Computer, and then click COM+ Applications. 4. SP4 adds a group policy that, in my case did not include the users as it should have. Hope you can point me in the right direction.

    Login Join Community Windows Events EventSystem Ask Question Answer Questions My Profile ShortcutsDiscussion GroupsFeature RequestsHelp and SupportHow-tosIT Service ProvidersMy QuestionsApp CenterRatings and ReviewsRecent ActivityRecent PostsScript CenterSpiceListsSpiceworks BlogVendor PagesWindows Events Event 4609 Wednesday, July 29, 2009 8:34 PM Reply | Quote 1 Sign in to vote HAVE YOU HAD ANY LUCK?  I RETURNED FROM 2 WEEK VAC WHILE MY LAPTOP REMAINED UNTOUCHED FOR The symptoms are that after SP2 has been installed, and the machine has been rebooted a few times, this error message appears in the Application Event log. Please contact Microsoft Product Support Services to report this error.See if you can get to the bottom of it with this it may indicate where the problem lies.Using Reliability Monitorhttp://technet2.microsoft.com/WindowsVista/en/library/d33c3cc1-a9dd-4b96-8062-edb21ee70f0e1033.mspx?mfr=trueUse Reliability

    I checked Event Viewer and found this in “Application”: Event ID: 4609 Date: 12/30/2011 Time: 7:05:22 PM User: N/A Computer: HOME Description: The COM+ Event System detected a bad return code http://supportcanonprinter.com/event-id/event-viewer-event-id-list.html See Error code 0x800706BF for more details. Please contact >> Microsoft Product Support Services to report this error. >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> >> How do I fix it. Is relating to SP1 for Vista.

    Similar Threads COM+ Event System detected a bad return code EddyVK, Oct 6, 2003, in forum: Windows XP General Replies: 0 Views: 370 EddyVK Oct 6, 2003 COM+ Event System detected The COM+ Event System service supports system event notification for COM+ components, which provides automatic distribution of events to subscribing COM components. If it works in new user account, then the other user should be a corrupted. this contact form Also have speccy installed and ran it but will do it as you suggest.

    This appearsto be indicating that the problem may be a -hardware- fault, and nothingto do with Windows. Let us know. > > Wes > MS-MVP Windows Shell/User > > In news:OM7$, > Barb Reinhardt <> hunted and pecked: >> THis is the error message I'm getting >> >> This just didn't strike me as a problem that would require that drastic a solution.

    Note If you have MS04-012 installed, you must now re-install MS04-012.

    By creating an account, you're agreeing to our Terms of Use, Privacy Policy and to receive emails from Spiceworks. Attached is a error log too. Email Reset Password Cancel Need to recover your Spiceworks IT Desktop password? Thank you again for your assistance.

    Please contact >> Microsoft Product Support Services to report this error. >> >> For more information, see Help and Support Center at >> http://go.microsoft.com/fwlink/events.asp. >> >> How do I fix it. I opened task manager and found that services.exe was running up my CPU. I have tried this solution, which unfortunately did not help. navigate here Toshiba laptop not powering on » Site Navigation » Forum> User CP> FAQ> Support.Me> Steam Error 118>> Trusteer Endpoint Protection All times are GMT -7.

    Fortunately, it seems to be quite easy to fix. Can't forward ports... Texas Posts: 106 OS: XP Home SP3 My System Couple of questions. After that, all worked well for me and I had no more problems with the 4 systems I was working with.

    COM technologies include COM+, DCOM, and ActiveX Controls. Get the answer AnonymousJul 3, 2005, 12:55 AM Archived from groups: microsoft.public.windowsxp.security_admin (More info?)Christopher Hill Wrote: > Hi,> > Did you try the fix I mentioned in my second post? Hello.. The only thing is that the first instruction to delete the ~Clbcatq.dll file returned the message that no file by that name was found.

    Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More... Reply Mrfreddy says: 6 July 2009 at 16:15 Log Name: Application Source: Microsoft-Windows-EventSystem Date: 7/6/2009 3:24:56 PM Event ID: 4609 Task Category: Event System Level: Error Keywords: Classic User: N/A Computer: Very liitle information on my particular error code - followed these instructions and problem resolved - took 3 minutes to sort what has been a nagging problem for several months.