After publishing an ASP.NET Web App, I'm trying to host the website on my local server. However, when I start it up, it gives me this error in my browser:
Oops. 500 Internal Server Error An error occurred while starting the application.
How can I debug what this error is? The website works (both Debug and Release configurations) when starting using IISExpress and "web" in Visual Studio.
I am using the Development environment, and I have already specified app.UseDeveloperExceptionPage();
.
I have followed the instructions here to deploy to IIS.
I've also tried the suggestion offered here (re-publishing with "Delete all existing files prior to publish" selected). (The OP there has a slightly different error, so that's why I'm posting a new question.)
I've looked for hours on the internet, but there doesn't seem to be much content about it. Any ideas?
I am on Windows 7, using ASP.NET 5 RC1.
The implementation class of above interface having dummy data. Then we have to create a Controller(API) for calling this repo, and inject this interface into this. In the last, we have to register it in Startup class. Also mention which type of instance want to inject - (the lifetime) of our instance.
You should set the stdoutLogEnabled=true
in the web.config file to see the actual error that is happening. You can direct where these files are written with the stdoutLogFile
argument; the screenshot example below writes to stdoutLogFile=".\logs\stdout"
. (You should ensure the directory exists; the app won't create it)
As for not being able to find the proper config file yes the default environment is production. It is set to development explicitly in visual studio in the project properties.
Update: In AspNetCore RTM the module is called aspnetCore under the system.webServer node in web.config. Also, as @ErikE pointed out in comments, the web.config is now located in the root of the project and not under wwwroot as in previous releases.
This error also occurs when you are attempting a database connection from the startup (eg for seeding) and it fails on the deployment server due to insufficent previleges at the database server.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With