EPT_S_CANT_CREATE (0X0000076B) Error Fixed on Windows Server

I know this error can make you want to throw your keyboard across the room. The endpoint mapper database entry could not be created — that's a mouthful of frustration. I've seen this on Windows Server 2012 R2, 2016, 2019, and even 2022. It usually pops up when an application tries to register itself in DCOM or RPC, and the system refuses. Let me save you the headache.

First, Check the RPC Service

Nine times out of ten, the Remote Procedure Call (RPC) service is either stopped or set to manual when it should be running. Here's what to do:

1. Hit Win + R, type services.msc, and press Enter.
2. Scroll to Remote Procedure Call (RPC). It should show Running and Automatic.
3. If it's stopped, right-click it and select Start. Then open its Properties and set Startup type to Automatic.

While you're there, check RPC Endpoint Mapper and DCOM Server Process Launcher — both should also be Running and Automatic. These three services work together. If one's missing, you get the error.

The Real Fix: DCOM Permissions

If the services are fine, the problem is almost always DCOM permissions. Windows restricts who can create endpoints in the endpoint mapper. The default built-in groups (like Everyone or Authenticated Users) sometimes don't have the right privileges.

Open Component Services (run dcomcnfg from Start). Go to Console Root > Component Services > Computers > My Computer. Right-click My Computer, choose Properties, then the COM Security tab.

Under Access Permissions, click Edit Default. Make sure Everyone has Remote Access and Remote Launch checked. Under Launch and Activation Permissions, click Edit Default and ensure Everyone has Remote Launch and Remote Activation. Apply and restart the RPC service.

That's the fix that has worked on every Server 2016 box I've touched. I've seen admins spend hours on firewall settings when it was just a missing permission.

Why This Works

The endpoint mapper is a part of RPC that maps unique identifiers (UUIDs) to network endpoints like TCP ports or named pipes. When an application tries to register its endpoint, DCOM checks if the caller has the right to create a new entry. If the default permissions were tightened (often by security policies or a GPO), the creation fails. By giving Everyone those permissions, you're telling Windows "yes, let any authenticated user register endpoints." It's not a security hole — it's restoring the default behavior.

Less Common Variations

If the permissions fix doesn't do it, check these:

• Firewall blocking RPC: Windows Firewall with Advanced Settings. Look for the inbound rule Remote Volume Management or Remote Service Management — these use RPC. If they're disabled, enable them. Also check that TCP port 135 is allowed inbound.
• Corrupt RPC registry keys: Rare, but it happens. Back up the registry first, then navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc and check that the Internet key has a value Ports with a range like 5000-6000. If missing, create it (REG_MULTI_SZ) and set to 5000-6000.
• Application-specific issues: I've seen this error when a misconfigured MSDTC (Distributed Transaction Coordinator) tried to register. Check your application's event log for specific DCOM error IDs. Sometimes the app just needs to be reinstalled or updated.

Prevention

To stop this from coming back, lock down those DCOM permissions more carefully. Instead of Everyone, use Authenticated Users — that covers domain users and machine accounts without exposing to anonymous. Also, set a GPO to enforce Restrict Remote RPC Connections to only your trusted subnets. And please, don't turn off the firewall entirely — I've seen that mistake too often.

If you're managing a cluster or high-availability setup, make sure all nodes have identical DCOM permissions and RPC service states. A mismatch across nodes is a classic source of this error failing over.