Log Service Container Limit Hit: 0X000019D9 Fix

1. Event Log Full – The Simple Fix

I've seen this pop up mostly on Windows Server 2016 and 2019 boxes that have been running without log maintenance for months. A client last month had a terminal server where the Security log had over 20,000 containers – the default limit is 16,384. The error hit during a routine backup script that tried to write to the Application log.

First thing to try: clear the overflowing event log. Don't delete the log file – you'll lose permissions. Instead, use the Event Viewer GUI or PowerShell.

GUI Method

1. Open Event Viewer (eventvwr.msc)
2. Expand Windows Logs, right-click the log showing the error (likely Application, Security, or System)
3. Select Clear Log…
4. Choose Save and Clear if you need the history, otherwise just clear it

PowerShell Method

Clear-EventLog -LogName Application
# or for Security log:
Clear-EventLog -LogName Security
# or clear all at once:
Get-EventLog -LogName * | ForEach { Clear-EventLog $_.Log }

That usually kills the error immediately. But if you don't fix the underlying container size, it'll come back in a few weeks.

2. Log Size Limit Too Low – The Real Fix

The default max log size for Application and System logs on older servers is 20MB. That's tiny. A busy domain controller can fill that in a day. The container count limit is directly tied to that size – more containers = more space, but the OS caps the count at about 16,384 containers per log file.

Increase the max log size to 100MB or even 256MB. This reduces how often you hit the container limit because the OS can allocate fewer, larger containers.

Via Event Viewer:

1. Right-click the log, go to Properties
2. Under Log maximum size, increase it (I set Application and System to 102400 KB, Security to 204800 KB)
3. Select Overwrite events as needed – don't use "Do not overwrite" or you'll get log full errors

Via PowerShell (one-liner):

Limit-EventLog -LogName Application -MaximumSize 102400KB
Limit-EventLog -LogName Security -MaximumSize 204800KB
Limit-EventLog -LogName System -MaximumSize 102400KB

After changing the size, clear the log once more to flush the old container structure. I've never had this error come back after that.

3. Registry Corruption or Third-Party Interference

This one's rarer but nasty. Some backup software (I'm looking at you, legacy NetBackup agents) or dodgy log shippers can create log containers directly without going through the normal API. This bloats the container count without increasing the size.

You'll see the error on the System log even if the Application log is barely half full. Here's the fix:

1. Open Regedit
2. Go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EventLog\<LogName>
3. Delete the File value – yes, this nukes the current log file. The OS recreates it on the next boot.
4. Reboot the server

Warning: This deletes ALL events. If you need compliance, export the log first using wevtutil epl <LogName> backup.evtx.

Last time I did this, it was on a Windows Server 2012 R2 box that had been running a custom log parser from a vendor. After the registry fix, the error never reappeared.

Quick Reference Table

Bottom line: bump the log size to 100MB and clear it once. You'll never see 0X000019D9 again unless someone's running bad third-party code.