All new sites have bad permissions

[Super2]

On one MOSS site collection, any new sub site has permissions problems. I am
the site owner, collection admin, server admin, but after creating a sub site
I can't edit any items.

I get an access denied message if I try to edit the default Welcome
announcement.
I have even added all authenticated users to the owners group and I still
get access denied.
Any ideas what might be going on?
Thanks

[spconsultant]

What does your environment look like? Win2008?

[Super2]

2003. It only happens on this site collection.

[xuemei chang [MSFT]]

Hello,

Thanks for your post!

I am sorry I cannot reproduce the issue, in order to narrow down the
problem's scope, could you let us know some more detailed information:

1. Did the sub site use unique permissions when creating?
2. If the sub site used unique permissions, you said you have added users
to site owners group, please make sure the group has permission to the sub
site (go to the sub site>People and Groups>select the site Owners
group>select "Settings"> click "View group permissions");
3. Did the issue only happen on the default Announcement list, or all the
lists? If it happened on the Announcement list, please make sure has
permissions in the list.

Let me know the result if possible.

Best Regards,
Xuemei Chang
Microsoft Online Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

[Super2]

1. The problem will happen with a new sub site that uses either unique
permissions or inherited permissions.
2. Yea
3. All lists have the problem.

Thanks

[xuemei chang [MSFT]]

Hi,

Thanks for your feedback.

From your post, we know that the users have adequate permissions to edit
the sub site and list item. Could you please tell me was the site
collection a customized site collection? For example firstly export a site
collection and then import the site collection to a new site collection.

If so, it is a known issue that we cannot edit new list items on customized
site collection and it was fixed in February Cumulative Update, It is
suggested to apply the Cu to fix the issue. Please visit Updates Resource
Center for SharePoint Products and Technologies
(http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx)
to get the latest update.

But for the existed sites that have the issue, you can fix them with the
code of this blog:
http://www.beyondweblogs.com/post/SharePoint-security-access-denied-permissi
on-corruption-problem-Edit-Item-and-Access-Workflows.aspx

Hope it can help you.

Best Regards,
Xuemei Chang
Microsoft Online Support

Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

[Susan]

On Oct 13, 1:39 am, v-xmc...@online.microsoft.com (xuemei chang

[MSFT]) wrote:
> Hi,
>
> Thanks for your feedback.
>
> From your post, we know that the users have  adequate permissions to edit
> the sub site and list item. Could you please tell me was the site
> collection a customized site collection? For example firstly export a site
> collection and then import the site collection to a new site collection.
>
> If so, it is a known issue that we cannot edit new list items on customized
> site collection and it was fixed in February Cumulative Update, It is
> suggested to apply the Cu to fix the issue. Please visit Updates Resource
> Center for SharePoint Products and Technologies
> (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx)
> to get the latest update.
>
> But for the existed sites that have the issue, you can fix them with the

> code of this blog:http://www.beyondweblogs.com/post/SharePoint-security-access-denied-p...

> on-corruption-problem-Edit-Item-and-Access-Workflows.aspx
>
> Hope it can help you.
>
> Best Regards,
> Xuemei Chang
> Microsoft Online Support
>
> Get Secure! -www.microsoft.com/security
> =====================================================
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.

I am experiencing the exact same issue. Was a resolution found for
existing sites?

Thanks!
Susan

[xuemei chang [MSFT]]

Hello,

I am interested in this issue. Would you mind letting me know the result of
the suggestions? If you need further assistance, feel free to let me know.
I will be more than happy to be of assistance.

To Susan, for the existed sites that have the issue, you can fix them with

the code of this blog:

http://www.beyondweblogs.com/post/SharePoint-security-access-denied-permissi
on-corruption-problem-Edit-Item-and-Access-Workflows.aspx
For your information, I list the workarounds in our internal database:
For existing lists, you can run the following code to fix it. This here is
a sample peace of code that should add the appropriate attribute to the
list having the issue:
void FixField()
{
string RenderXMLPattenAttribute = "RenderXMLUsingPattern"
string weburl = "<http://localhost>"
string listName = "test2"
SPSite site = new SPSite(weburl);
SPWeb web = site.OpenWeb();
SPList list = web.Lists[listName];
SPField f = list.Fields.GetFieldByInternalName("PermMask");
string s = f.SchemaXml;
Console.WriteLine("schemaXml before: " + s);
XmlDocument xd = new XmlDocument();
xd.LoadXml(s);
XmlElement xe = xd.DocumentElement;
if (xe.Attributes[RenderXMLPattenAttribute] == null)
{
XmlAttribute attr =
xd.CreateAttribute(RenderXMLPattenAttribute);
attr.Value = "TRUE"
xe.Attributes.Append(attr);
}
string strXml = xe.OuterXml;
Console.WriteLine("schemaXml after: " + strXml);
f.SchemaXml = strXml;
}

Have a nice day!