Jun 23 2021 09:54 AM
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, we found this entry around the start of the issue.
The WinHTTP Web Proxy Auto-Discovery Service service terminated with the following service-specific error:
The endpoint mapper database entry could not be created.
Has anyone ever had this issue or knows a fix?
We need to restart the VM for it to rectify as the WinHTTP Service refuses to start using the services control panel. The services on those box support 24/7 products and we don't have anyone on call to restart the box at a moments notice.
Jun 23 2021 10:09 AM
Jun 23 2021 11:44 AM
Scan didn't find any integrity violations
Jun 23 2021 12:26 PM
Apr 24 2022 01:38 AM
Hi @DylanDD13
I am recently getting the same issue on my computer. After that, I tried to run the command - netsh winhttp reset proxy to reset the proxy. (Refer to guide here)
It will reset your proxies and caches and your problem will most probably be fixed. However, If your problem is still not fixed then you can try this method.
Open your browser and go to its proxy section. This step might vary from browser to browser, In most of cases, it is Google Chrome Browser.
Enter this URL on Google Chrome - chrome://net-internals/#proxy
After that Reset and select "use system proxies" and it will start working again.
Hopefully, this will give you an answer to your problem. Thanks!!
Oct 03 2022 08:18 PM
There might be windows update error that might be causing issue you can try updating the system.
Oct 07 2022 06:30 AM
Hello DylanDD13,
WinHTTP Web Proxy Auto-Discovery is a Win32 service. It provides support for auto-discovering a proxy configuration by implementing the Web Proxy Auto-Discovery (WPAD) protocol.
If the WinHTTP Proxy Service Stops and throws an error, "The endpoint mapper database entry could not be created." then you can follow the steps below to troubleshoot the issue.
Boot the system in safe mode with networking:
Booting your computer in Safe Mode with Networking forces your computer to load with only the essential drivers and services.
Thus, you can launch programs, browsers and download files from the desktop to fix any issues you might have. You can simply restart the system from safe mode to return to normal mode.
Perform a clean boot in the Windows server:
A "clean boot" starts Windows with only essential drivers and programs to diagnose problems.
Note: After restarting the server, you'll have a clean boot environment. You must restore the system with changes made after completing your troubleshooting.
Check and Repair System Files:
You will have to scan all protected system files to review for any corrupted files on your system.
SFC /scannow
Note: You will have to wait until the process complete
If you get an error message containing corrupted files, then remove the corrupted files.
I hope the above ways help you to troubleshoot the issue and that WinHTTP Proxy Service starts without facing any errors.
-------------------------
Regards,
Austin_M
Mar 15 2023 09:08 AM
Yes i have the same issue. We tried completely re-installing the vm from scratch. Doesn't help. After a few weeks the Win HTTP proxy service breaks down.
This ONLY happens on this one VM.
It's only running IIS with two websites. One of the websites uses Microsoft Identity provider for azure SSO and this stops working. Everything else for both websites work fine.
NONE of the "fixes" written in this topic works. The worst advise is the one given about running a "safe boot".. COME on.. Microsoft just fix this **bleep** issue which has been present since the beginning of time and stops CRUCIAL web services from working!!!!
One might almost come to believe they made this problem on purpose to get people to use Azure hosting instead.