I moved content from one SharePoint 2007 server to another using stsadm export and import commands. I find now, that on the new server, any list I create does not allow me to edit an item once I have added it. The Edit Item option is available on the context menu but the edit form generates an Access Denied error.I can edit the items of existing lists OK. I can create new items in the old lists and edit those items ok. It is just new lists after import. I am a site collection administrator and a site owner. I have tried manipulating permisisons. I tried adding a custom permission specifically with edit item permission and adding that to me (even though I have full control) but that does not help. I tested the old server and it works fine there. The new server is version 12.0.6425.1000.Thanks in advance for your help.

What the STSADM parameters did you use to move the content?! you should use -includeusersecurity.In current situation I recommend to use STSADM - setsiteowner against your site collection to force site owner settingsSharePoint Tips & Tricks Portal | Microsoft MVP | My Blog | My twitter

The stsadmin command I used to export the site was:-o export -urlsitecollurl -filename FINAL_MIGRATE/rootmigrate.cmp -includeusersecurity -versions 2YesI am a site collection owner. I ran the siteowner command to give something a try but the results are no different.Note that I can edit items in lists that were migrated. It is just lists that were created after the migration that I am having problems with. I can reproduce this by creating a new list, creating an item in the new list and then selecting Edit Item from the context menu. The result is the Access Denied page.

Did you check the EventLogs and 12-hive logs?! Can you post the errors from there?!SharePoint Tips & Tricks Portal | Microsoft MVP | My Blog | My twitter

I've looked at the error logs and nothing useful appears.I played with the sites all day today. In looking at SPManager the items look very similar. My EffectivePermissions on the items are FullMask.The permissions on the old list and new list are basically the same (though one difference which didn't lead me anywhere).---------------------------------------------------------------------------------------------anItem = testnew = New List - Does not WORKnewItemMe = testme = OLD list - WORKSanItem.CheckPermissions(SPBasePermissions.EditListItems) does not generate an exceptionanItem.RoleAssignments.Xml - "<permissions><permission memberid='3' mask='9223372036854775807' />\r\n<permission memberid='4' mask='756052856929' />\r\n<permission memberid='5' mask='1856436900591' />\r\n<permission memberid='7' mask='9223372036854775807' />\r\n</permissions>" anItemMe - "<permissions><permission memberid='3' mask='9223372036854775807' />\r\n<permission memberid='4' mask='756052856929' />\r\n<permission memberid='5' mask='1856436900591' />\r\n<permission memberid='7' mask='206292717568' />\r\n</permissions>" anItem.RoleAssignments[0].RoleDefinitionBindings.XMl= (securitytest Owners)- <Roles> <Role ID="1073741829" Name="Full Control" Description="Has full control." Order="0" Hidden="False" Type="Administrator" BasePermissions="FullMask" /> </Roles> anItem.RoleAssignments[1].RoleDefinitionBindings.XMl= (securitytest Visitors)- <Roles> <Role ID="1073741826" Name="Read" Description="Can view only." Order="0" Hidden="False" Type="Reader" BasePermissions="ViewListItems, OpenItems, ViewVersions, ViewFormPages, Open, ViewPages, CreateSSCSite, BrowseUserInfo, UseClientIntegration, UseRemoteAPIs, CreateAlerts" /> </Roles> anItem.RoleAssignments[2].RoleDefinitionBindings.XMl= (securitytest Members)- <Roles> <Role ID="1073741827" Name="Contribute" Description="Can view, add, update, and delete." Order="0" Hidden="False" Type="Contributor" BasePermissions="ViewListItems, AddListItems, EditListItems, DeleteListItems, OpenItems, ViewVersions, DeleteVersions, ManagePersonalViews, ViewFormPages, Open, ViewPages, CreateSSCSite, BrowseDirectories, BrowseUserInfo, AddDelPrivateWebParts, UpdatePersonalWebParts, UseClientIntegration, UseRemoteAPIs, CreateAlerts, EditMyUserInfo" /> </Roles> anItem.RoleAssignments[3].RoleDefinitionBindings.XMl= (LHSNT\Domain Users)- <Roles> <Role ID="1073741829" Name="Full Control" Description="Has full control." Order="0" Hidden="False" Type="Administrator" BasePermissions="FullMask" /> </Roles>anItemMe.RoleAssignments[0].RoleDefinitionBindings.XMl same as anItem.RoleAssignments[0].RoleDefinitionBindings.XMl=anItemMe.RoleAssignments[1].RoleDefinitionBindings.XMl same as anItem.RoleAssignments[1].RoleDefinitionBindings.XMl=anItemMe.RoleAssignments[2].RoleDefinitionBindings.XMl same as anItem.RoleAssignments[0].RoleDefinitionBindings.XMl=anItemMe.RoleAssignemts[3]- <Roles> <Role ID="1073741825" Name="Limited Access" Description="Can view specific lists, document libraries, list items, folders, or documents when given permissions." Order="0" Hidden="True" Type="Guest" BasePermissions="ViewFormPages, Open, BrowseUserInfo, UseClientIntegration, UseRemoteAPIs" /> </Roles>-----------------------------------------------------------------------------------------------------------------------------------I looked over the EditForm in SP Designer and it seems fine. -----------------------------------------------------------------------So I took one more try at searching the web. I ran across a couple of blog entries that make me think I have the same problems as they are.http://sharepointworld.wordpress.com/2009/04/19/access-denied-error-after-doing-stsadm-importexport/http://www.beyondweblogs.com/post/SharePoint-security-access-denied-permission-corruption-problem-Edit-Item-and-Access-Workflows.aspxhttp://odole.wordpress.com/2009/01/30/access-denied-error-message-while-editing-properties-of-any-document-in-a-moss-document-library/http://vspug.com/share-a-pint/2009/03/11/bug-edit-aspx-pages-survey-branching-and-more/First I am going to try to apply the October 09cumulative update. I don't believe I have that on either machine. I don't see anything in the fix list that makes me believe that is the answer to my problem. So the next step will be to apply the premission fix described in these articles. I will let you know what I find.

Hi Vicki Dillon, Your issue looks same with this one: http://social.technet.microsoft.com/Forums/en-US/sharepointgeneral/thread/4d0578f8-f6f2-480a-8a63-737ac102cf98 Please check it out and following the steps above to resolve it. -lambertSincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Thanks Lambert!This is the exact problem!I applied the latest Cumulativeupdate (Oct 2009) but that did not fix the problem. I tried to re-import the site from scratch and still did not fix the problem. Iwrote a console app that fixed up the PermMask field SchemaXMLper your code example and now I can edit that list item. So I was thinking about how to fix this. I want to fix this permenantly.I tested it out andit appears you can fix the field on the SPWeb that owns the migrated site collection. Then new lists that are created do not have the "bug".I also found that I could use SPManager to navigate to the list/Web in question and edit the Field schema there (instead of writing a console program to exercise the FixField snippet on each site and list).

i fixed the problem of Access Denied Error Message While Editing Properties of any Document in a MOSS Document Library and infopath document library by the running the code of fixing permission problem with moss admin account ranyaof