• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 629
  • Last Modified:

Sharepoint (WSS 3.0) Slow start up

Our users each experience a 30-40 second delay the first time they try and log on to our new sharepoint site (WSS 3.0). After they have logged in once, the delay seems to disappear until the next day.

The WSS 3.0 environment is Server 2003 with a seperate SQL 2008 database.

I have read a fair amount on IIS and sharepoint warm up scripts, but the problem seems to be on each client locally.

I have also used the program "Fiddler" to check for any page errors - with no bad results.
1 Solution
Justin SmithSr. System EngineerCommented:
Are you 100% positive it happens to EVERY user the first time they load in the day?

This smells like a warm up issue, but it would only affect the absolute first person of the day.
When did this issue start?  Are you sure this is a SharePoint issue and not a GPO issue?

If you have verified it's happening to each user, then maybe have a look at IIS optimization...Have you enabled compression, cacheing, etc?  Here's a useful article:




ABV_UKAuthor Commented:
Hi there Ach1lles. Yes, this is happening for all users. Not just the first one to hit the site.

And Hi to you too Zar.
This is a new WSS 3.0 site and has always happened evn when it was being built.  I have tried the IIS optimisation stuff from the links but this has not made any difference. Caching etc is already enabled.

With regards to the GPO issue i'm not 100% sure what you mean but I dont think it is as we have an old WSS 3.0 site set up in the same environemnt. This loads fine on first try.

I just cant really sees how it differs from what i've set up myself. Theres no server memory / cpu spikes when we first log in either.
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

I'd look at the authentication "stream" - that is, when a user hits IIS first time in the morning, it has to authenticate anew - and that's where you are seeing the lag.

Are you using NTLM or Kerberos on the web application for authentication?
Is time in sync across all machines (client, servers (WSS and SQL) and dc's)?
Is DNS resolution fast and accurate from WSS to the SQL and DC's?
If you have the support tools installed, run a NETDIAG from 2003 box and see if there are any errors there.
Are there any nastygrams in EventViewer (on WSS or SQL) when a user logs in?

ABV_UKAuthor Commented:
OK - i found the issue. It turned out to be a webpart. It was a standard built in web part which displayed a folder on a shared drive. After removing this, it works lightning quick :)

Thanks very much for your all your help anyway guys.
ABV_UKAuthor Commented:
Found issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now