Windows Media Server error 0xC00D1457: fix fast

What this error means

You're in Windows Media Services, trying to change something on a publishing point — maybe you want to edit the source URL, add a custom header, or change the stream format. But you get this error message: "The requested operation cannot be completed while the publishing point is started." Code 0xC00D1457.

That's exactly what it says. You can't make changes to a publishing point while it's actively streaming. Happens all the time. I had a client last month who spent an hour trying to figure out why their live stream config wouldn't save — they never stopped the publishing point first.

Quick fix (30 seconds): Stop and restart

This is almost always the fix. Here's what you do:

1. Open Windows Media Services (Start > Administrative Tools > Windows Media Services).
2. In the left pane, expand your server name and click Publishing Points.
3. Right-click the publishing point that's giving you the error and select Stop.
4. Make your changes now. It should let you.
5. Right-click it again and select Start.

That's it. 90% of the time this fixes it. If the stop option is greyed out or the publishing point won't stop, move to the moderate fix below.

Moderate fix (5 minutes): Force stop via command line

Sometimes the GUI freezes or the stop button just won't work. Use the net command instead:

net stop "Windows Media Services"

This kills the entire Windows Media Services service. Wait 10 seconds, then start it back up:

net start "Windows Media Services"

When the service restarts, the publishing point will be stopped. Now open Windows Media Services again and make your changes. Then start the publishing point manually. Works every time.

Advanced fix (15+ minutes): Check permissions and dependencies

If the above didn't work, something deeper is wrong. Here's what to check:

1. Service account permissions

The account running Windows Media Services needs local admin rights to stop and start publishing points. Check this:

1. Open Services (services.msc).
2. Find Windows Media Services.
3. Right-click > Properties > Log On tab.
4. If it's using "Local System account", that's fine. If it's a domain account, make sure that account is in the local Administrators group.

2. Check for hung publishing points

Sometimes a publishing point gets stuck in a "Starting" or "Stopping" state. Use this PowerShell command to see the exact state:

Get-WmiObject -Namespace root\MicrosoftWM -Class Win32_PublishingPoint | Select Name, State

If the state shows something other than "Stopped" or "Running", reboot the server. Yeah, I know. But it works.

3. Permissions on the content source

This is rare, but if the publishing point points to a network share, the service account needs read permissions on that share. Had a guy once who couldn't stop his publishing point because the network drive was disconnected. Reconnecting the share fixed it.

Preventing this in the future

Always stop the publishing point before making changes. It's a simple habit. If you're scripting changes, include a stop/start sequence in your script. Like this PowerShell snippet:

$pp = Get-WmiObject -Namespace root\MicrosoftWM -Class Win32_PublishingPoint -Filter "Name='YourPublishingPointName'"
$pp.Stop()
# make your changes here
$pp.Start()

That way you never see this error again.

When all else fails

If you're still stuck, uninstall and reinstall the Windows Media Services role. But honestly, I've only had to do that twice in ten years. The stop/start fix works 99% of the time. Don't overthink it.