Export (0) Print
Expand All

7.1.1 Message Elements of Type "Error"

SharePoint

ID

Category

Feature

Message

Description

1

BrowserCompatibility

Controls

The form template is not browser-compatible. It might be possible to correct the problem by opening the form template in Microsoft InfoPath, and then republishing it.

The protocol server returns this error message when the form template file cannot be opened. This error will occur when the file is invalid or corrupt.

5

BrowserCompatibility

Controls

Error loading form code assembly: [name of the user code module].

As specified in [MS-IPFF] section 2.2.147.50

6

BrowserCompatibility

Controls

A rule references a button that is missing from the view.

The protocol server returns this error message when a rule is associated with a button control that is not part of the form view.

12

BrowserCompatibility

Controls

Button [button name] has a value of the xd:action attribute that is not supported in browser-enabled form templates.

As specified in [MS-IPFF] section 2.4.2.1.

13

BrowserCompatibility

Controls

Expected anchor tag is missing.

As specified in [MS-IPFF] section 2.4.1.12.

14

BrowserCompatibility

Controls

List Box control is not supported.

As specified in [MS-IPFF] section 2.4.1.13.

15

BrowserCompatibility

Controls

Choice Section control is not supported.

As specified in [MS-IPFF] section 2.4.1.21.

16

BrowserCompatibility

Controls

Combo Box control is not supported.

As specified in [MS-IPFF] section 2.4.1.21.

18

BrowserCompatibility

Controls

[Control Name] control is not supported.

As specified in [MS-IPFF] section 2.2.108.

21

BrowserCompatibility

Controls

Picture control is not supported.

As specified in [MS-IPFF] section 2.4.1.22.

22

BrowserCompatibility

Controls

Ink Picture control is not supported.

As specified in [MS-IPFF] section 2.4.1.21.

23

BrowserCompatibility

Controls

Horizontal Region control is not supported.

As specified in [MS-IPFF] section 2.4.1.21.

24

BrowserCompatibility

Controls

Master/detail control is not supported.

As specified in [MS-IPFF] section 2.4.2

25

BrowserCompatibility

Controls

Multiple-Selection List Box control is not supported.

As specified in [MS-IPFF] section 2.4.1.21.

26

BrowserCompatibility

Controls

Recursive control not supported.

As specified in [MS-IPFF] section 2.4.1.22.

27

BrowserCompatibility

Controls

Choice Section control is not supported.

As specified in [MS-IPFF] section 2.4.1.22.

28

BrowserCompatibility

Controls

Scrolling Region control is not supported.

As specified in [MS-IPFF] section 2.4.1.21.

30

BrowserCompatibility

Controls

Vertical text is not supported.

As specified in [MS-IPFF] section 2.4.1.21.

31

BrowserCompatibility

Controls

Controls that repeat horizontally are not supported.

As specified in [MS-IPFF] section 2.4.1.21.

40

BrowserCompatibility

Controls

Encountered an encoded identifier [Identifier name]. Encoded identifiers are not supported.

The protocol server returns this error message when parsing the cascading style sheet (CSS) associated with a form view and the CSS contains an encoded identifier.

45

BrowserCompatibility

Controls

The form locale [locale identifier] is not a valid language identifier. Assign a valid locale and try again.

As specified in [MS-IPFF] section 2.2.147.9.

46

BrowserCompatibility

Controls

An XSL file is missing from the form template.

As specified in [MS-IPFF] section 2.2.129.

57

BrowserCompatibility

Controls

Linked images are not supported by InfoPath Forms Services. To fix this problem, make the image a part of the form template. The following image was found in view [view name]: [image name].

The protocol server returns this error message when a form view contains an img element with a href attribute with a value of an absolute URL.

58

BrowserCompatibility

Controls

Unexpected image tag encountered. It is missing a required href attribute.

The protocol server returns this error message when detecting an img element without a href attribute in a form view.

59

BrowserCompatibility

Controls

Only the .png, .gif, and .jpg graphics file formats are supported.

The protocol server returns this error message when the href attribute of an img element in a form view refers a file with an unsupported extension. The Microsoft Office InfoPath 2007 supports the file extensions.png, .gif, and .jpg.

60

BrowserCompatibility

Controls

The data source [data source name] referenced in the form template is not valid or cannot be found.

As specified in [MS-IPFF] section 2.4.3.9.2.

61

BrowserCompatibility

Controls

Invalid format for location attribute [attribute value].

As specified in [MS-IPFF] section 2.2.61.

62

BrowserCompatibility

Controls

An eval expression used in the form has invalid arguments.

As specified in [MS-IPFF] section 2.4.3.6.2.

63

BrowserCompatibility

Controls

The XPath [xpath expression] is invalid. [error details]

As specified in [XPATH].

64

BrowserCompatibility

Controls

The following file is not a valid Xml Schema: [name of the schema file]

As specified in [XMLSCHEMA1].

67

BrowserCompatibility

Controls

The following file is either missing or is not part of included in the form template: [filename]. To add a file to the form template in design mode, use the Resource Files dialog box on the Tools menu, and then add the file.

As specified in [MS-IPFF] section 2.2.98.

68

BrowserCompatibility

Controls

Multiple xsl:templates found with name corresponding to this xsl:call-template. Using the first xsl:template found.

The protocol server returns this error message when a form view file contains more than one XSL template element with the same value for the name attribute.

69

BrowserCompatibility

Controls

Did not find an xsl:template with the same name as this xsl:call-template. Ignoring the xsl:call-template.

As specified in [W3C-XSLT].

71

BrowserCompatibility

Controls

Multiple xsl:templates found with mode corresponding to this xsl:apply-templates. Using the first xsl:template found.

The protocol server returns this error message when a form view file contains an apply-templates element that can find one or more xsl:template element to apply with the same mode attribute.

72

BrowserCompatibility

Controls

The xsl:stylesheet element had multiple xsl:template elements with no mode attribute. This is not supported. Using only the first of these xsl:templates.

As specified in [MS-IPFF] section 2.4.1.2.

73

BrowserCompatibility

Controls

The mode of this xsl:apply-templates element does not match the mode attribute of any xsl:template element.

As specified in [MS-IPFF] sections 2.4.1.15 and 2.4.1.18.

74

BrowserCompatibility

Controls

Could not find an xsl:template without a mode inside xsl:stylesheet.

As specified in [MS-IPFF] section 2.4.1.2 or in [MS-IPFF2] section 2.4.1.2.

75

BrowserCompatibility

Controls

The following construct is not supported: 'xsl:apply-imports'.

As specified in [MS-IPFF] section 2.4.1 or in [MS-IPFF2] section 2.4.1.

76

BrowserCompatibility

Controls

The following construct is not supported: 'xsl:import'.

As specified in [MS-IPFF] section 2.4.1.

77

BrowserCompatibility

Controls

The following construct is not supported: 'xsl:include'.

As specified in [MS-IPFF] section 2.4.1.

79

BrowserCompatibility

Controls

An unexpected error has occurred while verifying the form template.

As specified in [MS-IPFF] section 2.1.

87

BrowserCompatibility

Calculations

The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported function: [XPath expression].

As specified in [MS-IPFF] section 2.2.146, target and expression attributes.

88

BrowserCompatibility

ConditionalFormatting

Unsupported expression

As specified in [MS-IPFF] section 2.4.1.1.

89

BrowserCompatibility

Controls

Unsupported expression

As specified in [MS-IPFF] section 2.4.1.1.

90

BrowserCompatibility

DataAdapters

Unsupported expression

As specified in [MS-IPFF] section 2.2.44.

91

BrowserCompatibility

DigitalSignatures

Unsupported expression

As specified in [MS-IPFF] section 2.2.126, data and signatureLocation attributes.

92

BrowserCompatibility

GenericXsl

Unsupported expression

As specified in [MS-IPFF] section 2.4.1.

93

BrowserCompatibility

Rules

Unsupported expression

As specified in [MS-IPFF] section 2.2.133.

94

BrowserCompatibility

Controls

Unsupported expression

As specified in [MS-IPFF] section 2.2.63, expression and expressionContext attributes.

95

BrowserCompatibility

Controls

Unsupported expression

As specified in [MS-IPFF] sections 2.2.124 and 2.2.107.

97

BrowserCompatibility

Controls

Browser-enabled form templates must have at least one browser-compatible view.

As specified in [MS-IPFF] section 2.2.122.

98

BrowserCompatibility

Controls

[Detailed error message the XML Processor]

As specified in [MS-IPFF] section 2.2.

99

BrowserCompatibility

Controls

Unexpected schema validation error: [Schema Error]

As specified in [MS-IPFF] section 2.2.60.

100

BrowserCompatibility

Controls

[Detailed error message the XML Processor]

As specified in [MS-IPFF] section 2.2.

102

BrowserCompatibility

Controls

HWS data connections are not supported.

As specified in [MS-IPFF] section 2.2.40.

103

BrowserCompatibility

Controls

HWS task pane is not supported.

As specified in [MS-IPFF] section 2.2.87.

111

BrowserCompatibility

Controls

The form template is not browser-compatible, perhaps as a result of modifications made outside of Microsoft InfoPath. It might be possible to correct the problem by republishing the form template from within Microsoft InfoPath.

As specified in [MS-IPFF] section 2.2.147.8, runtimeCompatibility attribute.

112

BrowserCompatibility

Controls

Character expected. Found an empty value.

As specified in [MS-IPFF] section 2.4.1.

113

BrowserCompatibility

Controls

Character expected. Found a string value.

As specified in [MS-IPFF] section 2.4.1.1.

114

BrowserCompatibility

Controls

Double value expected. [value] is not a valid double.

As specified in [MS-IPFF] section 2.4.1.

115

BrowserCompatibility

Controls

Invalid Uri found as value of href attribute of xsl:import.

The protocol server returns this error message when parsing the XSL of a form view file. The href attribute of an xsl:import element uses an invalid URI value.

116

BrowserCompatibility

Controls

Invalid Uri found as value of href attribute of xsl:include.

The protocol server returns this error message when parsing the XSL of a form view file. The href attribute of an xsl:include element uses an invalid URI value.

117

BrowserCompatibility

Controls

Invalid value: [value] for grouping-size attribute of xsl:number. The value must be a positive integer value.

The protocol server returns this error message when parsing the XSL of a form view file. The grouping-size attribute xsl:number element has an invalid value.

118

BrowserCompatibility

Controls

Invalid value: [value] for letter-value attribute of xsl:number. Valid values are: 'alphabetic' and 'traditional'.

The protocol server returns this error message when parsing the XSL of a form view file. The letter-value attribute of an xsl:number element has a value different from "alphabetic" or "traditional".

119

BrowserCompatibility

Controls

Invalid value: [value] for level attribute of xsl:number. Valid values are: 'single', 'multiple' and 'any'.

The protocol server returns this error message when parsing the XSL of a form view file. The level attribute of an xsl:number element has a value different from "single", "multiple" or "any".

120

BrowserCompatibility

Controls

Invalid value: [value] for case-order attribute of xsl:sort. Valid values are: 'upper-first' and 'lower-first'.

The protocol server returns this error message when parsing the XSL of a form view file. The case-order attribute of an xsl:sort element has a value different from "upper-first" or "lower-first".

121

BrowserCompatibility

Controls

Invalid value: [value] for order attribute of xsl:sort. Valid values are: 'ascending' and 'descending'.

The protocol server returns this error message when parsing the XSL of a form view file. The order attribute of an xsl:sort element has a value different from "ascending" or "descending".

122

BrowserCompatibility

Controls

xsl:import encountered after other xsl constructs.

The protocol server returns this error message when parsing the XSL of a form view file. The parser found an xsl:import element that is not at the top level of the XSL document.

123

BrowserCompatibility

Controls

Integer value expected. [value] is not a valid integer.

The protocol server returns this error message when parsing the XSL of a form view file. The parser found an invalid value where an integer value was expected.

124

BrowserCompatibility

Controls

The qualified name [name] is not valid.

As specified in [MS-IPFF] section 2.4.1.

125

BrowserCompatibility

Controls

The qualified name [original value] is not a valid. Using qualified name [replace value].

As specified in [MS-IPFF] section 2.4.1.

126

BrowserCompatibility

Controls

Xsl for view [view name] is not a valid xml file. [Detailed error message the XML Processor]

As specified in [MS-IPFF] section 2.4.

127

BrowserCompatibility

Controls

Multiple xsl:otherwise elements in an xsl:when are not supported.

As specified in [W3C-XSLT] section 9.2.

128

BrowserCompatibility

Controls

xsl:template found with no match attribute and no name attribute. At least one must be specified.

As specified in [W3C-XSLT] section 5.3, 6

129

BrowserCompatibility

Controls

If a xsl:template element does not have a match attribute, it must not have a mode attribute.

As specified in [W3C-XSLT] section 5.7

130

BrowserCompatibility

Controls

xsl:otherwise element found without a corresponding xsl:when element.

As specified in [W3C-XSLT] section 9.2

131

BrowserCompatibility

Controls

xsl:param encountered after other xsl constructs.

As specified in [W3C-XSLT] section 15

132

BrowserCompatibility

Controls

The prefix [namespace prefix] is not declared in the current scope.

As specified in [W3C-XSLT] section 2.1

133

BrowserCompatibility

Controls

Unexpected attribute {[namespace]}[attribute local-name] encountered.

As specified in [W3C-XSLT] section 2.1

134

BrowserCompatibility

Controls

Unexpected element {[namespace]}[element local-name] encountered.

As specified in [W3C-XSLT] section 2.1

135

BrowserCompatibility

Controls

Unexpected node encountered.

As specified in [W3C-XSLT] section 2.1

136

BrowserCompatibility

Controls

Unexpected type of node [node type] encountered.

As specified in [W3C-XSLT] section 2.1

137

BrowserCompatibility

Controls

Unexpected child element for xsl:for-each. Only xsl:sort elements are allowed.

As specified in [W3C-XSLT] section 8

138

BrowserCompatibility

Controls

Unsupported value: [value] found for version attribute of xsl:stylesheet.

As specified in [MS-IPFF] section 2.4.1.2.

139

BrowserCompatibility

Controls

Unexpected text encountered.

As specified in [MS-IPFF] section 2.4.1.22.

140

BrowserCompatibility

Controls

Unexpected value: [value]. Expected 'yes' or 'no'.

As specified in [W3C-XSLT] section B

141

BrowserCompatibility

Controls

Entity References are not supported.

As specified in [W3C-XSLT] section 2.4.

142

BrowserCompatibility

Controls

This element does not permit content if the select attribute is specified.

As specified in [W3C-XSLT] section 2.4.

143

BrowserCompatibility

Controls

Unexpected xsl:when element found after an xsl:otherwise.

As specified in [W3C-XSLT] section 9.2.

144

BrowserCompatibility

Controls

The form definition (.xsf) file has an invalid errorCondition -- errorMessage tag is missing.

As specified in [MS-IPFF] section 2.2.63, errorCondition element.

145

BrowserCompatibility

Controls

The form definition (.xsf) file has an invalid errorCondition -- errorMessage tag is missing.

As specified in [MS-IPFF] section 2.2.63, errorCondition element.

147

BrowserCompatibility

Controls

Duplicate data adapter name encountered.

As specified in [MS-IPFF] section 2.2.36, name attribute.

148

BrowserCompatibility

Controls

The specified onAfterSubmit action is not supported.

As specified in [MS-IPFF] section 2.2.72, onAfterSubmit attribute.

149

BrowserCompatibility

Controls

Invalid query or submit specification for data adapter.

As specified in [MS-IPFF] section 2.2.37.

150

BrowserCompatibility

Controls

Unsupported Data Adapter.

As specified in [MS-IPFF] section 2.2.59.

151

BrowserCompatibility

Controls

A partFragment tag is missing a match attribute.

As specified in [MS-IPFF] section 2.2.44, match attribute.

152

BrowserCompatibility

Controls

A partFragment tag is missing a replaceWith attribute.

As specified in [MS-IPFF] section 2.2.44, replaceWith attribute

155

BrowserCompatibility

Controls

The operation failed. The data contained multiple DataSets.

The protocol server returns this message when the data source returns more than one dataset. This could happen when querying data from a [Iseminger] database that supports multiple datasets.

158

BrowserCompatibility

Controls

One or more data connection library attributes is empty.

As specified in [MS-IPFF] section 2.2.147.30, connectionLinkType attribute.

160

BrowserCompatibility

Controls

Filters on Repeating Sections are not supported.

As specified in [MS-IPFF] section 2.4.1.15.

161

BrowserCompatibility

Controls

Filters on Repeating Tables are not supported.

As specified in [MS-IPFF] section 2.4.1.16.

162

BrowserCompatibility

Controls

The following HTML tag is not supported: 'Text Box'.

As specified in [MS-IPFF] section 2.4.2.11.

171

BrowserCompatibility

Controls

The XSL for the Date Picker is not in the expected form.

As specified in [MS-IPFF] section 2.4.1.8.

172

BrowserCompatibility

Controls

Invalid or malicious HTML was found in view [view name].

The server returns this message when the body element in a form view is not valid HTML or if an attribute on that element contains a quote (") character.

173

BrowserCompatibility

Controls

Invalid or malicious HTML was found in view [view name].

The protocol server returns this error message when a form view contains invalid or unsafe HTML elements or attributes, and the only SourceLocation information the protocol server is returning is the source file in which the issue occurs. Determining what HTML to consider unsafe is implementation-specific.

174

BrowserCompatibility

Controls

Invalid or malicious HTML was found in view [view Name].

The protocol server returns this error message when the server cannot determine whether or not a form view contains invalid or unsafe HTML elements or attributes. Determining what HTML to consider unsafe is implementation-specific.

175

BrowserCompatibility

Controls

Invalid or malicious HTML was found in view [view Name].

The protocol server returns this error message when a form view contains invalid or unsafe HTML elements or attributes, the SourceLocation information the protocol server is returning contains both the source file and line number in which the issue occurs, and the MessageType value for the corresponding Message is "Error". Determining what HTML to consider unsafe is implementation-specific.

176

BrowserCompatibility

Controls

Invalid or malicious HTML was found in view [view Name].

The protocol server returns this error message when the server cannot determine whether or not a form view contains invalid or unsafe HTML elements or attributes. Determining what HTML to consider unsafe is implementation-specific.

177

BrowserCompatibility

TemplateXml

The form template cannot be browser-enabled because the template data is not valid according to its schema. [Error details]

As specified in [MS-IPFF] section 2.7.

178

BrowserCompatibility

Controls

A required parameter is missing for the data adapter [adapter name]: [XPath expression for the missing parameter]

As specified in [MS-IPFF] sections 2.2.39 and 2.2.41.

179

BrowserCompatibility

Controls

A required parameter is missing for the data adapter [adapter name]: [XPath expression for the missing parameter]

As specified in [MS-IPFF] sections 2.2.39 and 2.2.41.

180

BrowserCompatibility

Controls

Relative links to Data Connection Libraries located on different SharePoint site collection are not supported.

As specified in [MS-IPFF] section 2.2.147.30, siteCollection attribute.

183

BrowserCompatibility

Controls

Could not execute the following relative query [data adapter name]. Relative queries are not allowed for connections linked to the Data Connection Library.

As specified in [MS-IPFF] section 2.2.147.33.

184

BrowserCompatibility

Controls

Cannot run the relative query [query]. Relative queries are not allowed for connections linked to the Data Connection Library.

As specified in [MS-IPFF] section 2.2.147.34.

185

BrowserCompatibility

Controls

relativeQuery/@replace cannot be a relative, local, or UNC path.

As specified in [MS-IPFF] section 2.2.147.34.

186

BrowserCompatibility

Controls

Unsupported HTML constructs were found associated with this Repeating Table.

As specified in [MS-IPFF] section 2.4.1.16.

191

BrowserCompatibility

Controls

A text box is bound to an inappropriate datatype.

As specified in [MS-IPFF] section 2.4.1.20.

192

BrowserCompatibility

Controls

Rule was referenced but not defined: [rulenName].

As specified in [MS-IPFF] section 2.2.132, ruleSet attribute.

193

BrowserCompatibility

Controls

There has been a critical error while processing the form.

The protocol server returns this error message protocol server when an unknown error was encountered and the protocol server does not have a default method for handling this unknown error.

196

BrowserCompatibility

DataAdapters

This database is not supported. The database must be a Microsoft SQL Server.

The protocol server returns this error message when there is a data adapter that attempts to connection to a database that is not supported by the protocol server .

197

BrowserCompatibility

BusinessLogic

Unsupported object model version.

As specified in [MS-IPFF] section 2.2.147.50, version attribute.

200

BrowserCompatibility

GenericXsf

The definition of view [view name] does not exist.

As specified in [MS-IPFF] sections 2.2.68, 2.2.114, and 2.2.129, transform attribute.

203

BrowserCompatibility

GenericXPath

A call to GetDOM failed. The DataObject does not exist.

As specified in [MS-IPFF] section 2.4.3.9.2.

204

BrowserCompatibility

ExpressionXPathAnalysis

Invalid expression encountered: [XPath expression].

As specified in [XPATH].

205

BrowserCompatibility

ExpressionXPathAnalysis

Invalid binding XPath [XPath expression].

As specified in [MS-IPFF] section 2.4.1.1, productions LEAF_XPATH, GROUP_XPATH, RELATIVE_REPEATING_GROUP_XPATH and RELATIVE_LEAF_XPATH.

206

BrowserCompatibility

ExpressionXPathAnalysis

Invalid binding XPath [XPath expression.

As specified in [MS-IPFF] section 2.4.1.1, productions LEAF_XPATH, GROUP_XPATH, RELATIVE_REPEATING_GROUP_XPATH and RELATIVE_LEAF_XPATH.

207

BrowserCompatibility

ExpressionXPathAnalysis

Invalid binding XPath [XPath expression.

As specified in [MS-IPFF] section 2.4.1.1 or in [MS-IPFF2] section 2.4.1.1, productions LEAF_XPATH, GROUP_XPATH, RELATIVE_REPEATING_GROUP_XPATH and RELATIVE_LEAF_XPATH.

208

BrowserCompatibility

ExpressionXPathAnalysis

Invalid binding XPath [XPath expression.

As specified in [MS-IPFF] section 2.4.1.1, productions LEAF_XPATH, GROUP_XPATH, RELATIVE_REPEATING_GROUP_XPATH and RELATIVE_LEAF_XPATH.

209

BrowserCompatibility

ExpressionXPathAnalysis

Invalid binding XPath [Xpath expression].

As specified in [MS-IPFF] section 2.4.1.1, production LEAF_XPATH.

210

BrowserCompatibility

GenericXsf

The form template defines multiple schemas for the same namespace: [namespace]

As specified in [MS-IPFF] section 2.2.61, location attribute.

211

BrowserCompatibility

GenericXsf

Form template is not valid. The following schema file: [filename] was not found in the Form Template.

As specified in [MS-IPFF] section 2.2.98.

212

BrowserCompatibility

GenericXsf

The following DataObject either cannot be created or cannot be initialized: [data objectnName]. The data adapter cannot be initialized. The form contains XML that cannot be parsed: [Detailed error message the XML Processor].

As specified in [MS-IPFF] section 2.2.36, schema attribute.

213

BrowserCompatibility

GenericXsf

The specified XML template file (xsf:initialXmlDocument element) is not a valid XML document. [Detailed error message the XML Processor].

As specified in [MS-IPFF] section 2.2.92.

214

BrowserCompatibility

GenericXsf

The specified XML template file (xsf:initialXmlDocument element) does not contain required processing instructions.

As specified in [MS-IPFF] section 2.2.94.

215

BrowserCompatibility

GenericXsf

The specified XML template file (xsf:initialXmlDocument element) is not a valid XML document. [Detailed error message the XML Processor]

As specified in [MS-IPFF] section 2.2.94.

216

BrowserCompatibility

GenericXsf

The XML template file (specified in the xsf:initialXmlDocument element of the form template definition file) has a processing instruction with a form template version that does not match the version of the form template.

As specified in [MS-IPFF] section 2.2.20, solutionVersion attribute and [MS-IPFF] section 2.7.

217

BrowserCompatibility

GenericXsf

The specified XML template file (xsf:initialXmlDocument element) contains a urn reference that does not match the solutions name.

As specified in [MS-IPFF] section 2.2.20, name attribute and [MS-IPFF] section 2.7.

218

BrowserCompatibility

GenericXsf

No XML template file is present in the form template.

As specified in [MS-IPFF] section 2.2.94, href attribute.

219

BrowserCompatibility

GenericXsf

The following XML template file is missing or is not part of the form template: [file name]

As specified in [MS-IPFF] section 2.2.94, href attribute.

220

BrowserCompatibility

GenericXsf

Duplicate property name '[property name]' in file '[file name]'.

As specified in [MS-IPFF] section 2.2.100, name attribute.

221

BrowserCompatibility

GenericXsf

A button element in the form definition file (manifest.xsf) has invalid attributes.

As specified in [MS-IPFF] section 2.2.106 and 2.2.110.

223

BrowserCompatibility

DigitalSignatures

An error occurred when initializing a set of signable data. A name has not been specified for the set of data.

As specified in [MS-IPFF] section 2.2.126, name attribute.

234

BrowserCompatibility

DigitalSignatures

No group was found at the location specified for storing signatures for the set of signable data: [XPath expression] . Use the Digital Signatures category of the Form Options dialog box to edit the expression specifying the storage location for signatures.

As specified in [MS-IPFF] section 2.2.126, signatureLocation attribute.

235

BrowserCompatibility

DigitalSignatures

An error occurred when initializing the set of signable data: [XPath expression]. No group was found at the specified location.

As specified in [MS-IPFF] section 2.2.126, mode attribute.

236

BrowserCompatibility

DigitalSignatures

An error occurred when initializing the set of signable data: "[XPath expression ". No group was found at the specified location.

As specified in [MS-IPFF] section 2.2.126, mode attribute.

237

BrowserCompatibility

DigitalSignatures

No fields or groups were found corresponding to the set of signable data: [XPath expression]. Use the Digital Signatures category of the Form Options dialog box to edit the expression specifying the data to be signed.

As specified in [MS-IPFF] section 2.2.126, data attribute.

238

BrowserCompatibility

GenericXsl

No group was found at the location specified for storing signatures for the set of signable data: "[signed data block name]". Use the Digital Signatures category of the Form Options dialog box to edit the expression specifying the storage location for signatures.

As specified in [MS-IPFF] section 2.2.126, signatureLocation attribute.

239

BrowserCompatibility

GenericXsf

The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported function: [XPath expression].

As specified in [MS-IPFF] section 2.4.1.

240

BrowserCompatibility

Controls

Numbered List control is not supported

As specified in [MS-IPFF] section 2.4.1.21, xctName attribute.

241

BrowserCompatibility

Controls

Bulleted List control is not supported

As specified in [MS-IPFF] section 2.4.1.21, xctName attribute.

242

BrowserCompatibility

Controls

Plain List control is not supported

As specified in [MS-IPFF] section 2.4.1.21, xctName attribute.

247

BrowserCompatibility

Controls

This control formats the data to show both date and time. Date and time cannot be displayed together in the same control in server forms. Use two controls to display date and time separately and bind them to the same field.

As specified in [MS-IPFF] section 2.4.2.11.

248

BrowserCompatibility

Controls

This control formats the data using an invalid or unsupported time format [user format string]. Pick a different format.

As specified in [MS-IPFF] section 2.4.2.11.

249

BrowserCompatibility

Controls

This control formats the data using an invalid or unsupported date format [user format string]. Pick a different format.

As specified in [MS-IPFF] section 2.4.2.11.

250

BrowserCompatibility

GenericXsf

The restricted trust level is not supported.

As specified in [MS-IPFF] section 2.2.20, trustLevel attribute.

252

BrowserCompatibility

GenericXsf

This form template has not been correctly published to be browser-enabled. Open the form template in InfoPath Design mode, and click Publish Form Template in the Design Tasks task pane. Follow the steps in the Publishing Wizard to republish the form template, and then try again.

The protocol server returns this message when it encounters errors while trying to browser-enable a form template.

256

BrowserCompatibility

Controls

Selected rich text formatting options are not supported Selected rich text formatting options are not supported.

As specified in [MS-IPFF] section 2.2.147.43.

260

BrowserCompatibility

Controls

The following expression could not be parsed because of a syntax error or because it uses an undefined namespace prefix or unsupported function: [XPath expression].

As specified in [MS-IPFF] section 2.4.1.

261

BrowserCompatibility

Controls

Specifying a restricted set of allowable file types for a File Attachment control is not supported in server forms.

As specified in [MS-IPFF] section 2.2.108, allowedFileTypes attribute.

262

BrowserCompatibility

Controls

Conditionally formatting a File Attachment control is not supported in server forms

As specified in [MS-IPFF] section 2.4.1.11.

267

BrowserCompatibility

GenericXsf

The form template is not browser-compatible, perhaps as a result of modifications made outside of Microsoft InfoPath. It might be possible to correct the problem by republishing the form template from within Microsoft InfoPath.

The protocol server returns this error message when the form template is not a browser-compatible form template and no more specific error message is applicable.

268

BrowserCompatibility

GenericXsf

Forms enabled for use on a mobile device are supported only for administrator-approved form templates.

As specified in [MS-IPFF] section 2.2.147.9, isMobileEnabled attribute

269

BrowserCompatibility

GenericXsf

Unbound Rich Text Box controls are not supported by InfoPath Forms Services.

As specified in [MS-IPFF] section 2.4.1.17.

270

BrowserCompatibility

GenericXsf

Unbound File Attachment controls are not supported by InfoPath Forms Services.

As specified in [MS-IPFF] section 2.4.1.11.

271

BrowserCompatibility

GenericXsf

Invalid or unsupported locale (LCID [LCID]) used in view [view name]. Try using different locale.

As specified in [MS-IPFF] section 2.4.1.4.

272

BrowserCompatibility

GenericXsf

The form cannot be converted because it was designed for a later version of InfoPath Forms Services.

As specified in [MS-IPFF] section 2.2.20, solutionFormatVersion attribute.

273

BrowserCompatibility

GenericXsl

The view contains nested formatting that is not supported on InfoPath Forms Services. Examples of such formatting include heavily nested tables and heavily formatted text.

The protocol server returns this error message when an XSL file is not supported because either the depth at which XML elements are nested in the file or the complexity of processing the file exceeds what the server supports. The depth and complexity at which this message is reported is an implementation choice left to the protocol implementer.

274

BrowserCompatibility

GenericXPath

An XPath requires complicated processing that is not supported on InfoPath Forms Services.

The protocol server returns this error message when an XPath expression contains more steps and axis than the server supports. The complexity at which this message is reported is an implementation choice left to the protocol implementer

Show:
© 2015 Microsoft