InfoPath 2013

  1. The form cannot be submitted because of an error with the file attachments. To fix this problem, contact the form designer. ...
  2. The form cannot be submitted because some of the email addresses cannot be resolved. If you know the values in the form that ...
  3. The form cannot be submitted because the form view contains errors. For more information, contact the site administrator. ...
  4. The form cannot be submitted because this action would violate cross-domain restrictions.If this form template is published ...
  5. The form cannot be submitted to the specified SharePoint document library. The document library already contains a file with ...
  6. The form cannot be submitted to the specified SharePoint list or document library. The SharePoint location may be read-only ...
  7. The form cannot be submitted to the Web server either because your computer is offline or because the host server is currently ...
  8. The form cannot be submitted, because it contains validation errors. Before fixing the errors, remove all digital signatures ...
  9. The form cannot be updated because it is in use by another application. Wait for the other application to finish using the ...
  10. The form contains changes that must be processed before it can be printed. Click OK to update the form, and then try printing ...
  11. The form contains changes that must be processed before it can be signed. Click OK to update the form, and then try signing ...
  12. The form contains changes that must be processed before it can download file. Update the form, and then try downloading again. ...
  13. The form could not be opened. The system administrator has applied a policy setting to this machine which prevents opening ...
  14. The form data cannot be signed because the signature contains nested structures that InfoPath Forms Services does not support. ...
  15. The form definition (.xsf) file contains a button name that occurs more than once in a single view.Button name: %1!s!View: ...
  16. The form definition (.xsf) file contains the following error: The name attribute of the xmlToEdit element is longer than ...
  17. The form definition (.xsf) file contains the following error:Illegal value %1!s! for match attribute of %2!s! declaration ...
  18. The form definition (.xsf) file contains two view elements that have the same caption or name attribute. Each view element ...
  19. The form definition (.xsf) file does not specify an XML document, and the following element does not reference a schema: ...
  20. The form definition (.xsf) file has an error on the following element or attribute: %3!s!Error: %1!s!%2!s! in the xmlToEdit ...
  21. The form definition (.xsf) file has an error on the following element or attribute: %3!s!Error: %1!s!%2!s! in the xmlToEdit ...
  22. The form definition (.xsf) file is missing a required attribute in the error condition section (xsf3:errorBlank element). ...
  23. The form definition (.xsf) file is missing a required attribute in the error condition section (xsf:errorCondition element). ...
  24. The form definition (.xsf) file is missing the following attribute in the error section (xsf:errorCondition or xsf:errorMessage ...
  25. The form definition (.xsf) file references other files in the form with absolute paths. Only relative paths are supported. ...
  26. The form definition (.xsf) file refers to the following script file, but no such script file can be found in the form: %1 ...
  27. The form definition (.xsf) file specifies that save functionality will be defined in code, but the code does not define an ...
  28. The form definition (.xsf) file specifies that submit functionality will be defined in code, but the code does not define ...
  29. The form definition (.xsf) file specifies that submit functionality will be defined in code, but the code does not define ...
  30. The form has been saved.To add or update this form in (!idspnSharePointWorkspace): select "Import Form" if this is a new ...
  31. The form ID should be entered in the following format:Urn: : To see an example, or to generate a valid form ID, press the ...
  32. The form is accessed through a redirection from different domain, which is not allowed. If you want to open this form, copy ...
  33. The form library publish location does not exist. To publish the form again, click the File tab, open the Publish tab, and ...
  34. The form load time ({0}) has exceed the maximum configured threshold. This threshold can be configured by using the SPIPFormsService ...
  35. The form location and content type cannot be modified because these values are provided by another Web Part on the page. ...
  36. The form template associated with this form cannot be found. It is not on your computer and the form does not specify a location ...
  37. The form template associated with this form has moved or cannot be accessed. There is a form template, "%1!s!," on your computer ...
  38. The form template associated with this form was moved or cannot be accessed. The form template "%1!s!" on your computer has ...
  39. The form template cannot be opened inside the hosting environment because it uses Information Rights Management. To open ...
  40. The form template cannot be opened, because the system administrator has disabled opening form templates that require full ...
  41. The form template cannot be opened.The form template you are trying to open has the same ID as another form template on your ...
  42. The form template cannot be published because the (!idspnSharePoint) list or site content type settings folder could not ...
  43. The form template cannot be published because the Web service for updating the (!idspnSharePoint) list and site content type ...
  44. The form template cannot be published because your computer is not connected to the network. Check your network connection ...
  45. The form template cannot be published to the following location: %1.Only site collection administrators can publish sandboxed ...
  46. The form template cannot be published to the server: %1.Sandboxed solutions are not enabled on the (!idspnSharePoint) server ...
  47. The form template cannot be upgraded because the file name has changed since the previous version. Rename the file name to ...
  48. The form template cannot use data connection settings from more than one site collection. Remove data connections that reference ...
  49. The form template code is incompatible with %1. On the Developer tab, in the Code group, click Language, click Remove Code, ...
  50. The form template code language is incompatible with %1. On the Developer tab, in the Code group, click Language, click Change ...
  51. The form template contains files that are not referenced in the form definition (.xsf) file or are referenced more than once. ...
  52. The form template contains one or more data connections that access XML files on the local computer. To enable this data ...
  53. The form template could not be activated to the following site collection: {0}. You do not have the permissions required ...
  54. The form template could not be activated to the site collection. You do not have the permissions required to perform this ...
  55. The form template could not be deactivated from the following site collection: {0}. You do not have the permissions required ...
  56. The form template for "%1!s!" is already registered at different location (%2!s!). If you want to use the form template from ...
  57. The form template has been published to the server but it can only be opened in (!idspnInfoPathEditor).%1There may be additional ...
  58. The form template has been published to the server but it can only be opened in the (!idspnInfoPathEditor) because it contains ...
  59. The form template has been published to the server but it can only be opened in the (!idspnInfoPathEditor).Try publishing ...
  60. The form template has been successfully initiated for removal from the farm. It may take a few minutes for the operation ...
  61. The form template has been successfully initiated for upgrade to the farm. It may take a few minutes for the upgrade to complete. ...
  62. The form template has been successfully initiated for upload to the farm. It may take a few minutes for the upload to complete. ...
  63. The form template has been successfully upgraded. The new version of the form template will automatically be available where ...
  64. The form template has been successfully uploaded to the farm. To make the form template available in a site collection, activate ...
  65. The form template is a browser-compatible form. If the form is published to a server running InfoPath Forms Services, it ...
  66. The form template is accessed through a redirection from a different domain, which is not allowed because it could cause ...
  67. The form template is missing a required XML Schema. The following schema is not referenced in the form definition (.xsf) ...
  68. The form template is not browser-compatible, perhaps as a result of modifications made outside of Microsoft InfoPath. It ...
  69. The form template is not browser-compatible. It might be possible to correct the problem by opening the form template in ...
  70. The form template is not browser-compatible. Use the Design Checker in InfoPath to change the compatibility mode and modify ...
  71. The form template is not valid. If you are working with a document library on a SharePoint site, you can modify the library's ...
  72. The form template is requesting domain trust permissions. Domain trust forms will not have sufficient security permissions ...
  73. The form template is requesting domain trust permissions. Domain trust forms will not have sufficient security permissions ...
  74. The form template is trying to access files and settings on your computer. (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) cannot grant ...
  75. The form template must be published to a location on the same site as the content type. It is recommended that it be published ...