Views:


Applies to Product - Power Pages

What’s happening?
Portal websites intermittently encounter a 500 Internal Server Error, preventing users from accessing the application and causing disruptions.
 

Reason:
The underlying causes for the 500 Internal Server Error may include:

  • Expired authentication keys.
  • Configuration issues related to the website's setup, such as missing active site markers or incorrect entity configurations.
  • The Dataverse organization where the website is created may be in administration mode or not running.
  • CSS files not loading properly, potentially due to caching problems.

 

Resolution:
To resolve the 500 Internal Server Error, follow these steps:

  1. Check Authentication Key: Ensure that the authentication key is not expired. If it is expired, renew the authentication key.
  2. Verify Dataverse Organization: Confirm that the Dataverse organization where the website is created is up and running and not in administration mode. If it is in administration mode, disable this from the Power Platform Administration mode.
  3. Check Application User: Ensure that there is an application user created for the website in the Dataverse organization. Run the site checker to confirm if the application user exists.
  4. Update Site Configuration: Verify that the website record is present and active, and that the website binding is also present and active from the management app.
  5. Clear Cache: Restart the portal to clear the cache and reload the CSS files.
  6. Run Site Checker: Use the site checker to identify and address any configuration issues related to entity forms, multi-step forms, and quick forms.
  7. View Error Logs: Disable custom error settings to access detailed error logs and identify specific exceptions.
If the issue persists after following these steps, further investigation may be required to identify additional underlying causes.