We have a bunch of archived reports in a document library which are linked to an Info path template. That template has become corrupted but luckily we have a working copy of this in a backup folder.

So we are looking to delete the corrupted XSN file and bring in the working XSN file, the problem is as follows:

  1. Cannot delete the corrupted XSN file, each time we delete it reappears!?
  2. If we raname the corrupted XSN file, all the related XML document files update their reference to the rename file!
  3. I CAN modify the XML files to point to the working XSN file and all is well But I have over 800 XML files which I would rather NOT have to manually edit

Anyone any ideas?

3 Answers 3


I think, you don't need to rename or delete the old one , only what you need to overwrite the corrupted templated with the backup template by

  • Open the backup template via InfoPath.
  • Try to publish it again to with the same name of old one to overwrite it.

Hope it helps you

  • Open working copy of template.xsn file from Info-path form designer
  • Check all data connection.
  • Publish to SharePoint libray.
  • Publish in existing library

If It still not work then

  1. Open working copy of template.xsn file from Info-path form designer
  2. Check all data connection.
  3. Publish to SharePoint libray.
  4. create new library while publishing.
  5. add existing records in library using power shell

I do not quite understand why are you deleting XSN file instead of opening your backuped XSN template, saving it and republishing from its backup copy (and then relinking XML forms to a newly published template)?

Related post you might find helpful:

Some other thoughts to try:

  • If the Infopath forms are set to be opened in Filler (it is in library settings, under advanced settings, to open the browser or client), you might want to try repairing Microsoft Infopath and/or clearing Infopath cache on (all) client machines
  • The main reason was that I had 700 xml files all referencing the XSN...worked out a way to do it though by runing a script on the XML to update them to point to working XSN. Thanks for your input.
    – Stephen
    Commented Jan 29, 2013 at 14:06

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.