Ask a questionAsk a question
 

QuestionSharepoint - Access Denied on default.aspx

  • Monday, January 07, 2008 11:22 AMprakash patil Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi

     

    I've encountered a strange permissions problem while working with a WSS 3.0 site. One of the default.aspx pages for one of the subsite which is imported from staging server which is on other domain  is inaccessible to everyone who attempts to access it with a browser. Even administrators who attempt to open the page are prompted for different login information and eventually given the error:

    "Access denied

    If a user with the correct permissions navigates directly to the subpages of this site, like the Site Settings or Documents and Lists page, no error occurs. The problem seems to be specific to the one .aspx page.

    Also, there is no problem with opening the file in SharePoint Designer or any other program directly from the server. The error only occurs when accessing it with a browser.

    The site was being viewed but not modified when the problem began occuring. I cannot determine any relevant difference in the actions that were taken on the page immediately before the error from what had been done previously.

     

    Does anyone have solution?

     

    Prakash Patil

All Replies

  • Thursday, January 17, 2008 3:34 PMMart Muller Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    Hi,

    Can you try to set another masterpage? The site settings and lists use a different masterpage, so maybe something has gone wrong with that?

     

    Mart.

     

  • Thursday, November 05, 2009 9:38 PMIndybbshop Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    I'm having the same issue, same scenario.  Prakash, did you find an answer to this issue?

    Thank you,

    Jared Gollnitz
  • Friday, November 06, 2009 6:19 AMGanesh Jat Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Please check your default.aspx page , it might have some resource (images, cutom web part that have some code wich needs specific permission) that require some explicit permission to access.
  • Friday, November 06, 2009 5:25 PMcabanuta Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     

    I had the same issue and i found a broken webpart (in my case was the lightning conductor). I had to close that webpart and everything was fine. To do this,  go to the website and type     ?contents=1     in the url, after default.aspx.  Like:   http://website.com/pages/default.aspx?Contents=1
    You will see a list of all the webparts on your page. Click on "Switch to personal view" and then try to close the webparts (close, not delete!), one by one, until you find the one with problems. Check the default.aspx after each webpart that you close on default.aspx?Contents=1 . Being in the personal view, you will not bother any users, it's your view only. After you find the webpart with problems, switch to public view and close that webpart for everybody. Hope this helps.