Submit a ticketCall us

AnnouncementsFace your biggest database issues head-on

Our new eCourse helps you navigate SQL Server performance blocks by teaching you how to recognize and deal with the three DBA Disruptors: Performance Hog, Blame Shifter, and Query Blocker. Register today to learn how to defend your environment and fend off menacing disruptions.

Register for your free eCourse.

Home > Success Center > Orion Platform > Orion - Knowledgebase Articles > Orion website fails to start after a reboot

Orion website fails to start after a reboot

Created by Richard Casey, last modified by Karen Valdellon_ret on Nov 14, 2016

Views: 1,002 Votes: 1 Revisions: 10


After rebooting the Orion server, the website fails to start automatically.


All NPM versions


  • Default website causes conflict with the port 80 binding used by the Orion website.
  • A large number of failed delivery attempts for notifications can cause problems to Information Service


1. Click Start and then enter INETMGR.

2. Press Enter.

3. Expand the websites.

4. Right-click the default website and click Remove.

5. Clear the tables below according to the article Clear Information Service Subscriptions:
DELETE FROM Pendingnotifications   
DELETE FROM Subscriptiontags
DELETE FROM Subscriptions

6. Clear .Net Cache manually:

  1. On the Orion server, go to Start > Run, and enter services.msc.
  2. Stop the IIS service. Generally this would be named World Wide Publishing Service.
  3. When the service has stopped, go to C:\Windows\Microsoft.NET\Framework\
  4. Delete everything in the following directories
    1.  C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\root.
    2.  C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\root.
    3.  C:\Windows\Microsoft.NET\Framework64\v2.0.50727\Temporary ASP.NET Files\root.
    4.  C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\root.
  5. Delete everything in this directory if anything exists.
  6. Restart the IIS service.


An alternate Solution may be to set each of the SolarWinds Services to automatic (delayed start).


Last modified