InfoPath 2016

  1. One or more required components of (!idspnInfoPath) or the form template cannot run because of a security restriction.Contact ...
  2. Only durations are allowed. For example, to enter a duration of 0 years, 5 months, 16 days, 4 hours, 22 minutes, and 21 seconds, ...
  3. Other controls are bound to the same field or group ({0}). This can lead to effects that can be evaluated only on the server.{1} ...
  4. Parts of this form are digitally signed and cannot be modified. To modify those parts of the form, remove the associated ...
  5. Performing this task requires elevated privileges. You must be a member of the local administrators group and run the browser ...
  6. Performs maintenance operations on administrator-approved InfoPath Forms Services form templates across all front-end Web ...
  7. Permission for this form is currently restricted and there is another non-restricted form of the same solution opened. Close ...
  8. Policy settings prevent opening Internet forms with managed code. To fix this problem, contact your system administrator. ...
  9. Preserve code blocks are not supported by InfoPath Forms Services.To publish this form, you must remove the preserve code ...
  10. Printing headers and footers is not supported in server forms. The form printed from the browser will not have a header or ...
  11. Prompting the user to save changes during the 'Close the form' action is not supported by InfoPath Forms Services.When the ...
  12. Relationships between the following columns are in errorParent table: %1!s!Parent columns: %2!s!Child table: %3!s!Child columns: ...
  13. Relationships between the following columns are in errorParent table: %1Parent columns: %2Child table: %3Child columns: %4 ...
  14. Relative paths to files that are not listed in the Resource Files dialog box are not supported. Enter an absolute path to ...
  15. Returns a specific part of a text string. The second argument specifies the starting position and the third argument specifies ...
  16. Returns the address of the (!idspnSharePoint) server where the form is hosted ((!idspnInfoPath_Short_2010) and greater). ...
  17. Returns the address of the (!idspnSharePoint) site collection where the form is hosted ((!idspnInfoPath_Short_2010) and greater). ...
  18. Returns the first text string with each character in the second text string replaced by the character at the corresponding ...
  19. Returns the index (or position) of a field or group with respect to the other fields and groups in the same parent group. ...
  20. Returns the values of a field or group. The second argument defines the expression to calculate for the field or group. Usually, ...
  21. Save using custom code is not supported in InfoPath Forms Services.To fix this problem, remove this event and its related ...
  22. Security Warning: This form may use your identity to connect to data sources. At least one of these data sources is on a ...
  23. Some controls in this form will send data to the server whenever their values change. To see more details, open the form ...
  24. Some form data cannot be retrieved because InfoPath is operating in offline mode. Form elements, such as drop-down lists, ...
  25. Some form data cannot be retrieved because Internet Explorer is operating in offline mode. Form elements, such as drop-down ...
  26. Some form data may not be retrieved because Internet Explorer is operating in offline mode. Form elements, such as drop-down ...
  27. Specify default and maximum timeouts for data connections from browser-enabled form. The connection timeout can be changed ...
  28. Specify the list of user agents that, for indexing purposes, will receive InfoPath forms as XML files instead of full Web ...
  29. Specify time and data limits for user sessions. User session data is stored by the Microsoft SharePoint Server State Service. ...
  30. Submit functionality is disabled for forms that are published to the server. Users can query and edit data but cannot submit ...
  31. Submitting through e-mail is not supported in sandboxed solutions. To publish this form to SharePoint, use the administrator-approved ...
  32. Submitting to a hosting environment through code is not supported in sandboxed solutions. If your form submits to a hosting ...
  33. Support for Information Rights Management is not working correctly. To fix this problem, repair your installation of Microsoft ...
  34. The (!idspnSharePoint) list form can't be customized with (!idspnInfoPath) because fields of an unsupported data type are ...
  35. The action for the button has been updated because the data source associated with this button has been removed from the ...
  36. The address is not valid. Enter an address that begins with http://, https://, ftp://, mailto:, or another valid protocol. ...
  37. The amount of data that was returned by a data connection has exceeded the maximum limit that was configured by the server ...
  38. The amount of data that was returned by a data connection has exceeded the maximum limit that was configured by the server ...
  39. The assembly conflicts with a same named assembly in form template: {0}. Assemblies that are identical must be part of form ...
  40. The assembly {0} from form template {1}({2}) conflicts with a same named assembly in an older version of this form. Upgrade ...
  41. The attempted fragment operation cannot be completed because the parent element has text-only content according to the schema. ...
  42. The attempted fragment operation cannot be completed because the schema definition of the parent element requires empty content. ...
  43. The background picture associated with this view no longer exists in the form template. To add a picture, on the Page Design ...
  44. The binding of this section ({0}) can lead to effects that can be evaluated only on the server. Reason: {1}.As a result, ...
  45. The bstrPropertyName parameter must begin with an alphabetic character and can contain only alphanumeric characters and underscores. ...
  46. The buttons parameter is incorrect for the following method: XDocument.UI.Confirm(prompt,buttons). The parameter must be ...
  47. The call to the SetNamedNodeProperty failed. The following node property is used by InfoPath, and cannot be modified: %1!s! ...
  48. The certificate selected to sign this form template is not available or is invalid. Select a valid certificate and save the ...
  49. The class specified as the InfoPathStartupClass for the DescriptionAttribute attribute of the assembly does not match the ...
  50. The class that contains event handlers for this form cannot be identified in the form's code. Confirm that the InfoPathStartupClass ...
  51. The class that contains event handlers for this form cannot be identified. Confirm that the code generated by the Microsoft ...
  52. The connection file specified an unsupported credential type. Supported types are Sql, NTLM, Kerberos, CD, Basic, and Digest. ...
  53. The connection specified a connection in the server store. Only administrator-approved form templates can use this option. ...
  54. The connection {0} specified a connection in the server store. Only administrator-approved form templates can use this option. ...
  55. The current operation requires Business Connectivity Services client components. Install Business Connectivity Services client ...
  56. The current user does not have appropriate permissions for verifying browser compatibility on this site. Contact your server ...
  57. The currently selected form code language and/or object model version is not supported in InfoPath Forms Services.Form code ...
  58. The custom code in the form cannot be run because sandboxed solutions are not enabled on the server farm. For more information, ...
  59. The custom code in the form cannot be run because the sandboxed solutions are not enabled on this site collection. For more ...
  60. The custom code in the form cannot be run because the solution has been deactivated in the Solution Gallery. For more information, ...
  61. The custom code in the form cannot be run. This functionality may be deactivated on the server. For more information, contact ...
  62. The data posted from the browser is invalid. This may arise if a button (with an action other than rules) has been set never ...
  63. The data source file is accessed through a redirection from a different domain, which is not allowed. If you want to use ...
  64. The dataAdapter element in the form definition file (.xsf) is missing the name attribute for the following element: %1!s! ...
  65. The Document Information Panel template attempted to obtain a trust level that cannot be granted. For more information, see ...
  66. The Document Information Panel template cannot be opened because it was published to the local computer or an Internet or ...
  67. The Event Handler ID must begin with an alphabetic character and can contain only alphanumeric characters and underscores. ...
  68. The event handler section (xsf:domEventHandler element) in the form definition (.xsf) file is missing a required attribute. ...
  69. The Export to Excel feature requires Microsoft Office Excel 2003 or 2007. Install Excel, and then try this feature again. ...
  70. The External Item Picker is not supported in user code solutions. To publish this form to SharePoint, use the administrator-approved ...
  71. The fields on the (!idspnSharePoint) server need to be updated. Publish this form to the (!idspnSharePoint) server then try ...
  72. The file could not be saved to the specified location. Choose another location or contact the administrator of your SharePoint ...
  73. The file name is either missing or contains only white space. If you know the value in the form that specifies the file name, ...
  74. The file name is invalid or the file is empty. A file name cannot contain any of the following characters: \ / : ? " < > ...
  75. The file or folder name '{0}' contains invalid characters. Please use a different name. Common invalid characters include ...