I have a SharePoint 2007 EE Site (with patches up to version 12.0.0.6327) running on Windows Server 2008 & SQL Server 2008.I ported an existing site from a different domain to this server by backing up/restoring the content database. The site is running fine.I added a new sub-site and here is where I have the issue. If I create a document library, add a document, and then use the drop-down on the item to pick "edit properties" I bounce to the SP Error: Access Denied screen. My account is a site admin and has full access to the sub-site. I can view the properties fine. When I try to upload a document I get the access denied error message if some of the meta data properties are marked "required". The document is still uploaded. I also get the same error when I try to edit an item in a list.I can view/edit the properties in Data sheet view fine. The libraries on the existing sites work fine. It only seems to be an issue on new sub-sites.It almost seems like a permission problem generating the property edit forms. There is nothing in the SP log files.

Do you have different SSP's? Check that your site is linked to right SSP.Regards/Henrik

New items uploaded started working recently with no changes made to the system. Users cannot still edit properties of existing items.

One was created using a template - Is there something specific to remplates that I should look at?

I have a SharePoint 2007running on Windows Server 2003 & SQL Server 2005 and I have a similar problem:I added a new sub-site and here is where I have the issue. If I create a document library, add a document, and then use the drop-down on the item to pick "edit properties" I bounce to the SP Error: Access Denied screen. I can view the properties fine.The libraries on the existing sites work fine. It only seems to be an issue on new sub-sites.If I try to set permissionsfor a specific document or folder it is not possible. In the Actions there is only "Manage Permissions of Parent" I tried with Site collection admin account; System Account and user Account with full controlon site and sub-site. We did not import or export anytemplate. Does anybody found anything why this could happened?

Hi,When you say 'this is by design behavior and is targeted for next release', do you mean 'targeted to be corrected in next release?' Do you know if there will indeed be a hotfix, as another reply has implied?Thanks.

What is the work around? Do we have to move all the content OUT of the sub-site?

I worked through this issue with Micrososoft PSS. The Februray hotfix rollup kb961756 & kb961755 contain a fix to prevent this issue from occuring. This does not fixexisting sites though. The support person sent me a small executable that when executed against the SP libraries with the issue fixed the problem. The source code for this app is as follows. Put this in a console app and pass the site URL and list name as parameters. using System; using System.Collections.Generic; using System.Text; using Microsoft.SharePoint; using System.Xml; namespace CA_TestingHotfix { class Program { static void Main(string[] args) { FixField(args); } static void FixField(string[] args) { string RenderXMLPattenAttribute = "RenderXMLUsingPattern"; //Console.WriteLine("Please enter the URL of the site: (Press enter after typing):"); string weburl = args[0]; //Console.WriteLine("Please enter the Document Library Name: (Press enter after typing):"); string listName = args[1]; 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; } } }

This work fine... but if I create a new list the problem come back again in this new list...For sure I can't run this code everytime I have to create a new list or a new document library.Any idea?PSThis problem in my case happen also in the main site not only in the subsite.

Xue-Mei Chang, Would liketo know why this is by design. Seems to defeat the export/import process.

I think he meant it is a known issue and was slated to be fixed in SP2.

Hi everyone, we've detected some problems with item contextual menu that shows VIEW PROPERTIES and EDIT PROPERTIES options for only read access users. Is it related with this issue? We've started to have problems uploading documents and system allways shows the annoying ACCESS DENIED ERROR page. How can we fix that?Thanks for your help.

I am having the list edit issue as well. When i create the new list and try to edit item i get ACCESS denied. it occurs in all new list. I have full control on whole site collection. Please help.

Hello all, @Douglasfo -- did you ever find a solution on your side? We've noticed the same thing on our server. We also tried applying KB971065 but that didn't do anything. Does anyone have any suggestions? Many thanks in advance!

All,As many before me I just encountered this error as well. Users created a links list and then add items to the list and went to edit them and got "Access Denied". Even me the Site Collection Admin is getting the error on the this and any new links list that I create. Has there been a fix or to this or do i need the run the executable code that is on this post?We are in the process to upgrade to SP2 in our production environment today and from other comments even that will not fix the issue on exisiting lists.www.sharepointbeginners.com

You need to also fix the Field definition for the affected sites (not just the lists that are affected). The reason this happens in new lists is that the field definition is also missing the RenderXMLUsingPattern attribute. So in addition to fixing the lists with the problem you need to fix the field definition in the affected sites.Instead of writing a console app, you can also do this by using SPManager tool. Navigate to the affected site. Then navigate to the fields collection. Then find the "Effective Base Permission" field. Edit the SchemaXML for the field and add the attribute RenderXMLUsingPattern="TRUE".

i am having this problem as well. i'll try the fix from vicki, but any proposed fix or anything like that by microsoft?

Ok...it is available on list level. But there is no xmlSchema in field collection at site level....it is blank as given below <?xml version="1.0" encoding="utf-16"?><Fields></Fields>how we can fix it instead of each list?