Out of the Box - Problems on IIS 8 #1206

New Issue

fergalmoran · 2025-08-09T17:19:16Z

fergalmoran commented

2025-08-09 17:19:16 +00:00

Originally created by @imukai on 12/6/2016

Edit: Got the main problem of the post, and two additional things below it. If they warrant their own post let me know.

I first tried the VS Template and it worked fine local - started having problems when I published it to my IIS server. So I started fresh with Yeoman and still can't get this thing to work remotely. It still works fine on my local machine.

Note: The main ASP Core MVC App template runs just fine on my server - but I wanted to get my hands dirty with what you have going here.

This relates to IIS 8 on Server 2012, and the Angular2 version of the SPA package.

Here's what I've done after downloaded a fresh copy using yeoman.

Out of the box:

Compiles / Runs locally through VS with zero problems (and I love it)
Added a static file in wwwroot.
Published to IIS via Web Deploy.

Results on IIS:

Serves static file fine.
500 otherwise - not the app's Home/Error. The body of the response contains the Home/Error markup but browser is showing a generic 500 page. Server logs show 500 0 as the error.
Stdout:
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0]
An unhandled exception has occurred: The system cannot find the file specified
Run directly from Kestrel, blows up:
Unhandled Exception: System.AggregateException: One or more errors occurred. (Call to Node module failed with error: Webpack dev middleware failed because of an error while loading 'aspnet-webpack'. Error was: Error: Cannot find module 'aspnet-webpack'

Returned to VS:

Added "node_modules" to project.json under publishOptions/include.
Published to IIS via Web Deploy.

Results on IIS:

Serves static file fine.
500 otherwise. Same as before.
Stdout:
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0]
An unhandled exception has occurred: The system cannot find the file specified
Run directly from Kestrel, blows up:
Unhandled Exception: System.AggregateException: One or more errors occurred. (Call to Node module failed with error: Error: Cannot find module '************\webpack.config.js'
at Function.Module._resolveFilename (module.js:469:15)

Returned to VS:

Added "webpack*.js" to project.json under publishOptions/include
Published to IIS via Web Deploy

Results on IIS:

Serves static file fine.
500 otherwise. Same as before.
Stdout:
fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0]
An unhandled exception has occurred: The system cannot find the file specified
Run directly from Kestrel:
a. some webpack stuff happens
b. error:
ERROR in multi main-client
Module not found: Error: Cannot resolve 'file' or 'directory' ./ClientApp/boot-client.ts in C:***
c. doesn't blow up.

Access site via localhost:5000:

Serves static file fine.
Mostly loads otherwise - the underlying page is there, but has an overlay with the above Error message about the multi main-client.

I spent over 10 hours trying to resolve it thinking the problem was an IIS sub-app issue still, but I guess that's no longer a thing. A couple hours ago I moved it to a top level site and still have issues as outlined above.

Please save me from myself.

Edit: While I am here and waiting to see how to make this work, I noticed the console errors on Local pointing out the extra html and body tags that are being rendered after the app tag. Is this something that needs to be fixed still? It complains about the extra tags.

Edit 2: Also noticed 100s of these per second in Fiddler while this is running locally. Tell me this won't be server calls between client and server in production:

http: localhost:49155/vshub/f1b1ea0776194961a5b01f0fd8d67d8f/DataWarehouseModule/dataWarehouse/getResult/

*Originally created by @imukai on 12/6/2016* Edit: Got the main problem of the post, and two additional things below it. If they warrant their own post let me know. I first tried the VS Template and it worked fine local - started having problems when I published it to my IIS server. So I started fresh with Yeoman and still can't get this thing to work remotely. It still works fine on my local machine. Note: The main ASP Core MVC App template runs just fine on my server - but I wanted to get my hands dirty with what you have going here. This relates to IIS 8 on Server 2012, and the Angular2 version of the SPA package. Here's what I've done after downloaded a fresh copy using yeoman. Out of the box: 1. Compiles / Runs locally through VS with zero problems (and I love it) 2. Added a static file in wwwroot. 3. Published to IIS via Web Deploy. Results on IIS: 1. Serves static file fine. 2. 500 otherwise - not the app's Home/Error. The body of the response contains the Home/Error markup but browser is showing a generic 500 page. Server logs show 500 0 as the error. 3. Stdout: fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0] An unhandled exception has occurred: The system cannot find the file specified 4. Run directly from Kestrel, blows up: Unhandled Exception: System.AggregateException: One or more errors occurred. (Call to Node module failed with error: Webpack dev middleware failed because of an error while loading 'aspnet-webpack'. Error was: Error: Cannot find module 'aspnet-webpack' Returned to VS: 1. Added "node_modules" to project.json under publishOptions/include. 2. Published to IIS via Web Deploy. Results on IIS: 1. Serves static file fine. 2. 500 otherwise. Same as before. 3. Stdout: fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0] An unhandled exception has occurred: The system cannot find the file specified 4. Run directly from Kestrel, blows up: Unhandled Exception: System.AggregateException: One or more errors occurred. (Call to Node module failed with error: Error: Cannot find module '************\webpack.config.js' at Function.Module._resolveFilename (module.js:469:15) Returned to VS: 1. Added "webpack*.js" to project.json under publishOptions/include 2. Published to IIS via Web Deploy Results on IIS: 1. Serves static file fine. 2. 500 otherwise. Same as before. 3. Stdout: fail: Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware[0] An unhandled exception has occurred: The system cannot find the file specified 4. Run directly from Kestrel: a. some webpack stuff happens b. error: ERROR in multi main-client Module not found: Error: Cannot resolve 'file' or 'directory' ./ClientApp/boot-client.ts in C:\***\**** c. doesn't blow up. Access site via localhost:5000: 1. Serves static file fine. 2. Mostly loads otherwise - the underlying page is there, but has an overlay with the above Error message about the multi main-client. I spent over 10 hours trying to resolve it thinking the problem was an IIS sub-app issue still, but I guess that's no longer a thing. A couple hours ago I moved it to a top level site and still have issues as outlined above. Please save me from myself. -------------------- Edit: While I am here and waiting to see how to make this work, I noticed the console errors on Local pointing out the extra **html** and **body** tags that are being rendered after the **app** tag. Is this something that needs to be fixed still? It complains about the extra tags. ------------------ Edit 2: Also noticed 100s of these per second in Fiddler while this is running locally. Tell me this won't be server calls between client and server in production: http: localhost:49155/vshub/f1b1ea0776194961a5b01f0fd8d67d8f/DataWarehouseModule/dataWarehouse/getResult/

fergalmoran closed this issue

2025-08-09 17:19:16 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/JavaScriptServices#1206