none
Cannot Update existing infopath content types

    Question

  • I have a MOSS 2007 farm and am using Infopath 2010 for design.  Until recently, I've never had issues with content types, but lately if I try to make changes to an existing content type, the follow happens:

    • I get an error reading, "updating the content type failed."
    • If I go to the library where the .xsn is published, the modified date reflects that the changes did in fact occur.
    • The form will no longer open in the browser, I get the open/save/cancel prompt.  They're published as 2007 web browser forms properly, and they opened in the browser fine before the attempted update, but no longer after attempting the update.  The libraries using this content type still have the button checked to render in the browser.

    Because of this, any time a user wants a change to their form, I have to republish as a new content type, then go to each form library and point them to this new content type, which defeats the purpose of using content types in the first place.  Any advice would help...before you ask, I have no access to the logs and my farm host will not provide them. 


    paul truland

    Tuesday, April 30, 2013 5:23 PM

Answers

All replies

  • Hi Paul,

    Thank you for your question.  

    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.  

    Thank you for your understanding and support. 

    Thanks,


    Charlie Liao
    TechNet Community Support

    Wednesday, May 01, 2013 6:57 AM
  • Hi Paul,

    Do you have plenty of columns in the InfoPath Form template? There is a known issue that user will get timeout during publishing when form template tasks longer than 30 seconds to upload. And such InfoPath form often associated with multiple column promotions.

    For such issue, following resolutions are delivered.

    Solution1:

    Modify web.config, add “executionTimerout” attribute to the “httpRuntime” element as follows:
    <httpRuntime maxRequestLength="51200" executionTimeout="600" />

    Solution2:

    Install hotfix http://support.microsoft.com/kb/958139

    If you have workflow associated with the form library, also check this similar issue.
    http://social.msdn.microsoft.com/forums/en-US/sharepointcustomizationprevious/thread/a49883b3-181f-4805-be1f-39af5e5528d8

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please click here.


    Emir Liu
    TechNet Community Support


    Thursday, May 02, 2013 8:06 AM
  • There are only about 30 fields on the form, so I doubt that's it.  I'll request the hotfix be applied, I don't know whether or not it has been to this point.  There are no associated workflows. 

    paul truland

    Thursday, May 02, 2013 2:39 PM