locked
SharePoint 2007 performance issue after upgrading the operating system RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    We upgraded the operating system of our SharePoint Server 2007 from 2003 to 2008 R2. After upgrade we rebuilt the SharePoint using content DBs we backed up before upgrade. All settings is same except that we moved the DBs to new SQL servers. Now users are reporting performance issue with sites. I experienced it myself some of the pages takes 9-30 seconds to load. Also our SharePoint server is single server. I monitored the SharePoint Server and it is fine. I did fiddler trace and here are the result. I see lots of 401 (login failed) errors then 302 (redirect) then 200 (OK). Do you know why we are getting 401 errors?

    # Result Protocol Host URL Body Caching Content-Type Process
    184 401 HTTP sp07.ourcompany.com /bif/EUROPE-AMA 341 text/html; charset=us-ascii iexplore:15344
    185 302 HTTP sp07.ourcompany.com /bif/EUROPE-AMA 196 text/html; charset=UTF-8 iexplore:15344
    186 401 HTTP sp07.ourcompany.com /bif/EUROPE-AMA/default.aspx 341 text/html; charset=us-ascii iexplore:15344
    187 200 HTTP sp07.ourcompany.com /bif/EUROPE-AMA/default.aspx 105,487 private, max-age=0; Expires: Mon, 22 Dec 2014 21:37:48 GMT text/html; charset=utf-8 iexplore:15344
    188 401 HTTP sp07.ourcompany.com /_layouts/1033/styles/calendar.css?rev=BrbrIU86qTG2EHx1ZUuFBQ%3D%3D 341 text/html; charset=us-ascii iexplore:15344
    189 200 HTTP sp07.ourcompany.com /_layouts/images/prevbuttonltr.gif 76 max-age=31536000 image/gif iexplore:15344
    190 200 HTTP sp07.ourcompany.com /_layouts/images/nextbuttonltr.gif 78 max-age=31536000 image/gif iexplore:15344
    191 200 HTTP sp07.ourcompany.com /_layouts/images/day.gif 1,051 max-age=31536000 image/gif iexplore:15344
    192 200 HTTP sp07.ourcompany.com /_layouts/images/month.gif 1,068 max-age=31536000 image/gif iexplore:15344
    193 200 HTTP sp07.ourcompany.com /_layouts/1033/styles/calendar.css?rev=BrbrIU86qTG2EHx1ZUuFBQ%3D%3D 28,814 max-age=31536000 text/css iexplore:15344
    194 200 HTTP sp07.ourcompany.com /_layouts/images/week.gif 1,057 max-age=31536000 image/gif iexplore:15344
    195 200 HTTP sp07.ourcompany.com /_layouts/images/weekbox.gif 149 max-age=31536000 image/gif iexplore:15344
    196 200 HTTP sp07.ourcompany.com /_layouts/images/alldayDefault.gif 157 max-age=31536000 image/gif iexplore:15344
    197 200 HTTP sp07.ourcompany.com /_layouts/images/calnumBttntoday.gif 146 max-age=31536000 image/gif iexplore:15344
    198 200 HTTP sp07.ourcompany.com /_layouts/images/calnumBttn.gif 95 max-age=31536000 image/gif iexplore:15344

    Wednesday, January 7, 2015 5:24 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    when you request a  Site collection (http://domain/) or a Site (http://domain/foo/) of your Publishing Site you get redirected to the http://domain/Pages/<WelcomePage>.aspx. SharePoint 2007 uses the 302 header (location temporarily moved) for this purpose. Surprisingly even WSS uses the 302 header to redirect a root url to the default.aspx. In comparison ASP.NET uses an internal redirect to render the default page when the root url requested: there is no redirect in this situation.

    Check the link which can give more input

    http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/

    for error 401 you can check this link

    http://discussions.citrix.com/topic/97027-no-resources-401-unauthorized/d

    and check SharePoint ULS logs and event viewer for any exceptions.

    Please mark the Answer and Vote me if you think that it will help you to resolved your issue



    • Marked as answer by F1365 Thursday, January 15, 2015 5:11 PM
    Saturday, January 10, 2015 6:30 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Are you using Publishing sites or team sites? Is the performance slow for OOTB sites too?

    Please check the SharePoint ULS logs and event viewer for any exceptions.

    Sometimes reseting the superuser and superreader account helps if the issue is with caching.

    Regards, Mahesh

    Saturday, January 10, 2015 4:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    when you request a  Site collection (http://domain/) or a Site (http://domain/foo/) of your Publishing Site you get redirected to the http://domain/Pages/<WelcomePage>.aspx. SharePoint 2007 uses the 302 header (location temporarily moved) for this purpose. Surprisingly even WSS uses the 302 header to redirect a root url to the default.aspx. In comparison ASP.NET uses an internal redirect to render the default page when the root url requested: there is no redirect in this situation.

    Check the link which can give more input

    http://blog.mastykarz.nl/sharepoint-2007-redirect-solved-using-301-instead-of-302-redirects/

    for error 401 you can check this link

    http://discussions.citrix.com/topic/97027-no-resources-401-unauthorized/d

    and check SharePoint ULS logs and event viewer for any exceptions.

    Please mark the Answer and Vote me if you think that it will help you to resolved your issue



    • Marked as answer by F1365 Thursday, January 15, 2015 5:11 PM
    Saturday, January 10, 2015 6:30 PM