We're experiencing random but fairly frequent (5-10 a day) crashes in the hwc.exe file. I've capture some of the details from the Windows event logs at https://gist.github.com/amhuber/d4c59ca3e42d19b7b44fe9288ea9cae8. These are apps that have been running for some time using the binary_buildpack and are seeing the crashes after moving to hwc_buildpack. From the CF side the errors look like:

App instance exited with guid efefaa8f-1b71-4654-9e5c-2186845cae0f payload: {"instance"=>"402b9783-eb18-46d4-542d-8f1c660ad285", "index"=>2, "reason"=>"CRASHED", "exit_description"=>"2 error(s) occurred:\n\n* Exited with status -1073741571\n* cancelled", "crash_count"=>1, "crash_timestamp"=>1496251511896170785, "version"=>"c127b9a6-8658-43db-afa2-2c8211cea06a"}

Any ideas on what we can do to help troubleshoot the overflow errors?

Aaron

This typically isn't something to worry about outside development since hwc.exe is typically only used from CloudFoundry which does a healthcheck for each app, but just in case...

1. Standup clean Windows box without IIS or HWC installed. I'm using Windows 10 here, but other OSs likely exhibit similar behavior.
2. Install Web-WHC feature
3. Start a web application, e.g. & { $env:PORT=8080; .\hwc.exe -appRootPath "C:\containerizer\env\ViewEnvironment\" }

The stdout from hwc.exe displays something like:

Server Started for 41bd1a07-0909-41f1-9157-423a9e95cc14

However when browsing the site on port 8080, the browser cannot connect to the site. Looking at the Windows Application Event Log you'll notice a few errors:

The worker process failed to initialize correctly and therefore could not be started.  The data is the error.
The Module DLL C:\Windows\System32\inetsrv\validcfg.dll failed to load.  The data is the error.

Installing the IIS ASP.NET 4.6 feature along with it's dependencies and then restarting the hwc.exe produces a slightly different set of errors:

The worker process failed to initialize correctly and therefore could not be started.  The data is the error.
The Module DLL C:\Windows\System32\inetsrv\iiswsock.dll failed to load.  The data is the error.

Installing the WebSocket Protocol feature and restarting the hwc.exe process now properly starts the web server. There is a warning logged, but it the web server does work properly.

The directory specified for caching compressed content C:\Users\vagrant\tmp\IIS Temporary Compressed Files\AppPool9000 is invalid.  Static compression is being disabled.

The following warning is observed in the Windows Application event log when an hwc process is started:

The directory specified for caching compressed content C:\Users\vagrant\tmp\IIS Temporary Compressed Files\AppPool8023 is invalid.  Static compression is being disabled.

This definitely happens locally outside Cloud Foundry, but I'm pretty certain I've seen this warning on a Windows cell before.

Hi,
I am new to CF and .net Core, I am trying to run Asp.net Core application on PCF. I have PCF environment with windows stack,and hwc also available in build pack.I am deploying application with following command

• cf push -s windows2012R2

I have added web.config file also add some default configuration. Application deployed and Instance also running, however application is not responding it is throwing 500 error(The page cannot be displayed because an internal server error has occurred.). on deployed application we can see buildpack PCF console application detected build pack automatically.
please let me know if i missed any configuration or start command to use HWC or any server url :port settings i have to do.
Also guide me on how I can start and configure HWC build pack asp.net core application.

Help much appreciated!!

Thanks,
Abhijit Patil.

Background:
We have migrated some legacy .net project. These projects could be running in IIS with enable32BitAppOnWin64 set to "true" for the iis pool.

But in hwc_buildpack, it is not working for these project. And hwc_build pack use this hwc project.
As I know this hwc project invoke the hosted web core with applicationHost.config, I checked the code as below:

If possbile this could be solved as below"

Looking forward to your response. :）

Thanks
David