DCOM got error “The service cannot be started,

either because it is disabled or because it has no enabled devices associated with it. 
´Attempting to start the service StiSvc with arguments´" in order to run the server A1F4E726-8CF1-11D1-BF92-0060081ED811
EventID: 10005
Possible Solutions
just the lack of Windows updates
----------------------------------------

Check the Windows Image Acquisition (WIA) service, make sure it is set to manual or automatic. This service is required by many imaging utilities.

----------------------------------------

In my case, the error message was "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." and I got it while attempting to start the  wuauserv (Windows Update) service.
So, if you have the SAME error for the SAME service, then this might be caused by the Automatic Updates Service being disabled or if the .dll files needed for Automatic Update need to be registered. Just run the following commands to register the .dll files and the service will also be set to automatic:
REGSVR32 %windir%\system32\wuapi.dll
REGSVR32 %windir%\system32\wuaueng1.dll
REGSVR32 %windir%\system32\wuaueng.dll
REGSVR32 %windir%\system32\wucltui.dll
REGSVR32 %windir%\system32\wups.dll
REGSVR32 %windir%\system32\Wuauserv.dll
However, if the Automatic Updates Service is disabled on purpose (i.e. through GPO or otherwise), then this error message can be ignored. 

============================

Source

DCOM got error "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service IISADMIN with arguments "" in order to run the server:
{A9E69610-B80D-11D0-B9B9-00A0C922E750}
More information

DCOM got error ' 58' attempting to start the service StiSvc with arguments '' in order to run the server:A1F4E726-8CF1-11D1-BF92-0060081ED811
More information
 
DCOM got error ' 58' attempting to start the service gusvc with arguments '' in order to run the server:89DAE4CD-9F17-4980-902A-99BA84A8F5C8
More information

DCOM got error ' 58' attempting to start the service gusvc with arguments '' in order to run the server:89DAE4CD-9F17-4980-902A-99BA84A8F5C8

=============================

Source (Read more solutons at source) 

the "System Event Notification" service was disabled. I enabled it and that fixed the problem. 

-------------------------------------------

As per Microsoft: "These error messages are generated because another application, such as Microsoft Transaction Server, has already started the Dcom (the Distributed Component Object Model) Service. These messages do not indicate an actual problem and are benign." The recommended solution is to install the latest Service Pack

Error: "The Dependency Service does not exist or has been marked for deletion" Attempting to start the service IIS Admin with arguments " " in order to run the server: (a9e69610-b80d-11d0-b9b9-00a0c922e750) - This is the most common error for this event. There are several instances where this can occur:
The error can be genereated when the Protected Storage, RPC Configuration, or Windows NT LM Security Support Provider is not started, is not installed, or has become corrupt. See M187710 and M189649 for more details.

Another potential cause for this error is that the Windows NT LanManager (NTLM) Security Support Provider service is not installed. See M218458 for more details.

Article M249023 describes this error as showing up after the restart of Microsoft Internet Explorer for the second time during setup and the user logged in using an administrator account is different from the one used to start Internet Explorer Setup.

Error: "An instance of the service is already running." - This is a nonfatal error warning that the IIS service is already started but has not registered a class factory that a Distributed Component Object Model (DCOM) client requires. It should be resolved by the latest service pack. See M193646.

Error: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it." attempting to start the IISAdmin with arguments.". As per M295623 the can be caused if the Microsoft Internet Information Services (IIS) Admin Service is disabled on the computer on which you are trying to install Exchange 2000 Server. Exchange 2000 Server requires the IIS 5.0 services to be running in order to install and function correctly.
Another article that mentions this error is M300319 but this is in fact a failure of MOM (the Microsoft Operations Manager) to load the proper event message file.

Error: "The service did not respond to the start or control request in a timely fashion.", {BA126AD1-2166-11D1-B1D0-00805FC1270E} server - From a newsgroup post, this message start occuring after the installation of Zone Alarm personal firewall). The fix was to start the Zone Alarm after the WWW service (either by a startup script or by making Zone Alarm dependent on the WWW service).

Error: "The service database is locked". One may get this error if an attempt is made to stop/start or otherwise perform some service-related tasks when a server has just started and the systems still performs some of the startup functions in the background thus keeping the services database locked. In this case just wait a couple of minutes for the system to finish its tasks. It could also be that a faulty service installation procedure "locked" the database and in this case a reboot may help. 

---------------------------

Jim Felty
- Error: "The service cannot be started, either because it is disabled or because it has no enabled devices associated with it. " attempting to start the service IISADMIN with arguments "" in order to run the server: {}" - We found that we were getting this error on our SMS 2003 Management Point server after we had changed the management point service from another server to this one. During the change, the IIS Service was disabled on some, but not all of our SMS 2003 Distribution Point servers. There was a 10005 error on the effected Distribution Point server. Enabling and starting the IIS service on the Distribution Point server stopped the errors. 

=============================

http://teldata.wordpress.com/2007/01/20/what-is-stisvc-getting-dcom-error-in-windows-2003-server/