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.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

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.
10 Tips to Protect Your Business from Ransomware

Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.

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.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ABV_UKAuthor Commented:
Found issue.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Applications

From novice to tech pro — start learning today.