"Server" in this context does not refer to a Windows OS server but rather to a "server" COM component (to which "client" components connect). There could be many reasons for a component to fail to execute. To name a few:
- improper configuration
- corrupted files
- mismatched dlls
- security problems (user rights, file permissions)
- lack of resources
A botched upgrade may be one reason to get this problem.
As per Microsoft, in many instances, these errors appear because the server-side code is running without a user profile or the user identity that is specified for the launching context does not have proper DCOM permissions. So, if possible, verify that from a security point of view, there are no issues with the application (i.e. service accounts, user profiles, DCOM permissions).
Given to vast number of potential reason, it is not easy to troubleshoot this issue. Look for additional clues, (re)install the latest service packs or hotfixes.
Symbolic name: CO_E_SERVER_EXEC_FAILURE
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.