Hi there, I have a report centre site that i am the owner of. I have granted access to a number of other users to have custom privleges over the site. The site has only been in use for a week but twice during that time one of the users has had Access Denied errors on the site and another user has had Access Denied on certain libraries within the site. Both these users have the same permissions. The strange part is that to fix this problem, i as the site owner login to the site, browse to the permissions for the main library on the site and view these permissions and then the users have access again. I don't even change anything. Any help or advise would be greatly appreciated as i am really stuck on this one. Cheers

I feel like I've read about this before. Are you on SP1?

Thanks for your reply. Yes I am on SP1 on Windows Server2008. I have come across some posts where people had IIS access denied errors caused by a problem with ASP.Net but my error is a SharePoint access denied error. At the moment I am logging into the site every morning andbrowsing security settings just to ensure theusers have access Any help would be greatly appreciated Cheers

Does anyone have any idea what is causing this? My users are still experiencing the same issues and I am still unsure how to resolve this. I have been unable to find any other users who are experiencing this issue. Thanks Carla

I have been able to determine that the following error message is occuring when a user attempts to log into a site and get the access denied error: Unknown SPRequest error occurred. More information: 0x80070005 07/22/2008 06:31:34.63 w3wp.exe (0x109C) 0x0FD0 CMS Publishing 8ts5 Unexpected Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) 07/22/2008 06:31:34.63 w3wp.exe (0x109C) 0x0FD0 CMS Publishing 8ts6 Critical Console Configuration File Error: XML Exception: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) 07/22/2008 06:31:34.63 w3wp.exe (0x109C) 0x0FD0 CMS Publishing 7fov Medium Caught a thread abort exception in TemplateRedirectionPage.ProcessRequest, the exception may be expected. stack trace= at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.REPORTCENTERLAYOUT_ASPX_184860969.ProcessRequest(HttpContext context) at Microsoft.SharePoint.Publishing.TemplateRedirectionPage.ProcessRequest(HttpContext context) The following post deals with the same issue however the link to the solution is broken. http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sharepoint.general&tid=1044d4f7-fa32-4cfd-a9c0-8405c8c9a34a&cat=en_US_2BE0F7C1-F80B-C480-EA27-790E679D7E1B&lang=en&cr=US&sloc=&p=1 Anyone have any ideas or know of where another solution is posted for this issue? Cheers

Did you ever find a solution. I have the exact same issue. I have to log on every morning so users have access to a particular sub-site.

Has anyone found a solution to this yet? This error comes and goes on our system. When this error surfaces, the site collection is not accessible by anyone, even the site collection administrator. After a few hours, magically all is better.We have been on with MS premiere support for hours and they do not offer any solution to this issue.

Wehave had the same problem for the last couple of months, with just one of our hundreds of sites. Has anyone been successful in permanently resolving this issue?

Ditto to the above. We are running MOSS 2007 v12.0.0.6341.5002 (Feb 2009 cummulative patch). We did notice that the user does not experience this issue when using the navigation menu, only when they go to the site from a shortcut or manually type the address.J. Aqiu

Apologies for the late reply on this one, in my case the problem was occuring on a subsite (Report Centre) in a site collection (Publishing Site). I had removed user permissions to the parent site because it was still under development even though the sub site is in use. Once i gave all the users permissions (read only) to the parent site this issue disappeared. CheersCarlaCarla

Anyone found a permanent fix?Anil