InfoPath 2016

  1. The form template contains files that are not referenced in the form definition (.xsf) file or are referenced more than once. ...
  2. The form template could not be activated to the following site collection: {0}. You do not have the permissions required ...
  3. The form template could not be activated to the site collection. You do not have the permissions required to perform this ...
  4. The form template could not be deactivated from the following site collection: {0}. You do not have the permissions required ...
  5. The form template for "%1!s!" is already registered at different location (%2!s!). If you want to use the form template from ...
  6. The form template has been successfully initiated for removal from the farm. It may take a few minutes for the operation ...
  7. The form template has been successfully initiated for upgrade to the farm. It may take a few minutes for the upgrade to complete. ...
  8. The form template has been successfully initiated for upload to the farm. It may take a few minutes for the upload to complete. ...
  9. The form template has been successfully upgraded. The new version of the form template will automatically be available where ...
  10. The form template has been successfully uploaded to the farm. To make the form template available in a site collection, activate ...
  11. The form template is accessed through a redirection from a different domain, which is not allowed because it could cause ...
  12. The form template is missing a required XML Schema. The following schema is not referenced in the form definition (.xsf) ...
  13. The form template is not browser-compatible, perhaps as a result of modifications made outside of Microsoft InfoPath. It ...
  14. The form template is not browser-compatible. It might be possible to correct the problem by opening the form template in ...
  15. The form template is not browser-compatible. Use the Design Checker in InfoPath to change the compatibility mode and modify ...
  16. The form template is not valid. If you are working with a document library on a SharePoint site, you can modify the library's ...
  17. The form template is trying to access files and settings on your computer. (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) cannot grant ...
  18. The form was not submitted because a form named %1!s! already exists in the document library at %2!s!. Please contact the ...
  19. The form you are attempting to open may be located on a different server. This form can only be opened using Microsoft InfoPath. ...
  20. The form you are opening requires a new version of the form template. To upgrade the form template, close all the forms based ...
  21. The InfoPath form template for the selected content type cannot be loaded. The form template was not designed for InfoPath ...
  22. The language pack corresponding to the form locale "{0}" you have chosen has not been installed on the server. Text generated ...
  23. The merge cannot be started, because the merge feature is disabled for the selected form template. To fix this problem, contact ...
  24. The name of the following file, which is part of the form template, contains non-ASCII characters, the number sign (#), or ...
  25. The OpenIn query parameter, if present, must have one of the allowed values: 'Browser', 'Client', 'PreferClient' or 'Mobile'. ...
  26. The operation requested in the Soap message with soapAction %1 isn't defined in the WSDL file. This may be because it is ...
  27. The original form template for this form cannot be found.Another form template, "%1!s!", can be used to open the form. Do ...
  28. The parameterOrder attribute for operation %1 was invalid. It either did specify the same parts multiple times or not all ...
  29. The rich text field contains nested formatting which is not supported on InfoPath Forms Services. The formatting may be heavily ...
  30. The root element of the form definition (.xsf) file does not belong to the following namespace: http://schemas.microsoft ...
  31. The schema for the form template cannot be found. (!idspnExcel_NV) will create a schema based on the XML data in the form. ...
  32. The script running in this form is causing (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) to run slowly. If the script continues to ...
  33. The section is bound to the root node ({0}) of the data source. This can lead to effects that can only be evaluated on the ...
  34. The selected data file does not match the current form template. You can select a different data file, or you can preview ...
  35. The selected database connection saves passwords in a plain text file. Because plain text files are unencrypted and because ...
  36. The selected field or group contains characters in the XPATH definition that cannot be displayed in form library columns. ...
  37. The selected field or group contains characters in the XPATH definition that cannot be displayed in Web Part connection parameters. ...
  38. The selected file is too large and is causing the form to exceed the amount of allowable resources. Select another file. ...
  39. The selected Office data connection (.odc) file is missing required information. The following property is missing or invalid: ...
  40. The server could not verify browser compatibility of the form template because InfoPath Forms Services is not enabled for ...
  41. The server is currently being taken down for maintenance. Check with your system administrator to see when this server is ...
  42. The settings for one or more data connections in your form are defined in a data connection library on a Microsoft SharePoint ...
  43. The settings for one or more data connections in your form are defined in a data connection library on a Microsoft SharePoint ...
  44. The settings in the specified data connection file do not match the connection that you are converting. Choose a different ...
  45. The sign signature line rule action is not supported in Web browser forms. The rule will be ignored when the form is edited ...
  46. The sites listed have been shortened so that they can be displayed. For the full list of sites, contact the form author. ...
  47. The specified file name is formatted incorrectly. The file name must end with the .xsn file extension and cannot contain ...
  48. The specified form template could not be found, or is not compatible with rendering in the browser. It might need to be republished ...
  49. The specified location cannot be accessed. Check that the location you entered is correct and that you have appropriate permissions. ...
  50. The specified location does not exist or could not be opened. Choose a data connection library on a server running Microsoft ...
  51. The specified location is not a data connection library. Choose a data connection library on a server running Microsoft SharePoint ...
  52. The specified query did not return any data. You can revise the query, or you can click New Record to enter a new record. ...
  53. The specified URL cannot be used. This error could be caused by any of the following: the URL is not valid or uses a relative ...
  54. The specified values for the replaceChild call are not valid. (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) cannot replace a node with ...
  55. The specified varNode value and varViewContext value for the View.GetContextNodes call is not in the view or is in the view ...
  56. The specified XML template file (xsf:initialXmlDocument element) contains a urn reference that does not match the solutions ...
  57. The submit section (xsf:submit element) in the form definition (.xsf) file is missing the href attribute, or the attribute ...
  58. The submit section (xsf:submit element) in the form definition (.xsf) file is missing the method attribute or the attribute ...
  59. The submit section (xsf:submit element) in the form definition (.xsf) file specifies the following HTTP method, which is ...
  60. The update cannot be completed, because you do not have permission to modify the location where the template is installed. ...
  61. The update cannot continue because you have several %1 forms open. Please close all forms before continuing with the update. ...
  62. The updated form template is identified by the following URN: %1!s!. The original form template at this location was identified ...
  63. The URL {0} is an unsupported relative URL. To fix this problem, use a site-relative URL starting with '~site' or a site ...
  64. The value of an ID key or timestamp has been changed. ID keys and timestamp columns are automatically generated by the data ...
  65. The value of the 'namespace' attribute on an import element was '%1', matching the value of the enclosing schema's 'targetNamespace' ...
  66. The value of the DefaultDataConnectionTimeout property must not be greater than that of the MaxDataConnectionTimeout property. ...
  67. The value specified for the destination host (%1) is not valid. The value specified must be either a UNC path that includes ...
  68. The view (.xsl) file contains customized ID attributes. Because (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) automatically generates ...
  69. The view (.xsl) file creates an HTML file which includes a tag, which is not allowed.This can happen if the .xsl file has ...
  70. The view (.xsl) file creates an HTML file with an invalid tag, which is not allowed.This can happen if the .xsl file has ...
  71. The view (.xsl) file creates an HTML file with more than one tag, which is not allowed.This can happen if the .xsl file has ...
  72. The view contains an xd:binding attribute that is not valid. The xd:binding attribute cannot be bound by default to a CODE ...
  73. The view contains nested formatting which is not supported on InfoPath Forms Services. Examples of such formatting include ...
  74. The Web Part cannot find an InfoPath form in the specified location. Either the location does not have an InfoPath form associated ...
  75. The Web service returned data in a format that (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) does not understand. (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) ...