The endpoint mapper on Windows 2019 Servers is running out of available endpoints, causing it to block outbound HTTP requests. You’ll notice this issue when the WinHTTP Proxy service fails to start, displaying an 1899 error indicating that the “endpoint mapper database entry could not be created.” Attempting to access the proxy settings will also hang the window, requiring a force-close.
Before the HTTP requests start getting blocked, you’ll see 7024 events in the event log related to the WinHTTP Proxy service failing. The full error message reads:
“The WinHTTP Web Proxy Auto-Discovery Service service terminated with the following service-specific error: The endpoint mapper database entry could not be created.”
This issue seems to have started occurring after migration from VMware to Hyper-V and appears to only affect Windows 2019 VMs.
To work around this problem, you’ve implemented a reboot policy using RMM (Remote Monitoring and Management) tool. The policy schedules a reboot when it detects these events starting to occur.
Possible solutions to consider:
- Check for any available updates or hotfixes from Microsoft that address this specific issue on Windows 2019 servers running on Hyper-V.
- Review Hyper-V configuration settings and compare them to best practices to ensure optimal performance and stability.
- Monitor the endpoint mapper’s resource usage and investigate any potential resource leaks or excessive consumption by applications or services.
- Consider adjusting the reboot policy to find the right balance between maintaining system stability and minimizing downtime.
It’s crucial to identify the root cause of the endpoint mapper exhaustion to implement a permanent solution. Engage with Microsoft support or consult with Hyper-V expert to dive deeper into the issue and find a suitable resolution.