Forum Discussion
WinHTTP Proxy Service Stopping on Server 2019
I am having an issue with a few of our Windows server 2019 VMs. Every week weeks one of the boxes would suddenly be unable to send HTTP requests. Upon further investigations into the Event Viewer, ...
You're facing an issue with the WinHTTP Proxy Service on your https://www.laptopicker.com/04-best-laptops-with-ethernet-port/ 2019 VMs. The service stops, causing HTTP request failures. The error message suggests a problem with the endpoint mapper database entry. Restarting the VM temporarily resolves the issue, but it's not ideal for 24/7 products. Ensure VMs are updated, try alternative methods to restart the service, and consider contacting Microsoft support for assistance. Implement monitoring to respond promptly. Resolving this issue requires further investigation and contacting support.
This is a known error that Microsoft does not intend to fix. It only effects 2019.
If it doesn't contact a website at least every 27 minutes, the WinHTTP Web Proxy Auto-Discovery Service will stop. Each time it starts up again it creates a new endpoint, which causes it to eventually run out of endpoints, then flood the event log with "The endpoint mapper database entry could not be created" messages.
To prevent it from happening we created a scheduled task that runs every 15 minutes and executes this command, so that the service doesn't ever stop.
"Powershell.exe -NoProfile -NonInteractive -Command "try { Invoke-WebRequest 'http://<Insert_website_to_contact_here>' -ErrorAction Stop } catch { Write-EventLog -LogName Application -Source WSH -EventId 0 -EntryType Information -Message 'The keep-alive task for WinHTTP Web Proxy Auto-Discovery Service failed to contact a website.' }"
If it doesn't contact a website at least every 27 minutes, the WinHTTP Web Proxy Auto-Discovery Service will stop. Each time it starts up again it creates a new endpoint, which causes it to eventually run out of endpoints, then flood the event log with "The endpoint mapper database entry could not be created" messages.
To prevent it from happening we created a scheduled task that runs every 15 minutes and executes this command, so that the service doesn't ever stop.
"Powershell.exe -NoProfile -NonInteractive -Command "try { Invoke-WebRequest 'http://<Insert_website_to_contact_here>' -ErrorAction Stop } catch { Write-EventLog -LogName Application -Source WSH -EventId 0 -EntryType Information -Message 'The keep-alive task for WinHTTP Web Proxy Auto-Discovery Service failed to contact a website.' }"