SQL Server Errors or Failures from Error: 6981 to Error: 7000

SQLServerF1

 

Error: 6981, Severity: 16, Invalid restriction for type ‘%s’. The element in the restricted type may not be nillable if the corresponding element in the base type is not.
Error: 6982, Severity: 16, Invalid restriction for type ‘%s’. The element in the restricted type must be fixed to the same value as the corresponding element in the derived type.
Error: 6983, Severity: 16, Invalid restriction for type ‘%s’. The element in the restricted type may not have a ‘block’ value more permissive than the corresponding element in the base type.
Error: 6984, Severity: 16, Invalid restriction for type ‘%s’. The element in the restricted type must be in one of the namespaces allowed by the base type’s wildcard.

Error: 6985, Severity: 16, Invalid restriction for type ‘%s’. The Wildcard in the restricted type must be a valid subset of the corresponding wildcard in the base type, and the processContents may not be more permissive.
Error: 6986, Severity: 16, Invalid restriction for type ‘%s’. The effective total range of the model group in the restricted type must be a valid restriction of the occurrence range of the wildcard in the base type.
Error: 6987, Severity: 16, Invalid restriction for type ‘%s’. An ‘all’ particle may be restricted only by ‘all’, ‘element’, or ‘sequence’.
Error: 6988, Severity: 16, Invalid restriction for type ‘%s’. A ‘choice’ particle may be restricted only by ‘element’, ‘choice’, or ‘sequence’.
Error: 6989, Severity: 16, Invalid restriction for type ‘%s’. A ‘sequence’ particle may be restricted only by ‘element’ or ‘sequence’.
Error: 6990, Severity: 16, Invalid restriction for type ‘%s’. Invalid model group restriction.

Error: 6991, Severity: 16, Invalid restriction for type ‘%s’. If the base type has empty content, then the derived type must as well, and if the derived type has empty content, then the base type must be emptiable.
Error: 6992, Severity: 16, The content model of type ‘%s’ contains two elements with the same name ‘%s’ and different types, nullability, or value constraints.
Error: 6993, Severity: 16, Value constraint on use of attribute ‘%s’ must be consistent with value constraint on its declaration.
Error: 6994, Severity: 16, Invalid restriction for type ‘%s’. The attribute wildcard in the restricted type must be a valid subset of the corresponding attribute wildcard in the base type, and the processContents may not be more permissive.
Error: 6995, Severity: 16, Invalid definition for type ‘%s’. SQL Server does not permit the built-in XML Schema types ‘ID’ and ‘IDREF’ or types derived from them to be used as the type of an element or as the basis for derivation by extension.
Error: 6996, Severity: 16, Invalid type definition for type ‘%s’. A type may not have both ‘minInclusive’ and ‘minExclusive’ or ‘maxInclusive’ and ‘maxExclusive’ facets.
Error: 6997, Severity: 16, Invalid definition for element ‘%s’. An element which has a fixed value may not also be nillable.
Error: 6998, Severity: 16, Invalid type definition: Type or content model ‘%s’ is too complicated. It may be necessary to reduce the number of enumerations or the size of the content model.
Error: 6999, Severity: 16, Invalid definition for element or attribute ‘%s’. Value constraints on components of type QName are not supported in this release.
Error: 7000, Severity: 16, OPENXML document handle parameter must be of data type int.

This is applicable on below versions of SQL Server

SQL Server 2005
SQL Server 2008 R2
SQL Server 2012
SQL Server 2014

Hope this was helpful.

Thanks,
SQLServerF1 Team
In-Depth Blogs on SQL Server, Information about SQL Server Conferences and Events, SQL Server Frequently asked questions, SQL Server Trainings.

 

Leave a Reply

Your email address will not be published. Required fields are marked *