Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Takes long time for Solarwinds to start? reach login screen

Hi,

After not using the solarwidns site for an hour or two or over night the first visit to the site takes a very long time... about 30 seconds to reach login screen. Once the first visit is done then the site responds quickly

Latest version, running NPM, APM and NetFlow

Windows 2008 R2 - SQL 2008 R2

2 X 6 core 2.3GHZ, 6GB RAM

It feels like SQL is going to sleep or something?

Find more posts tagged with

Accepted answers

All comments

bobross

We have ~50 different Solarwinds servers and none of them exhibit this behavior. I'd be inclined to think its more of a network issue myself. Might try taking a look there for the culprit.

sean.martinez

There are three possible causes and resolutions to resolve the issue that you are seeing:

Resolution #1

If the Orion web console was not being used heavily, IIS shuts down the worker process that handles requests from Orion's website every 20 minutes (this is the default value in IIS).

Server 2008

1. Control Panel> Administrative Tools> IIS Manager

2. Expand out Local Computer

3. Select Application Pools

4. Right Click on SolarWinds Orion Application Pool and select Properties (or Advanced Settings for Server 2008)

5. In the Idle Time-out (minutes) box, type a number of minutes (you can set to 1440 for 1 full day), and then click OK.

Server 2003

6. Control Panel> Administrative Tools> IIS Manager

7. In IIS Manager, expand the local computer, expand Application Pools, right-click the Solarwinds Orion application pool, and then click Properties.

8. On the Performance tab, under Idle timeout, select the Shutdown worker processes after being idle for check box.

9. In the minutes box, type the number of idle minutes (with no processing requests) that you want to elapse before shutting down the idle worker process. The default value is 20 minutes. (You can set to 1440 for 1 full day)

10. Click OK.

Resolution #2 Proxy Auto Detection

The problem is being caused by proxy auto-detection. Internet Explorer is set to auto-detect proxies, then HttpWebRequest will as well, only it will auto-detect every time you create a new WebRequest instead of caching anything in a helpful manner.

This KB article talks about the issue: http://support.microsoft.com/kb/968699

Method 1: Turn off “Automatically Detect Settings” in Internet Explorer

Method 2: Modify machine.config to disable .Net framework from using the autoproxy feature.

You should only need to make a change here:

C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\Machine.config

Find this line, then inset the following below --></system.serviceModel>

<system.net>

</defaultProxy>

</system.net>

This is the last line in the config, and should be just after the new code --> </configuration>

Resolution #3 Thwack Resources or NCM integration

On the Page you are seeing slowness, remove all Thwack.com Resources from the Page which can cause some Delays. If you have the NCM Integration, please remove any NCM Resources from the Pages that are having loading delays and this will further reduce Loading time as well.