locked
Yet another cannot edit ASPX pages in Sharepoint Designer 2007 RRS feed

  • Question

  • Hi,

    Whenever I try to edit ASPX pages in my WSS 3.0 instance (both on my dev and production environments), I get the "Server could not complete your request" error with details of:

    soap:ServerServer was unable to process request. ---> Cannot complete this action. Please try again. ---> Cannot complete this action. Please try again.

    I've been looking online and saw several others have experienced this issue.  Unfortunately, none of the provided solutions are working for me.  I tried clearing my website cache, clearing out my temp internet files and using the FQDN to no avail.  I tried to check out the master page through my browser and then used the context menu to "Edit in Sharepoint Designer", but that failed as well.  I cleared out any and all web parts causing errors on my pages and that did not fix the situation.

    Like others in this boat, I can create new ASPX pages and edit them at the time of creation.  However, I cannot edit them after they've been created.  I can also create and edit HTML pages with no problems.  I have full rights on all of the servers as I'm a domain admin and a SharePoint administrator.  Also, the ability to edit ASPX pages worked for me in the past, though that was about 2 years ago.  Our environment hasn't shifted very much however in that time.

    Any help would be greatly appreciated.

    Thank you.

    Sincerely,

    Dave

    Tuesday, March 8, 2011 7:26 PM

All replies

  • Hey Dave,

    Can you edit other aspx pages - like default.aspx, AllItems.aspx, etc?

    Thanks!

    Tom


    Tom Molskow - SharePoint Architect - Microsoft Community Contributor 2011 Award - Linked-In - SharePoint Gypsy
    • Marked as answer by Leoyi Sun Wednesday, March 23, 2011 2:19 AM
    • Unmarked as answer by Mike Walsh FIN Thursday, June 16, 2011 5:32 AM
    Tuesday, March 8, 2011 11:13 PM
  • Hi Tom,

    Thanks for getting back to me.  Sorry to take so long to respond.

    I can't edit any aspx pages on the site - default.aspx, allitems.aspx, etc.  Any aspx pages, whether they be custom or out-of-the-box, gives me that error.

    Thanks!

    -Dave-

    Tuesday, March 15, 2011 4:25 PM
  • Hey Dave,

    You may be missing the "Add and Customize Pages" permission at the site level.  Can you check your permissions at the site level and verify this?  Also, here is a great blog on locking down SPD - http://blogs.msdn.com/b/sharepointdesigner/archive/2008/11/25/locking-down-sharepoint-designer.aspx

    Thanks!

    Tom


    Tom Molskow - SharePoint Architect - Microsoft Community Contributor 2011 Award - Linked-In - SharePoint Gypsy
    • Marked as answer by Leoyi Sun Wednesday, March 23, 2011 2:19 AM
    • Unmarked as answer by Mike Walsh FIN Thursday, June 16, 2011 5:32 AM
    Tuesday, March 15, 2011 6:14 PM
  • I'm experiencing this problem on a number of separate SharePoint farms in the same domain.  As far as I can tell, it happened simultaneously on all farms.

    I've tried all the standard "fixes" for this, including installing a brand new instance of SPD 2007 on a fresh VM, but I can't open any *.aspx page on any SharePoint site, including the SharePoint instance on my dev workstation (which I know hasn't been modified, unless an OS patch has been involved).

    Yes, I have add and customize pages, and I'm a site collection admin as well as a farm admin.

    This can't be any sort of cache issue, since I installed a brand new instance of SPD in a fresh VM, and still have the problem.  The problem repros even when our infrastructure engineer tries to do it.

    Thanks,

    Mike

    Also, I don't understand  how Leoyi Sun can mark a question as an answer; Leoyi, it's not helpful to mark anything as an answer unless it actually solves the problem.

    Update:

    Looking deeper into this, I see that this is the request that SPD is making:

    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
      <soap:Body>
        <GetWebPartPage xmlns="http://microsoft.com/sharepoint/webpartpages">
          <documentName>default.aspx</documentName>
        </GetWebPartPage>
      </soap:Body>
    </soap:Envelope>

    When you look at the WSDL for GetWebPartPage, you can see that this is what it *should* be: 

    <s:element name="GetWebPartPage">
      <s:complexType>
        <s:sequence>
          <s:element minOccurs="0" maxOccurs="1" name="documentName" type="s:string" />
          <s:element minOccurs="1" maxOccurs="1" name="behavior" type="tns:SPWebServiceBehavior" />
        </s:sequence>
      </s:complexType>
    </s:element>
    
    
    
    <?xml version="1.0" encoding="utf-8"?>
    <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>
      <GetWebPartPage xmlns="http://microsoft.com/sharepoint/webpartpages">
        <documentName>string</documentName>
        <behavior>Version3</behavior>
      </GetWebPartPage>
    </soap:Body>
    </soap:Envelope> 
    


    So my request is missing the required <behavior> parameter.  Anyone have a clue? And what could have caused this??

    Thanks,

    Mike



    Wednesday, June 15, 2011 10:55 PM
  • Well, the SOAP schema thing may be a red herring...I tried using the same instance of SPD but to a WSS 3.0 SharePoint instance hosted in a different domain, and the same SOAP request works without the behavior element.

    Here's the ULS trace when the 500 error occurs:

    06/16/2011 12:07:14.62  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    Database  880m Verbose  
     SqlCommand: 'dbo.proc_getObjectsByBaseClass'     CommandType: StoredProcedure CommandTimeout: 0     Parameter: '@RETURN_VALUE' Type: Int Size: 0 Direction: ReturnValue Value: ''     Parameter: '@BaseClassId' Type: UniqueIdentifier Size: 0 Direction: Input Value: '113fb569-7520-4651-8fc4-e9f4f5887618'     Parameter: '@ParentId' Type: UniqueIdentifier Size: 0 Direction: Input Value: '08d288c2-5e62-4deb-ae4c-69ab1d8405eb' 
     
    06/16/2011 12:07:14.63  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    General   6t8d Verbose  
     Looking up the additional information about the typical site http://na00005d:8080/_vti_bin/webpartpages.asmx

    06/16/2011 12:07:14.63  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    General   6t8f Verbose  
    Site lookup is replacing http://na00005d:8080/_vti_bin/webpartpages.asmx with the alternate access url http://na00005d:8080.

    06/16/2011 12:07:14.63  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    General   6t8g Verbose  
     Looking up typical site http://na00005d:8080/_vti_bin/webpartpages.asmx in web application SPWebApplication Name=SharePoint - 8080 - IVWeb Parent=SPWebService. 

    06/16/2011 12:07:14.63  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    General   6t8h Verbose  
     Found typical site / (a616be71-a4a7-418c-b6df-bac0eda0c235) in web application SPWebApplication Name=SharePoint - 8080 - IVWeb Parent=SPWebService. 

    06/16/2011 12:07:14.63  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    General   8kh7 High     
     Cannot complete this action.  Please try again. 

    06/16/2011 12:07:14.64  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    Web Parts 89fh Monitorable 
     Usage: Security - Web Services: GetWebPartPageDocument 

    06/16/2011 12:07:14.64  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    General   8kh7 High     
     Cannot complete this action.  Please try again. 

    06/16/2011 12:07:14.64  w3wp.exe (0x18E0) 0x1464 Windows SharePoint Services    General   0 Verbose  
     Releasing SPRequest with allocation Id {C4B396C4-F26D-4ACB-A5AE-BBA003CB8E11} 

    Any ideas?

    Thursday, June 16, 2011 7:18 PM