Something had added ACL entries for ports 10000-10002 that were conflicting with my web project, which was trying to run on port 10000 using IISExpress. Then I ran netsh http delete urlacl url= and IISExpress started working again.
![azure storage emulator failed to initialize azure storage emulator failed to initialize](https://user-images.githubusercontent.com/10958000/40836819-171b0782-6590-11e8-8590-2a40e8ebeb3b.png)
![azure storage emulator failed to initialize azure storage emulator failed to initialize](https://i.stack.imgur.com/hK7Qd.png)
Where did these come from? I ran netsh http delete urlacl url= and removed the entry and confirmed IISExpress stopped working. Amazingly, the command worked! Although I was happy, I was also disappointed that I wouldn’t be able to see what the value was previously so I could find out the root cause.Īnd that displayed a bunch of entries that included these as well (User and SDDL changed): I’d only ever used NETSH maybe once or twice for some obscure reason, but the inclusion of “ACL” in the command was encouraging. In a comment on one of the web posts that I read, I saw this command: And IIS would work for any other project on seemingly any other port. So IIS would work on port 8085 but IISExpress would not work on port 10000. An IISRESET resolved that problem and I was able to browse to the web project using IIS. Oddly, my new websites and application pools didn’t refresh after being created, which led me to think there was even more wrong with my workstation. While doing so, I set up a new website in IIS on port 8085. That lead me down a totally different troubleshooting path. The data field contains the error number.ĮventID 2276: The worker process failed to initialize correctly and therefore could not be started. IISExpress was logging these two events:Įvent ID: 2269: The worker process for app pool ‘Clr4IntegratedAppPool’, PID=’7536′, failed to initialize the http.sys communication when asked to start processing http requests and therefore will be considered ill by W3SVC and terminated.
#AZURE STORAGE EMULATOR FAILED TO INITIALIZE WINDOWS#
Then, late as usual, I finally remembered the Windows Event Viewer. At this point, I was the only developer in my team who had a single web project that wouldn’t launch. I tried other web projects in the solution. I tried an older iteration of the web application. I read many potential solutions, some as crazy as not being able to use a user name with “bg” in it. I checked my *.config files in Documents\IISExpress over and over. The only thing I had done that morning was use Disk Cleanup to delete all my temp files and archived error reports.
![azure storage emulator failed to initialize azure storage emulator failed to initialize](https://miro.medium.com/max/782/1*ZWVSdv_73rWjRKpFEQvXcQ.png)
I was an administrator on the local machine, so that didn’t make any sense. IISExpress would operate just fine when run as Administrator, but not as my normal user. I started down the obvious track of checking permissions. The error reported was:įailed to register URL " for site "Portal3" application "/". When I would launch a web project from Visual Studio, IIS Express would fail to load. Today, I spent my entire work day trying to find the solution to this error.