Results 1 to 2 of 2

Thread: Could not start the DCOM Server Process Launcher

  1. #1
    Join Date
    Oct 2004
    Posts
    19

    Could not start the DCOM Server Process Launcher

    Facing some problems on my Windows XP system. Due to some reason I need to use installshield but it first requires DCOM process to be started, when I try to start the same , it ends up with an error message saying:

    “Could not start the DCOM Server Process Launcher service on Local Computer.
    Error 1053: The service did not respond to the start or control request in a timely fashion.”


    As far as I know DCOM process is not associated with some other services as it has no dependenciesThen why is it not getting started and giving me error? Please help.

  2. #2
    Join Date
    Jul 2004
    Posts
    109

    Re: Could not start the DCOM Server Process Launcher

    Most probably it could be due to Service startup failure or either corrupt system files, or a driver conflict. So i will suggest you to better try repairing repair all system files.

    You can do this by going to Start/Run, and type (or paste in):

    SFC /SCANNOW

Similar Threads

  1. Replies: 2
    Last Post: 20-10-2011, 04:47 PM
  2. Missing DCOM Server Process Launcher entry
    By Shiverer in forum Windows XP Support
    Replies: 8
    Last Post: 21-06-2011, 11:35 PM
  3. DCOM server process launcher terminated unexpectedly
    By santoshgondkar in forum Windows XP Support
    Replies: 4
    Last Post: 31-01-2010, 11:01 AM
  4. DCOM Server Process Launcher terminates unexpectedly
    By jonzy28 in forum Operating Systems
    Replies: 3
    Last Post: 30-01-2010, 11:33 PM
  5. DCOM server process launcher service terminated unexpectedly
    By Billie in forum Windows XP Support
    Replies: 3
    Last Post: 30-05-2008, 12:49 AM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,713,521,531.31692 seconds with 17 queries