Submit a ticketCall us

WebinarVisual Monitoring Tactics: Getting More Log Search Value from SolarWinds Log & Event Manager with nDepth Webcast

Do things seem to make more sense when they are visualized? Are you an IT professional or security expert with a wish for more cybersecurity tools that provide an intuitive visual experience? Join Alexis Horn and Jamie Hynds from SolarWinds as they demonstrate how the nDepth feature in LEM can help make visualizing log search results a reality.

Register now.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Rebuild the Orion Website

Rebuild the Orion Website

Updated November 1, 2018


This article describes how to rebuild the Orion Website when a user encounters certain issues, such as Web Console Error 500 or Internal Server Error 500 issues.

Rebuilding the website means downtime and maintenance windows. 


NPM 11.5 and later


  1. Stop all Orion Services using the Orion Service Manager.
  2. Open the IIS Manager (Start > Run > enter "inetmgr").
  3. Navigate through the Connections tree and select the SolarWinds NetPerfMon site.NPM_RebuildOrionWebsite.png
  4. Note the Orion Web Site details:
    1. With SolarWinds NetPerfMon selected in Connections, click Basic Settings in the Actions pane on the right, and note the location of the WebSite directory (Physical path).

    2. In the Actions pane, click Bindings and note any available bindings.

  5. Right-click the SolarWinds NetPerfMon site, and click Remove.

    Deleting the Orion Web Site will not cause any data loss because all settings are stored in the database. 


  6. Delete the SolarWinds Orion Application Pools.
    1. In the Connections tree, select Application Pool.
    2. In the center area, right-click the SolarWinds Application Pool and select Remove.


  7. Make a backup of the SolarWinds folder in inetpub: Go to  C:\inetpub in the File System and rename the SolarWinds folder to Solarwinds.old and move it to another folder away from inetpub.

    You may need to run IISRESET from CMD to unlock the files.

  8. Delete everything in:  
    C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root\*
    C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root\*
    C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root\*
    C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root\*

    You may need to run IISRESET from an elevated command prompt to avoid a file sharing violation.

  9. Run the Configuration Wizard and select the Website component. (optionally: Select all - Database, Website and Services and then click Next.)
  10. On Website Settings, make sure the Website Root Directory is the same as the Physical Path for the website you noted in step 4. 
  11. Follow the on-screen instructions and complete the Configuration Wizard. The Orion Web Site will be created.
  12. Verify that the new Web Site has correct bindings:

    1. Open IIS, navigate to your Orion Web Site.

    2. In the Actions pane, click Bindings, and adjust or add bindings so correspond with the notes you took in step 4.

    3. You may need to run IISRESET from an elevated command prompt right after if the page did not load at the end of the configuration wizard. then re-open page.

The Orion Web Site is rebuilt now. It might be slow for 30 -60 minutes after the rebuild.

If your issues persist, look for troubleshooting options at SolarWinds Customer Success Center or on THWACK.


Last modified