COMException (0x80004005): Cannot complete this action.
We recently enabled forms authentication for our MOSS Sites and whenever someone checks out a page, it throws aCOMexception to allthe other users . When the page is checked inback , everything is fine. We are using a custom AD membership provider and two sites are enabled: One is intranet (windows authentication, NTLM) and the other internet(forms authentication). Also, impersonation has been enabled. Errors: Cannot complete this action.Please try again. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Runtime.InteropServices.COMException: Cannot complete this action.Please try again.Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [COMException (0x80004005): Cannot complete this action.Please try again.] Microsoft.SharePoint.Library.SPRequestInternalClass.CalculatePermissionsForCurrentThread(Object& pvarAcl, Boolean bOnlyAces, UInt64& pPermGrant, UInt64& pPermDeny, Boolean& pbIsSiteAdmin, Boolean& pbIsSiteAuditor) +0 Microsoft.SharePoint.Library.SPRequest.CalculatePermissionsForCurrentThread(Object& pvarAcl, Boolean bOnlyAces, UInt64& pPermGrant, UInt64& pPermDeny, Boolean& pbIsSiteAdmin, Boolean& pbIsSiteAuditor) +124[SPException: Cannot complete this action.Please try again.] Microsoft.SharePoint.Library.SPRequest.CalculatePermissionsForCurrentThread(Object& pvarAcl, Boolean bOnlyAces, UInt64& pPermGrant, UInt64& pPermDeny, Boolean& pbIsSiteAdmin, Boolean& pbIsSiteAuditor) +165 Microsoft.SharePoint.Administration.SPAcl`1.CalculatePermissions() +144 Microsoft.SharePoint.Administration.SPAcl`1.DoesUserHavePermissions(T permissions) +104 Microsoft.Office.Server.Infrastructure.SharedServiceAccessControlList.AccessCheck(SharedServiceRights rights) +107 Microsoft.Office.Server.UserProfiles.SRPSite.CanManagePeople() +41 Microsoft.Office.Server.UserProfiles.UserProfileManager.get_IsSiteAdmin() +73 Microsoft.Office.Server.UserProfiles.UserProfileManager..ctor(ServerContext serverContext, Boolean IgnoreUserPrivacy, Boolean backwardCompatible) +348 Microsoft.Office.Server.UserProfiles.UserProfileManager..ctor(ServerContext serverContext) +54 Microsoft.SharePoint.Publishing.WebControls.ConsoleUtilities.GetPageCheckedOutMessage(String userLoginName, String userName, String userEmail) +923 Microsoft.SharePoint.Publishing.WebControls.ConsoleDataSource.OnPreRender(EventArgs e) +1024 System.Web.UI.Control.PreRenderRecursiveInternal() +77 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Control.PreRenderRecursiveInternal() +161 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360 Any help on this issue will be greatly appreciated.
July 5th, 2007 3:34pm

We have the same problem. When the page is checked out, and another user accesses the page we get the same error. Has anyone solved this issue? Please post the solution.
Free Windows Admin Tool Kit Click here and download it now
February 5th, 2008 3:25pm

I had same problem. Setting the Impersonate = True (which is default in Apps created by MOSS) resolved the issue.
March 19th, 2008 7:27pm

One possible reason I saw this happening is a malformed query. Or, something that SharePoint does not support. For example, this threw this exact exception: <Where> <And> <Gt> <FieldRef Name='ID'/> <Value Type='Integer'>-1</Value> </Gt> <Lt> <FieldRef Name='ID'/> <Value Type='Integer'>5000</Value> </Lt> <Or> <Eq> <FieldRef Name='Field2'/> <Value Type='Choice'>Value2</Value> </Eq> <Eq> <FieldRef Name='Field3'/> <Value Type='Choice'>Value3</Value> </Eq> </Or> </And> </Where> <OrderBy Override='TRUE'> <FieldRef Name='Field3'/> </OrderBy> After I enclosed the "Gt" and the "Lt" above under an "And", it just worked fine. (Maybe SP doesn't support more than 2 children for a node in a CAML query XML?) So, I'd start with playing with the CAML query, reducing it until it works, and then start to build it up until we reach the exact cause of the error.
Free Windows Admin Tool Kit Click here and download it now
April 22nd, 2008 1:06am

Installing http://support.microsoft.com/kb/936867fixed the issue.
September 30th, 2009 5:19am

It's true. Reducing number of parameters within <And> to two solved this problem for me. Géza Prouza
Free Windows Admin Tool Kit Click here and download it now
April 19th, 2010 12:26pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics