SharePoint 2016 configuration to the leader error-the ' listinternal ' attribute is not allowed

Objective

Configure SharePoint 2016 Configuration Wizard, the third step to create a configuration database error, and then Baidu, Google a bit, did not solve, their own look at the log, perhaps some people encounter similar problems, share a bit.

1. Configuration wizard errors, such as:

2, according to find the error log, the detailed information in the log, as follows:

Failed to create the configuration database.  An exception of type System.Xml.Schema.XmlSchemaException was thrown. Additional exception information:feature definition with Id ca7bd552-10b1-4563-85b9-5ed1d39c962a failed validation, File ' Fieldswss4.xml ', line character, 9:the ' listinternal ' attribute are not allowed. System.Xml.Schema.XmlSchemaException:Feature definition with Id ca7bd552-10b1-4563-85b9-5ed1d39c962a failed Validation, file ' Fieldswss4.xml ', line, character 9:the ' listinternal ' attribute are not allowed.   ---> System.Xml.Schema.XmlSchemaValidationException:The ' listinternal ' attribute are not allowed. ---End of inner exception stack trace---at Microsoft.SharePoint.Administration.SPElementManifest.ElementXmlValidatio Ncallback (Object sender, ValidationEventArgs Evtargs) at System.Xml.Schema.XmlSchemaValidator.SendValidationEvent ( String code, string arg) at System.Xml.Schema.XmlSchemaValidator.ValidateAttribute (string lName, string ns, Xmlvalueget ter AttriButevaluegetter, String Attributestringvalue, XmlSchemaInfo schemainfo) at System.Xml.Schema.XmlSchemaValidator.ValidateAttribute (String localname, String NamespaceURI, XmlValueGetter AttributeValue, XmlSchemaInfo SchemaInfo) at System.Xml.XsdValidatingReader.ValidateAttributes () at System.Xml.XsdValidatingReader.ProcessElementEvent () at System.Xml.XsdValidatingReader.Read () at System.Xml.XmlReader.MoveToContent () at System.Xml.XmlReader.IsStartElement () at MICROSOFT.SHAREPOINT.UTILITIES.SPUTILITY.XSDVALIDATEXML (XmlTextReader xmlstreamreader, string FriendlyName, String Pathxsdfile, String Tagexpectedrootnode, Int32 desiredpathversion, ValidationEventHandler Xsdvaleventhandler) at Microsoft.SharePoint.Administration.SPElementManifest.ValidateDefinition (String Pathtofeatureandelementmanifestxsdfile) at MICROSOFT.SHAREPOINT.ADMINISTRATION.SPFEATUREDEFINITION.VALIDATEELEMENTMANIFESTXML (String Pathtofeatureandelementmanifestxsdfile) at Microsoft.SharePoint.AdministratioN.spfeaturedefinition.validatedefinition (String pathtofeatureandelementmanifestxsdfile) at Microsoft.SharePoint.Administration.SPFeatureDefinitionCollection.AddCore (spfeaturedefinition featdef, SPSite Site, String Solutionhash, Boolean Fforce, Boolean fdovalidation, String pathtofeatureandelementmanifestxsdfile) at MICR Osoft. SharePoint.Administration.SPFarmFactory.EnsureOutOfBoxFeaturesInstalled (SPFarm Farm, string[] Rgsoutofboxfeatures , Int32 CompatibilityLevel) at Microsoft.SharePoint.Administration.SPFarmFactory.CreateBasicServices (SPFarm Farm) at Microsoft.SharePoint.Administration.SPFarmFactory.Create () at Microsoft.SharePoint.Administration.SPFarm.Create ( SqlConnectionStringBuilder configurationdatabase, SqlConnectionStringBuilder administrationcontentdatabase, SqlConnectionStringBuilder SiteMapDatabase, Identitytype identitytype, String farmuser, SecureString Farmpassword, SecureString masterpassphrase) at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabAsetask.createorconnectconfigdb () at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run () At Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask ()

3, find fieldswss4 This file, such as:

4, with vs open fieldswss4 This file, found that there is indeed this attribute, and there are error alerts, such as:

5. Locate the following location in the SharePoint 2013 environment and find similar files such as:

6. Compare this error file for SharePoint 2013 and SharePoint 2016, and find that SharePoint 2016 has the following field:

• • Smtotalsize
  • Smlastmodifieddate
  • Smtotalfilestreamsize
  • Smtotalfilecount

7. Delete the listinternal attribute of the four field and then run the Configuration Wizard to find the successful operation, such as:

Summarize

In fact, I do not know the role of this document, check out the detailed description is not found; but delete the Listinternal property can run the Configuration Wizard successfully, I think if there is a problem, it will be possible to restore it back if it is successful (the changes have been backed up before), Does not affect the running of SharePoint.

Of course, have to know the role of this file, welcome message to inform, thank you!

Related errors

Also see have encountered the same error situation, but because of insufficient memory, with their own situation, attached to the reference bar.

Http://fangdahai.blogspot.hk/2016/05/invalid-feature-definition-error-during.html

SharePoint 2016 configuration to the leader error-the ' listinternal ' attribute is not allowed