piersonal
Thu Apr 24 03:16:46 CDT 2008
On Apr 23, 2:07=A0am, "galvin.p...@gmail.com" <galvin.p...@gmail.com>
wrote:
> On Apr 22, 12:47=A0pm, piersonal <piers.but...@silverbug.com> wrote:
>
> > We have the weirdest thing just happen with our install of MOSS and it
> > has stumped us all.
>
> > Under our Ops department site, we have 3 sub sites for Admin,
> > Frontline and 3rd Line. Admin and 3rd Line are fine, but no-one other
> > than the 2 SharePoint admin accounts can access Frontline.
>
> > The error is the standard "Access Denied" message that you would get
> > if you didn't have permissions to the site, but the site is using
> > inherited permissions, so exactly the same as the parent Ops site and
> > the 2 sibling sites, but nothing. We have done everything that we can
> > think of bar recreating the site, so hoping that someone might be able
> > to save us before we have to resort to this ...
>
> If you wanted to do something like this on purpose, you could create a
> web application policy. =A0I did the opposite of that once by accident
> and bloggeda about it here:
http://paulgalvin.spaces.live.com/blog/cns!1CC1=
EDB3DAA9B8AA!255.entry
>
> --Paul Galvin, Conchango
> =A0 RSS @
http://feeds.feedburner.com/PaulGalvinsSharepointSpace
> =A0 Web site @
http://paulgalvin.spaces.live.com
> =A0 Twitter @
http://twitter.com/pagalvin
Many thanks for your reply Paul and this wasn't something that we had
thought of. Unfortunately in this case it wasn't what was wrong so we
have since logged a call with Microsoft and after a good few hours, we
have finally figured out what was wrong
First a nice trick we didn't know: adding ?contents=3D1 to the end of
the default.aspx url gives you the diagnostic option of first
temporarily disabling web parts from loading before opening the actual
page
By using this, we were able to find out that the offending web part
was a sql display that required a document library to first be updated
in order for the web part to be populated. We had inadvertently
changed the rights for all but admin to this back end library to read
only and this lead to no-one being able to open even the site, let
alone the specific web part. By giving all our users the contribute
rights, the page opened fine. Good old Microsoft support!
Hoping this might be of use to someone else out there!