InfoPath 2013

  1. The selected XML Schema contains one or more elements that (!idspnInfoPath) does not support. The unsupported elements will ...
  2. The selected XML Schema contains one or more required elements that are recursive. Because (!idspnInfoPath) does not support ...
  3. The selected XML Schema specifies one or more namespaces that are already in use in this form template by another XML Schema. ...
  4. The server administrator must enable the form template for use in a browser before users will be able to open the form in ...
  5. The server could not verify browser compatibility of the form template because InfoPath Forms Services is not enabled for ...
  6. The server is currently being taken down for maintenance. Check with your system administrator to see when this server is ...
  7. The server is running (!idspnInfoPathFormsServices), but the compatibility setting for this form template is (!idspnInfoPath) ...
  8. The settings for one or more data connections in your form are defined in a data connection library on a Microsoft SharePoint ...
  9. The settings for one or more data connections in your form are defined in a data connection library on a Microsoft SharePoint ...
  10. The settings in the specified data connection file do not match the connection that you are converting. Choose a different ...
  11. The sign signature line rule action is not supported in %1!s! forms.The rule will be ignored when the form is edited in a ...
  12. The sign signature line rule action is not supported in Web browser forms. The rule will be ignored when the form is edited ...
  13. The source of this issue has been removed from the form template. To check the template for additional issues, click Refresh. ...
  14. The specified file name is formatted incorrectly. The file name must end with the .xsn file extension and cannot contain ...
  15. The specified form template could not be found, or is not compatible with rendering in the browser. It might need to be republished ...
  16. The specified location cannot be accessed. Check that the location you entered is correct and that you have appropriate permissions. ...
  17. The specified location does not exist or could not be opened. Choose a data connection library on a server running Microsoft ...
  18. The specified location is not a data connection library. Choose a data connection library on a server running Microsoft SharePoint ...
  19. The specified query did not return any data. You can revise the query, or you can click New Record to enter a new record. ...
  20. The specified task pane cannot be displayed. Either the task pane cannot be displayed when the form is open in the current ...
  21. 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 ...
  22. The specified values for the replaceChild call are not valid. (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) cannot replace a node with ...
  23. The specified varNode value and varViewContext value for the View.GetContextNodes call is not in the view or is in the view ...
  24. The specified XML template file (xsf:initialXmlDocument element) contains a urn reference that does not match the solutions ...
  25. The SQL statement cannot be represented as a tree view. To remove the SQL statement, click Edit SQL, and then delete the ...
  26. The structure of the selected .xml file will provide the data source for your form template. Do you also want to use the ...
  27. The submit operation for the Web service requires the following parameters. Specify which fields or groups in your form provide ...
  28. The submit operation for the Web service requires the parameters listed below. You can specify which elements in your form ...
  29. The submit section (xsf:submit element) in the form definition (.xsf) file is missing the href attribute, or the attribute ...
  30. The submit section (xsf:submit element) in the form definition (.xsf) file is missing the method attribute or the attribute ...
  31. The submit section (xsf:submit element) in the form definition (.xsf) file specifies the following HTTP method, which is ...
  32. The update cannot be completed, because you do not have permission to modify the location where the template is installed. ...
  33. The update cannot continue because you have several %1 forms open. Please close all forms before continuing with the update. ...
  34. The updated form template is identified by the following URN: %1!s!. The original form template at this location was identified ...
  35. The URL {0} is an unsupported relative URL. To fix this problem, use a site-relative URL starting with '~site' or a site ...
  36. The value of an ID key or timestamp has been changed. ID keys and timestamp columns are automatically generated by the data ...
  37. The value of the 'namespace' attribute on an import element was '%1', matching the value of the enclosing schema's 'targetNamespace' ...
  38. The value of the DefaultDataConnectionTimeout property must not be greater than that of the MaxDataConnectionTimeout property. ...
  39. The value specified for the destination host (%1) is not valid. The value specified must be either a UNC path that includes ...
  40. The view %1!s! cannot be updated. Modify the xsf:view entry in the form definition file (.xsf) to include design-mode="protected" ...
  41. The view (.xsl) file contains customized ID attributes. Because (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) automatically generates ...
  42. The view (.xsl) file creates an HTML file which includes a tag, which is not allowed.This can happen if the .xsl file has ...
  43. The view (.xsl) file creates an HTML file with an invalid tag, which is not allowed.This can happen if the .xsl file has ...
  44. 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 ...
  45. The view cannot be refreshed, because the form template was removed from your computer. To fix this problem, make sure that ...
  46. The view contains an xd:binding attribute that is not valid. The xd:binding attribute cannot be bound by default to a CODE ...
  47. The view contains nested formatting which is not supported on InfoPath Forms Services. Examples of such formatting include ...
  48. The Web Part cannot find an InfoPath form in the specified location. Either the location does not have an InfoPath form associated ...
  49. The Web service returned data in a format that (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) does not understand. (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) ...
  50. The word cannot be added to the custom dictionary because no custom dictionary can be found or the custom dictionary is full. ...
  51. The XML data returned from the data source does not match the XML Schema for this form. This discrepancy might be caused ...
  52. The XML file %1 referenced a schema that was missing or invalid. (!idspnInfoPath) will generate a new schema for this form ...
  53. The XML Schema contains one or more elements with a complexType that references an optional element more than once. This ...
  54. The XML Schema contains whitespace characters in the following namespace declaration: %1!s!(!idspnInfoPath) does not support ...
  55. The XML Schema of the form template is either invalid or contains a structure that (!XDOCS_APP_SHORT_NAME_PLACEHOLDER) does ...
  56. The XML Schema or XML document cannot be used because (!idspnInfoPath) does not support adding complete XML Schemas without ...
  57. The XML Schema you selected cannot be added because it contains structures that (!idspnInfoPath) cannot completely support ...
  58. The XML template file (specified in the xsf:initialXmlDocument element of the form template definition file) has a processing ...
  59. The XmlFormView Control cannot be loaded because the AspCompat property of the aspx page is set to true. XmlFormView is not ...
  60. The XPath functions xdEnvironment:IsMobile and xdEnvironment:IsBrowser are not supported in (!idspnInfoPath_Short_2003). ...
  61. The XPath must point to a field or group in the data source, or more than one field or group separated by the 'or' operator ...
  62. The xsf:script element in the form definition (.xsf) file is missing the following src attribute, or the attribute is not ...
  63. The xsl:stylesheet element had multiple xsl:template elements with no mode attribute. This is not supported. Using only the ...
  64. The _Startup or _Shutdown method in this form's code contains one or more calls to members of the Microsoft.Office.Interop.InfoPath.SemiTrust ...
  65. There are no digital signatures associated with this form. Before you submit the form, it is recommended that you sign it. ...
  66. There has been an error while loading the form because the fields in the form and SharePoint list do not match. Contact the ...
  67. There has been an error while loading the form. A required resource could not be downloaded. To try to resume the download, ...
  68. There is a control bound to a descendant ({0}) of this control's binding ({1}). But that control is not within this control ...
  69. There is a control within this control that is bound to a field or group ({0}) that is not a descendant of this control's ...
  70. There is a problem with the Web server. Make sure the Web server exists, try again later or contact the Web server administrator. ...
  71. There is a section or table bound to an ancestor ({0}) of this control's binding ({1}). But this control is not within that ...
  72. There is already a more recent version of this form template on the server. Either remove the existing form template from ...
  73. There was an error creating a document to print this form with (!idspnWord_NV). To print the form in InfoPath instead, click ...
  74. There was an unexpected error during field recognition.To fix this problem, import the document again with the "form layout ...
  75. These properties indicate the security settings for this form template. Trust level is either domain trust or full trust. ...