none
Custom Editform.aspx crashes Sharepoint Designer

    Question

  • Hi there,

    I've recently designed a sharepoint list and customised newform.aspx and editform.aspx. I made copies of the originals then customised the copies.
    On both forms I simply:

    * Closed original List Form web part
    * Added Custom List Form
    * Added some section breaks (<tr>) to the form to break it into sections
    * Added a new css style to change the background colour on the section breaks (table rows)

    Now NewForm.aspx works fine. However after making above changes in EditForm.aspx, I saved it. However whenever I try to reopen EditForm.aspx in Sharepoint Designer (SD), SD crashes! I can only open it in Text view. The error details reported by SD are:

    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    SPDESIGN.EXE
      Application Version:    12.0.6423.1000
      Application Timestamp:    49b09947
      Fault Module Name:    FPEDITAX.DLL
      Fault Module Version:    12.0.6423.1000
      Fault Module Timestamp:    49b098d3
      Exception Code:    c0000005
      Exception Offset:    0010b35c
      OS Version:    6.0.6002.2.2.0.272.7
      Locale ID:    3081

    Additional information about the problem:
      LCID:    1033
      Brand:    Office12Crash
      skulcid:    1033


    I really don't know why SD is crashing. As a test I made a new copy of original Editform.aspx. I added in the custom list form, but didn't edit the custom list form. Saved it, and can re-open it no problem. So the custom list form isn't the cause. It seems to be my adding a row that bugs out the form - but the row just contains text, and has a css style applied.

    Funnily enough, the EditForm works Ok via the web interface. I just can't open it with SD after making those simple changes.
    However, the 'Attach file' option doesn't work on the EditForm page, yet it works fine on the NewForm page.

    Please help! Any help would be really appreciated.
    Thank you in advance.


    Steve

    Update: I've just tried a more basic modification to see if it still ends up crashing SD. The following modification still crashes SD:
    1) Create copy of Editform.aspx
    2) Close List Form Web Part in new file
    3) Add Custom List Form below LFWP
    4) Add new table row anywhere in Custom List Form
    5) Save and then close file
    6) Re-open file --> Crashes Sharepoint Designer

    This is running Sharepoint Designer with Office 2007 SP2.
    Thursday, December 10, 2009 11:13 AM

All replies

  • Hi,

     

    I am sorry I cannot reproduce the issue, could you please provider me more information for further research?\

     

    1.     How did you add new table row? I added <tr> and <td> flag in the custom list form, it is well.

    2.     Have you done any other customization in the page?

     

    Let me know the result.


    Xue-Mei Chang
    Tuesday, December 15, 2009 8:45 AM
    Moderator
  • I have also run into this exact same issue. Editing a Custom List Form works for the most part, but when I start adding rows to a table, or even splitting a cell into two rows will trigger it.

    I had to basically start over with the form, as I couldn't open the page in SPD, and opening in something else, while possible, left me only guessing as to what might have triggered the crashing. I have saved copies of the page after minor changes to see what things cause the crash. It's consistently adding rows or splitting cells of a table. I can very easily reproduce this. In fact, I was able to reproduce it on a separate PC. My main notebook runs Win7 64-bit, so thinking that it might be a quirk there, I went over to an XP 32-bit PC, opened SPD, pulled up a totally different dev site to ensure it was completely different and sure enough, it was the exact same thing.

    I typically work in design mode. I have not added the rows via code. Perhaps that's the workaround, but just wanted to confirm that this is indeed an issue that can be readily reproduced. Right-click a table row, Insert - Row Above. Save the file, close the file, view it in a browser and it shows the change just fine, but trying to reopen the file in SPD causes insta-crash.
    Thursday, February 04, 2010 4:21 AM
  • I have exactly the same issues as Furo. Does Microsoft have any solution? We are in 2010 and SPD was released in 2007.
    Saturday, February 13, 2010 1:58 AM
  • Hi there,

    I've recently designed a sharepoint list and customised newform.aspx and editform.aspx. I made copies of the originals then customised the copies.
    On both forms I simply:

    * Closed original List Form web part
    * Added Custom List Form
    * Added some section breaks (<tr>) to the form to break it into sections
    * Added a new css style to change the background colour on the section breaks (table rows)

    Now NewForm.aspx works fine. However after making above changes in EditForm.aspx, I saved it. However whenever I try to reopen EditForm.aspx in Sharepoint Designer (SD), SD crashes! I can only open it in Text view. The error details reported by SD are:

    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    SPDESIGN.EXE
      Application Version:    12.0.6423.1000
      Application Timestamp:    49b09947
      Fault Module Name:    FPEDITAX.DLL
      Fault Module Version:    12.0.6423.1000
      Fault Module Timestamp:    49b098d3
      Exception Code:    c0000005
      Exception Offset:    0010b35c
      OS Version:    6.0.6002.2.2.0.272.7
      Locale ID:    3081

    Additional information about the problem:
      LCID:    1033
      Brand:    Office12Crash
      skulcid:    1033


    I really don't know why SD is crashing. As a test I made a new copy of original Editform.aspx. I added in the custom list form, but didn't edit the custom list form. Saved it, and can re-open it no problem. So the custom list form isn't the cause. It seems to be my adding a row that bugs out the form - but the row just contains text, and has a css style applied.

    Funnily enough, the EditForm works Ok via the web interface. I just can't open it with SD after making those simple changes.
    However, the 'Attach file' option doesn't work on the EditForm page, yet it works fine on the NewForm page.

    Please help! Any help would be really appreciated.
    Thank you in advance.


    Steve

    Update: I've just tried a more basic modification to see if it still ends up crashing SD. The following modification still crashes SD:
    1) Create copy of Editform.aspx
    2) Close List Form Web Part in new file
    3) Add Custom List Form below LFWP
    4) Add new table row anywhere in Custom List Form
    5) Save and then close file
    6) Re-open file --> Crashes Sharepoint Designer

    This is running Sharepoint Designer with Office 2007 SP2.

    Same problem here.  It doesn't matter whether running on XP or Windows 7 and it doesn't matter if SPD is SP1 or SP2.  What may matter is the level of the site.  I tried on MOSS2007 SP1 w/infrastructure update and WSS 3.0 w/SP2 and get the problem.  One thing that is different, is that when right clicking on the ListFormWebPart and choosing Web Part Properties to hide the WebPart I get a the EditForm.aspx page rendered in the WebPart properties dialog instead of the WebPart properties that would be expected.  I also get various crashes when attempting to add any xslt to the code view of the form.  SPD and LFWP's are VERY buggy from what I am experiencing.

    Is there a fix for this or are we all just out of luck and expected to shut up and upgrade to 2010 when it comes out?
    Wednesday, February 24, 2010 11:53 PM
  • Normally, I'm not one to really say much about this stuff, but SharePoint developers shouldn't HAVE TO wait to get any support on such a fundamental part of the only development tool Microsoft allowed access to for SharePoint remotely.  Even this they eventually changed to being "free" because they knew that it was buggy and it was a concession to the enterprise license holders.... IMHO.  As a web developer there are 3 major problems right now regarding custom development for SharePoint.

    1.  No debug support from Visual Studio 2008 unless you are running off *the server running SharePoint*....  Wha?!?!
    2.  For custom web parts or customized site definitions, you need to package it up on your development box and hope the server admin deploys it properly on the server.... if they will even do it....it's even worse if your site collection is on a farm.
    3.  Not a lot of support or information for storing the solutions created in Visual Studio 2008 to TFS 2008 so you can have any kind of source control on it.

    Since I don't believe in a good rant without some providing some suggestions:
    1.  There needs to be some kind of windows service/port combination that allows the developers to be able to connect to their sites from their Windows XP Professional development machine to the SharePoint 2007/2010 server and debug in Visual Studio 2008/2010.  *NO EXCEPTIONS*
    2.  A way to publish your newly created web part or site definition to your site collection if you are the site collection owner...in other words, you don't need admin rights on the server or farm box to get your stuff deployed
    3.  A better forum for the support tools that Microsoft provides..... from an integration standpoint.  This means that when I have SharePoint Designer 2007 for customizing SharePoint views, Expression Suite for designing custom graphics, and Visual Studio 2008 for applications with SharePoint 2007 API calls -- the fundamental chassis *.DLL files don't clobber one another.  When you contact the Microsoft application support forums it's pretty common to be treated to a strange game of hot-potato where you get bounced from one application support forum to another because they're not really sure if it's their application or another one that's causing it, but it's a tough and DEEP problem that keeps breaking one or more applications so nobody wants to address it even though the problem hasn't gone away.


    I sincerely hope these issues are being addressed in the 2010 versions of the Microsoft products, but the only way to tell is to wait and see what happens....  Good luck!  :)
    Tuesday, March 16, 2010 6:33 PM
  • I found this -->  http://ph-tom.blogspot.com/2010/04/microsoft-office-sharepoint-designer.html 

    I have a custom form that gives "Microsoft Sharepoint Designer has stopped working."  I have already rebuilt it 3 times.

    I have tried single clicking on the file in the folder view (to the left).   Then, I go to the menu - View - Page - Code.   Nothing happens.

    If someone can get the the procedure at the link to work, please reply as to what I am missing.

    Thanks!

    Wednesday, April 21, 2010 10:11 PM
  • I've also struck this whenever I customise (do anything at all, add row, delete row) in a List form.

    Another method I've tried is to create a new set of list forms, (Newform_copy,Editform_copy,Dispform_copy) customised them, and redirected the library to them  (right click list/library in folders tab, select Properties, then Supporting Files tab)

    This method also crashes SPD, though not every time, which I can't work out.

     

    Thursday, April 29, 2010 3:46 AM
  • I am seeing the same problem. Whether I create a custom list form from scratch or copy an existing form and edit it, I only have one shot at it. Once I save the form, that's it, I can't reopen it without crashing SPD. I've moved from XP to W7 and tried uninstalling and reinstalling SPD and it hasn't made a bit of difference. It just crashes and crashes and crashes.
    Wednesday, June 09, 2010 11:36 PM
  • hey i have some problem , when am trying to add a list to the dataform web part . SPD is crashing.

     

    and it says

    Problem signature:
      Problem Event Name:    APPCRASH
      Application Name:    SPDESIGN.EXE
      Application Version:    12.0.6423.1000
      Application Timestamp:    49b09947
      Fault Module Name:    FPEDITAX.DLL
      Fault Module Version:    12.0.6423.1000
      Fault Module Timestamp:    49b098d3
      Exception Code:    c0000005
      Exception Offset:    0030b6a8
      OS Version:    6.0.6002.2.2.0.274.10
      Locale ID:    1033

    Additional information about the problem:
      LCID:    1033
      Brand:    Office12Crash
      skulcid:    1033


    Share Knowledge and Spread Love!
    Tuesday, June 15, 2010 2:16 PM
  • Smae here... SPD crashes when I try to create a custom from.  It happens when I click on Show Data on the Data sources section.  The event viewer logged this:

    Office Diagnostics:

    Event Type: Error
    Event Source: Microsoft Office 12 Sessions
    Event Category: None
    Event ID: 7001
    Date:  7/27/2010
    Time:  5:34:58 PM
    User:  N/A
    Computer: KOTAPALLYS
    Description:
    ID: 7, Application Name: Microsoft Office SharePoint Designer, Application Version: 12.0.6423.1000, Microsoft Office Version: 12.0.6425.1000. This session lasted 101 seconds with 60 seconds of active time.  This session ended with a crash.
     

    System

    Event Type: Error
    Event Source: Microsoft Office 12
    Event Category: None
    Event ID: 1000
    Date:  7/27/2010
    Time:  5:33:08 PM
    User:  N/A
    Computer: KOTAPALLYS
    Description:
    Faulting application spdesign.exe, version 12.0.6423.1000, stamp 49b09947, faulting module fpeditax.dll, version 12.0.6423.1000, stamp 49b098d3, debug? 0, fault address 0x0030b6a8.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Data:
    0000: 41 00 70 00 70 00 6c 00   A.p.p.l.
    0008: 69 00 63 00 61 00 74 00   i.c.a.t.
    0010: 69 00 6f 00 6e 00 20 00   i.o.n. .
    0018: 46 00 61 00 69 00 6c 00   F.a.i.l.
    0020: 75 00 72 00 65 00 20 00   u.r.e. .
    0028: 20 00 73 00 70 00 64 00    .s.p.d.
    0030: 65 00 73 00 69 00 67 00   e.s.i.g.
    0038: 6e 00 2e 00 65 00 78 00   n...e.x.
    0040: 65 00 20 00 31 00 32 00   e. .1.2.
    0048: 2e 00 30 00 2e 00 36 00   ..0...6.
    0050: 34 00 32 00 33 00 2e 00   4.2.3...
    0058: 31 00 30 00 30 00 30 00   1.0.0.0.
    0060: 20 00 34 00 39 00 62 00    .4.9.b.
    0068: 30 00 39 00 39 00 34 00   0.9.9.4.
    0070: 37 00 20 00 69 00 6e 00   7. .i.n.
    0078: 20 00 66 00 70 00 65 00    .f.p.e.
    0080: 64 00 69 00 74 00 61 00   d.i.t.a.
    0088: 78 00 2e 00 64 00 6c 00   x...d.l.
    0090: 6c 00 20 00 31 00 32 00   l. .1.2.
    0098: 2e 00 30 00 2e 00 36 00   ..0...6.
    00a0: 34 00 32 00 33 00 2e 00   4.2.3...
    00a8: 31 00 30 00 30 00 30 00   1.0.0.0.
    00b0: 20 00 34 00 39 00 62 00    .4.9.b.
    00b8: 30 00 39 00 38 00 64 00   0.9.8.d.
    00c0: 33 00 20 00 66 00 44 00   3. .f.D.
    00c8: 65 00 62 00 75 00 67 00   e.b.u.g.
    00d0: 20 00 30 00 20 00 61 00    .0. .a.
    00d8: 74 00 20 00 6f 00 66 00   t. .o.f.
    00e0: 66 00 73 00 65 00 74 00   f.s.e.t.
    00e8: 20 00 30 00 30 00 33 00    .0.0.3.
    00f0: 30 00 62 00 36 00 61 00   0.b.6.a.
    00f8: 38 00 0d 00 0a 00         8..... 

    Tuesday, July 27, 2010 10:01 PM
  • Is there an answers for this. Sharepoint desinger is consistently crashhing wehn I try to opne a custom form.
    Tuesday, August 24, 2010 1:45 PM
  • Hi all,

    I'm the original creator of this thread. This issue seemed to be caused by the whole bad code thing that stops attachments working on customized forms.

    From what I could see, every time that I modified a form, SD would add bad code to the form which breaks the functionality of attachments (this is well documented). If you then save that form (with the bad code) it will crash many implementations of SD when you try to re-open the file.


    My workaround was to correct the bad code each and every time that I saved the form. The bad code is:

     

    					<tr id="idAttachmentsRow{generate-id()}">
    						<td nowrap="true" valign="top" class="ms-formlabel" width="20%">
    							<SharePoint:FieldLabel ControlMode="Edit" FieldName="Attachments" runat="server"/>
    						</td>
    						<td valign="top" class="ms-formbody" width="80%">
    							<SharePoint:FormField runat="server" id="AttachmentsField{$Pos}" ControlMode="Edit" FieldName="Attachments" __designer:bind="{ddwrt:DataBind('u',concat('AttachmentsField',$Pos),'Value','ValueChanged','ID',ddwrt:EscapeDelims(string(@ID)),'@Attachments')}"/>
    							<script></script> </td>
    					</tr>
    

     

    Replace with:

    					<tr id="idAttachmentsRow">
    						<td nowrap="true" valign="top" class="ms-formlabel" width="20%">
    							<SharePoint:FieldLabel ControlMode="Edit" FieldName="Attachments" runat="server"/>
    						</td>
    						<td valign="top" class="ms-formbody" width="80%">
    							<SharePoint:FormField runat="server" id="AttachmentsField" ControlMode="Edit" FieldName="Attachments" __designer:bind="{ddwrt:DataBind('u','AttachmentsField','Value','ValueChanged','ID',ddwrt:EscapeDelims(string(@ID)),'@Attachments')}"/>
    							<script>
       						var elm = document.getElementById("idAttachmentsTable");
       						if (elm == null || elm.rows.length == 0)
       						document.getElementById("idAttachmentsRow").style.display='none';
      					</script> </td>
    					</tr>
    

     

    This will fix up the attachments functionality also - but make sure that EVERY time you edit the form, that you do not save it without first checking the above code. Bad code is inserted almost every time that I edit a file with SD.

    It's a pain in the neck but I hope it helps everyone.

    • Proposed as answer by JTMiles Tuesday, July 15, 2014 7:56 PM
    Friday, August 27, 2010 5:15 AM
  • I wrote a post on how to do this a while ago. It is very quirky to change those files.
    http://www.techelixir.com/sn/Lists/Posts/Post.aspx?List=c2743b4c%2D2c08%2D4f02%2D9c90%2D1e7ba0c1f044&ID=4

    Let me know if that helps.
    vr,
    SharePointNinja

    Tuesday, August 31, 2010 4:36 AM
  • I am experiencing this issue as well.  I am unable to reproduce it predictably; however, SP Designer 2010 when I am editing a form and save it.  So it may be reproducible if you open SP Designer and try to make changes, save, more changes... save again and continue until it fails.  Furthermore, I encourage anyone encountering this to select the "look for a solution' button so as to send appropriate data to Microsoft for debugging. 

     

    Thanks!

    Saturday, September 18, 2010 3:17 PM
  • I notice this topic started in December '09

    Is all of the above only applicable to SharePoint Designer 2007?

    Was this fixed in SPD 2010 / SharePoint Foundation ?

    Should I be wary of this issue as our company steps into SharePoint solution development for our intranet?

    EDIT: .. oh, I just now saw the forum cookie trail (pre-2010) .. but, I still wonder if SPD 2010 has resolved this issue.

    Friday, November 12, 2010 3:40 PM
  • When I click on the link provided here, the link does not display anymore "Internet Explorer cannot display the webpage"

    Tuesday, April 03, 2012 1:26 PM
  • Hi all,

    I have the same issue with SD 2010 that goes in hang also if I don't edit anymore :(

    I have only a doubt about SD and SharePoint version conflict (also if is strange) because the first is 32bit the second 64bit....

    If someone has update about this issue, please insert a possible solution....

    Kind Regards


    FabioA

    Friday, July 13, 2012 8:08 AM
  • Here we are in 2013 and this stuff is still happening.  SPD should be scrapped entirely if it cannot be stable.  I have the same issue.  Created a run of the mill custom list.  Went into SPD and made a copy of the NewForm.aspx page.  Opened it up in Advanced mode.  Tried to insert a custom new form so I could make modifications to the XSLT and EVERY TIME I try this SPD crashes.  My company is already considering moving off of SharePoint because of all of the bad apps local contractors and partners have created for us.  Buggy development/design tools doesn't help my case.

    Thursday, February 21, 2013 2:53 PM
  • Hi,

    This is still an issue with 2007. I haven't run into it yet in 2010, myself. It will cause problems and lo and behold - one day the files will open as if they had all along? Very strange! Some sites yes, some no, all on the same server.

    jmiles


    John Miles Technical Director Harvest America Corporation

    Tuesday, July 15, 2014 7:59 PM
  • And still in 2014!

    John Miles Technical Director Harvest America Corporation

    Tuesday, July 15, 2014 8:00 PM