Error on log in: 500 - Internal server error

Overview

When logging in, you may experience an Internal Server Error (code: 500). This may occur after a DNN Evoq upgrade. In these cases, you may not be able to access the administrative interface of the site due to the login error.

You may also find the following error in your server logs during that time: 

System.AggregateException: One or more errors occurred. ---> 
System.Net.Http.HttpRequestException: An error occurred while sending the request. --->
System.Net.WebException: The remote name could not be resolved: 'dnnapi.com'

 

Solution

This problem may be tied to a problem connecting to Microservices. Though the root cause may be different in each case, this problem can be resolved in some cases by disabling microservices and re-enabling them.

To implement this solution, you will need access to your site's SQL Server as well as Super User access to your site.

 

Step 1: Disable Microservices

NOTE: As with any process involving SQL scripts, we recommend you backup your site database before running the script against it. Be sure to test the script in a safe environment before running it against production.

  1. Attached to this article is a SQL script titled DisableMicroservices.sql. You can run this script against your site's database to disable your microservices.
  2. You should be able to log into your site now. Log in as a Super User.
  3. Clear your server cache and restart the DNN application

 

Step 2: Re-enable Microservices

Only re-enable the microservices your site needs. If this problem has been persistent, it may be worth leaving some microservices off to pinpoint which microservice is causing the problem. You can re-enable your microservices by following the directions in the article Enable Microservices.

 

Testing

To test the solution, log out and re-enter the site after enabling your microservices.

If problems re-occur, you may need to contact DNN support for further troubleshooting. Be sure to include your server error logs for the time in question, as well as a precise timeline for the problem and all troubleshooting steps taken.

Attachments

Comments

0 comments

Please sign in to leave a comment.