| Event Id | 10000 |
| Source | DCOM |
| Description | Description: 1.Unable to start a DCOM Server: %3. The error:"%%%2" Happened while starting this command: %1 2. The server <Code> did not register with DCOM within the required timeout. |
| Event Information | The application might have been moved or deleted.
Check that the application is present and installed properly. According to Microsoft: CAUSE: In some situations, when the first 16-bit program to be run in the current users logon session is invoked using COM, the system may create a new or additional Windows NT Virtual DOS Machine (NTVDM) that runs in the local systems security context, instead of in the security context of the logged-on user. Local system does not have the required permissions to load the form, and the error message is displayed. RESOLUTION: Ensure that the Wowexec tool (Wowexec.exe) is running in the context of the logged-on user before you attempt to load a 16-bit form, using either of the following methods: • Click Start, click Run, type wowexec.exe, and then click OK. • Run Wowexec.exe from the users logon script. |
| Reference Links | Unable to Open 16-Bit Exchange EFD Form Using Outlook 97 in a Terminal Server Client Window Unable to Activate a DCOM Server from a Terminal Server Client Session Event ID 10000 - Unable to start a DCOM Server Unable to start a DCOM Server Windows Operating System (DCOM) |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.