%3CLINGO-SUB%20id%3D%22lingo-sub-309056%22%20slang%3D%22en-US%22%3ESharePoint%20fails%20to%20create%20Configuration%20Database%20for%20a%20new%20farm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-309056%22%20slang%3D%22en-US%22%3E%3CH1%20id%3D%22toc-hId-1869992086%22%20id%3D%22toc-hId-1898413593%22%20id%3D%22toc-hId-1898413593%22%20id%3D%22toc-hId-1898413593%22%20id%3D%22toc-hId-1898413593%22%3EProblem%20Description%3C%2FH1%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EA%20new%20installation%20of%20SharePoint%20fails%20to%20provision%20a%20new%20farm%20due%20to%20a%20failure%20while%20creating%20the%20configuration%20database.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExample%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20601px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64684i9678B9868F710E55%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22011118_1934_SharePointf1.png%22%20title%3D%22011118_1934_SharePointf1.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHere%20is%20the%20exception%20stack%20from%20the%20PSCDiagnostics%20log%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3E01%2F11%2F2018%2013%3A37%3A00%2010%20ERR%20Exception%3A%20Microsoft.SharePoint.Upgrade.SPUpgradeException%3A%20One%20or%20more%20types%20failed%20to%20load.%20Please%20refer%20to%20the%20upgrade%20log%20for%20more%20details.%0Aat%20Microsoft.SharePoint.Upgrade.SPActionSequence.LoadUpgradeActions()%0Aat%20Microsoft.SharePoint.Upgrade.SPActionSequence.get_Actions()%0Aat%20Microsoft.SharePoint.Upgrade.SPActionSequence.get_ActionsInternal()%0Aat%20Microsoft.SharePoint.Upgrade.SPUtility.GetLatestTargetSchemaVersionBeforeMajorVersion(Type%20typeActionSequence%2C%20Int32%20majorVer)%0Aat%20Microsoft.SharePoint.Upgrade.SPSiteSequence.get_PreviousTargetSchemaVersion()%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.PopulateSequencesTable(StringBuilder%20sqlstr%2C%20Boolean%20siteSequence)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.ConstructSiteNeedsUpgradeQuery(Guid%20siteId)%0Aat%20Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.GetSiteNeedsUpgrade(SPUpgradeSession%20session%2C%20SPContentDatabase%20database%2C%20Dictionary%602%26amp%3B%20dictSitesNeedUpgrade%2C%20Dictionary%602%26amp%3B%20dictSitesNeedFeatureUpgrade)%0Aat%20Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.AddNextLevelObjects()%0Aat%20Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree%601%20root%2C%20Boolean%20bRecursing%2C%20SPDelegateManager%20delegateManager)%0Aat%20Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree%601%20root%2C%20SPDelegateManager%20delegateManager)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object%20o%2C%20Boolean%20bRecurse)%0Aat%20Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalUpgradeStatus()%0Aat%20Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalProductVersions(SPProductVersions%20prodVer)%0Aat%20Microsoft.SharePoint.Administration.SPServerProductInfo.UpdateProductInfoInDatabase(Guid%20serverGuid)%0Aat%20Microsoft.SharePoint.Administration.SPFarm.Join(Boolean%20skipRegisterAsDistributedCacheHost%2C%20Nullable%601%20serverRole)%0Aat%20Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()%0Aat%20Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()%0Aat%20Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()%3C%2FPRE%3E%0A%3CH1%20id%3D%22toc-hId--682164875%22%20id%3D%22toc-hId--653743368%22%20id%3D%22toc-hId--653743368%22%20id%3D%22toc-hId--653743368%22%20id%3D%22toc-hId--653743368%22%3E%26nbsp%3B%3C%2FH1%3E%0A%3CH1%20id%3D%22toc-hId-1060645460%22%20id%3D%22toc-hId-1089066967%22%20id%3D%22toc-hId-1089066967%22%20id%3D%22toc-hId-1089066967%22%20id%3D%22toc-hId-1089066967%22%3ECause%3C%2FH1%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20issue%20can%20occur%20if%20you%20chose%20to%20download%20and%20install%20all%20the%20prerequisite%20software%20manually%2C%20namely%20in%20this%20case%20the%20%22%3CSTRONG%3EWCF%20Data%20Services%205.6%20Tools%3C%2FSTRONG%3E%22.%20If%20you%20are%20experiencing%20the%20error%2C%20%3CEM%3E%3CSPAN%3E%22One%20or%20more%20types%20failed%20to%20load%22%20%2C%20%3C%2FSPAN%3E%3C%2FEM%3Ewhile%20creating%20a%20new%20SharePoint%20Farm%2C%20it's%20most%20likely%20caused%20by%20the%20installer%20executable%20being%20in%20a%20%22blocked%22%20state%20while%20it%20was%20installed.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExample%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20402px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64685iECC2D4D9753130DA%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22011118_1934_SharePointf2.png%22%20title%3D%22011118_1934_SharePointf2.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWhen%20executables%20are%20downloaded%20from%20the%20internet%2C%20they%20are%20put%20into%20a%20%22blocked%22%20state%20by%20to%20OS%2C%20to%20prevent%20users%20from%20running%20malicious%20code.%20However%2C%20in%20this%20case%2C%20if%20the%20installer%20was%20in%20a%20blocked%20state%20when%20the%20%3CSTRONG%3E%22WCF%20Data%20Services%205.6%20Tools%22%3C%2FSTRONG%3E%20were%20installed%2C%20the%20install%20will%20%22succeed'%20but%20will%20not%20be%20installed%20properly.%3C%2FP%3E%0A%3CH1%20id%3D%22toc-hId--1491511501%22%20id%3D%22toc-hId--1463089994%22%20id%3D%22toc-hId--1463089994%22%20id%3D%22toc-hId--1463089994%22%20id%3D%22toc-hId--1463089994%22%3E%26nbsp%3B%3C%2FH1%3E%0A%3CH1%20id%3D%22toc-hId-251298834%22%20id%3D%22toc-hId-279720341%22%20id%3D%22toc-hId-279720341%22%20id%3D%22toc-hId-279720341%22%20id%3D%22toc-hId-279720341%22%3EResolution%3C%2FH1%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3ETo%20resolve%20this%20issue%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E1.%20Go%20to%20the%20properties%20of%20each%20prerequisite%20installer%20package%20that%20was%20downloaded%20manually%20and%20remove%20the%20block%20flag%20by%20selected%20%22Unblock%22%20and%20applying%20the%20changes.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExample%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20828px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64686i8E1E27AB649E8F04%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22011118_1934_SharePointf3.png%22%20title%3D%22011118_1934_SharePointf3.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2.%20After%20the%20file%20has%20been%20unblocked%2C%20re-run%20the%20installer%20and%20choose%20the%20repair%20option.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20533px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64687i35FA8145B1B2253A%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22011118_1934_SharePointf4.png%22%20title%3D%22011118_1934_SharePointf4.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3.%20Finally%2C%20re-run%20the%20SharePoint%20Configuration%20Wizard%20to%20successfully%20create%20a%20new%20Farm.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20608px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64688i1CE0891442BD160E%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22011118_1934_SharePointf5.png%22%20title%3D%22011118_1934_SharePointf5.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CHR%20%2F%3E%0A%3CH1%20id%3D%22toc-hId-1994109169%22%20id%3D%22toc-hId-2022530676%22%20id%3D%22toc-hId-2022530676%22%20id%3D%22toc-hId-2022530676%22%20id%3D%22toc-hId-2022530676%22%3EUpdate%3C%2FH1%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20wanted%20to%20update%20this%20blog%20with%20a%20recent%20discovery%20that%20will%20cause%20the%20same%20issue%20without%20the%20installer%20appearing%20to%20be%20%22blocked%22.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EFor%20example%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20following%20image%20does%20not%20show%20the%20installer%20package%20being%20in%20a%20%22blocked%22%20state.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64689i1BE826CDA1F1A5C5%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22unblocked_but_blocked.png%22%20title%3D%22unblocked_but_blocked.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--951074802%22%20id%3D%22toc-hId--922653295%22%20id%3D%22toc-hId--922653295%22%20id%3D%22toc-hId--922653295%22%20id%3D%22toc-hId--922653295%22%3E%26nbsp%3B%3C%2FH3%3E%0A%3CH3%20id%3D%22toc-hId-791735533%22%20id%3D%22toc-hId-820157040%22%20id%3D%22toc-hId-820157040%22%20id%3D%22toc-hId-820157040%22%20id%3D%22toc-hId-820157040%22%3EHow%20does%20this%20occur%3F%3C%2FH3%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThis%20condition%20can%20occur%20of%20your%20system%20is%20configured%20with%20the%20%22%3CSTRONG%3EDo%20not%20preserve%20zone%20information%20in%20file%20attachments%3C%2FSTRONG%3E%22%20policy%20enabled.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPolicy%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CPRE%3EUser%20Configuration%20%26gt%3B%20Administrative%20Templates%20%26gt%3B%20Windows%20Components%20%26gt%3B%20Attachment%20Manager%20%26gt%3B%20Do%20not%20preserve%20zone%20information%20in%20file%20attachments%20%3D%20Enabled%3C%2FPRE%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EExample%3A%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20961px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F64690i46D3BB0074DD3094%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20alt%3D%22policy.png%22%20title%3D%22policy.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CH3%20id%3D%22toc-hId--1760421428%22%20id%3D%22toc-hId--1731999921%22%20id%3D%22toc-hId--1731999921%22%20id%3D%22toc-hId--1731999921%22%20id%3D%22toc-hId--1731999921%22%3EWhat%20should%26nbsp%3B%20be%20done%3F%3C%2FH3%3E%0A%3CP%3EIf%20you%20find%20yourself%20in%20this%20situation%2C%20there%20is%20a%20good%20possibility%20that%20additional%20pre-req%20software%20was%20not%20installed%20properly%20and%20will%20cause%20unexpected%20outcomes%20while%20working%20with%20SharePoint.%3C%2FP%3E%0A%3CP%3EWith%20that%20said%2C%20please%20consider%20the%20following%20actions.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3COL%3E%0A%3CLI%3EDisable%20the%20%22%3CSTRONG%3EDo%20not%20preserve%20zone%20information%20in%20file%20attachments%3C%2FSTRONG%3E%22%20policy%20and%20reboot.%3C%2FLI%3E%0A%3CLI%3ERe-run%20each%20pre-req%20package%20manually%20and%20choose%20the%20repair%20option%2C%20if%20applicable.%3C%2FLI%3E%0A%3CLI%3EIf%20the%20repair%20options%20is%20not%20offered%2C%26nbsp%3Buninstall%20and%20re-install%20pre-req%26nbsp%3Binstaller%26nbsp%3Bpackage.%3C%2FLI%3E%0A%3C%2FOL%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-309056%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3ESharePoint%20fails%20to%20create%20Configuration%20Database%20for%20a%20new%20farm%20with%20exception%20%22Microsoft.SharePoint.Upgrade.SPUpgradeException%3A%20One%20or%20more%20types%20failed%20to%20load.%20Please%20refer%20to%20the%20upgrade%20log%20for%20more%20details.%22%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-309056%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20On-Prem%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%20Support%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1522916%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20fails%20to%20create%20Configuration%20Database%20for%20a%20new%20farm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1522916%22%20slang%3D%22en-US%22%3E%3CP%3EThank%20you%20for%20sharing%20this%20post!%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CSPAN%3EI%20also%20experienced%20this%20issue%20in%20March%202018%20and%20wrote%20down%20the%20details%20of%20its%20resolution%20and%20root%20cause%20at%26nbsp%3B%3C%2FSPAN%3E%3CSTRONG%3E%3CA%20title%3D%22SharePoint%202016%3A%20Failed%20to%20create%20the%20configuration%20database.%20Microsoft.SharePoint.Upgrade.SPUpgradeException%20was%20thrown%22%20href%3D%22https%3A%2F%2Fspgeeks.devoworx.com%2Fsharepoint-2016-failed-to-create-the-configuration-database-an-exception-of-type-microsoft-sharepoint-upgrade-spupgradeexception-was-thrown%2F%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noreferrer%22%3ESharePoint%202016%3A%20Failed%20to%20create%20the%20configuration%20database.%20Microsoft.SharePoint.Upgrade.SPUpgradeException%20was%20thrown%3C%2FA%3E%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%3CBR%20%2F%3E%3CSPAN%3EHope%20this%20workaround%20also%20helps%20others!%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1950700%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20fails%20to%20create%20Configuration%20Database%20for%20a%20new%20farm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1950700%22%20slang%3D%22en-US%22%3E%3CP%3EAmazing!%20Truly%20Astounding%20how%20much%20the%20SharePoint%20team%20is%20an%20%3CSTRONG%3Eutter%20failure%3C%2FSTRONG%3E.%20This%20is%20the%20most%20horrific%20installation%20process%20of%20all%20software%20in%20the%202000s.%20I've%20been%20at%20this%20for%2025%20years%20and%20it%20truly%20takes%20effort%20to%20fail%20this%20hard.%20I've%20been%20working%20on%20installing%20this%20software%20for%20many%20hours%20due%20to%20broken%20links%2C%20failed%20prerequisites%2C%20mysterious%20errors%20and%20bugs%20that%20simply%20SHOULD%20NOT%20exist%20in%20production%20level%20software.%20SharePoint%202007%20was%20much%20easier%20to%20install%20than%20this%20'new%20version'.%20Lipstick%20on%20a%20Pig%20if%20you%20ask%20me.%20It%20appears%20that%202019%20will%20be%20more%20of%20the%20same%2C%20since%20I'm%20having%20this%20EXACT%20issue%20on%202016%2C%20which%20has%20been%20in%20production%20for%205%20years%20without%20any%20patches%20for%20this%20misery.%20I%20am%20even%20being%20VERY%20kind%20with%20my%20words.%20Please%20do%20better!%20Stop%20investing%20all%20efforts%20in%20your%20manipulative%20subscription%20model.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1950786%22%20slang%3D%22en-US%22%3ERe%3A%20SharePoint%20fails%20to%20create%20Configuration%20Database%20for%20a%20new%20farm%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1950786%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F232144%22%20target%3D%22_blank%22%3E%40Scott%20Mickelson%3C%2FA%3E%26nbsp%3B%20I%20understand%20your%20frustration%2C%20but%20it's%20important%20to%20note%20when%20installing%20SharePoint%20via%20the%20Prereq%20installer%20UI%2C%20this%20issue%20does%20not%20occur.%20This%20only%20occurs%20when%20admins%20are%20manually%20downloading%20and%20installing%20the%20SharePoint%20prerequisites.%20When%20downloading%20the%20software%20from%20the%20internet%2C%20some%20files%20become%20%22blocked%22%20for%20security%20reasons%20by%20the%20Browser%20%2F%20Operating%20System%20policies.%26nbsp%3B%20If%20the%20installer%20package%20is%20blocked%2C%20it%20would%20need%20to%20be%20executed%20as%20admin%2C%20or%20unblocked%20manually%20to%20ensure%20a%20successful%20installation.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20helps.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E-Mike%3C%2FP%3E%3C%2FLINGO-BODY%3E

Problem Description

 

A new installation of SharePoint fails to provision a new farm due to a failure while creating the configuration database.

 

Example:

 

011118_1934_SharePointf1.png

 

Here is the exception stack from the PSCDiagnostics log:

 

01/11/2018 13:37:00 10 ERR Exception: Microsoft.SharePoint.Upgrade.SPUpgradeException: One or more types failed to load. Please refer to the upgrade log for more details.
at Microsoft.SharePoint.Upgrade.SPActionSequence.LoadUpgradeActions()
at Microsoft.SharePoint.Upgrade.SPActionSequence.get_Actions()
at Microsoft.SharePoint.Upgrade.SPActionSequence.get_ActionsInternal()
at Microsoft.SharePoint.Upgrade.SPUtility.GetLatestTargetSchemaVersionBeforeMajorVersion(Type typeActionSequence, Int32 majorVer)
at Microsoft.SharePoint.Upgrade.SPSiteSequence.get_PreviousTargetSchemaVersion()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.PopulateSequencesTable(StringBuilder sqlstr, Boolean siteSequence)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ConstructSiteNeedsUpgradeQuery(Guid siteId)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.GetSiteNeedsUpgrade(SPUpgradeSession session, SPContentDatabase database, Dictionary`2& dictSitesNeedUpgrade, Dictionary`2& dictSitesNeedFeatureUpgrade)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.AddNextLevelObjects()
at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, Boolean bRecursing, SPDelegateManager delegateManager)
at Microsoft.SharePoint.Upgrade.SPHierarchyManager.Grow(SPTree`1 root, SPDelegateManager delegateManager)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.ReflexiveNeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.NeedsUpgrade(Object o, Boolean bRecurse)
at Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalUpgradeStatus()
at Microsoft.SharePoint.Administration.SPServerProductInfo.DetectLocalProductVersions(SPProductVersions prodVer)
at Microsoft.SharePoint.Administration.SPServerProductInfo.UpdateProductInfoInDatabase(Guid serverGuid)
at Microsoft.SharePoint.Administration.SPFarm.Join(Boolean skipRegisterAsDistributedCacheHost, Nullable`1 serverRole)
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.CreateOrConnectConfigDb()
at Microsoft.SharePoint.PostSetupConfiguration.ConfigurationDatabaseTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

 

Cause

 

This issue can occur if you chose to download and install all the prerequisite software manually, namely in this case the "WCF Data Services 5.6 Tools". If you are experiencing the error, "One or more types failed to load" , while creating a new SharePoint Farm, it's most likely caused by the installer executable being in a "blocked" state while it was installed.

 

Example:

 

011118_1934_SharePointf2.png

 

When executables are downloaded from the internet, they are put into a "blocked" state by to OS, to prevent users from running malicious code. However, in this case, if the installer was in a blocked state when the "WCF Data Services 5.6 Tools" were installed, the install will "succeed' but will not be installed properly.

 

Resolution

 

To resolve this issue:

 

1. Go to the properties of each prerequisite installer package that was downloaded manually and remove the block flag by selected "Unblock" and applying the changes.

 

Example:

 

 

011118_1934_SharePointf3.png

 

 

2. After the file has been unblocked, re-run the installer and choose the repair option.

 

011118_1934_SharePointf4.png

 

3. Finally, re-run the SharePoint Configuration Wizard to successfully create a new Farm.

 

011118_1934_SharePointf5.png

 


Update

 

I wanted to update this blog with a recent discovery that will cause the same issue without the installer appearing to be "blocked".

 

For example:

 

The following image does not show the installer package being in a "blocked" state.

 

unblocked_but_blocked.png

 

How does this occur?

 

This condition can occur of your system is configured with the "Do not preserve zone information in file attachments" policy enabled.

 

Policy:

 

User Configuration > Administrative Templates > Windows Components > Attachment Manager > Do not preserve zone information in file attachments = Enabled

 

Example:

 

policy.png

 

What should  be done?

If you find yourself in this situation, there is a good possibility that additional pre-req software was not installed properly and will cause unexpected outcomes while working with SharePoint.

With that said, please consider the following actions.

 

  1. Disable the "Do not preserve zone information in file attachments" policy and reboot.
  2. Re-run each pre-req package manually and choose the repair option, if applicable.
  3. If the repair options is not offered, uninstall and re-install pre-req installer package.
3 Comments

Thank you for sharing this post!

 

I also experienced this issue in March 2018 and wrote down the details of its resolution and root cause at SharePoint 2016: Failed to create the configuration database. Microsoft.SharePoint.Upgrade.SPUpgrade...


Hope this workaround also helps others!

Occasional Visitor

Amazing! Truly Astounding how much the SharePoint team is an utter failure. This is the most horrific installation process of all software in the 2000s. I've been at this for 25 years and it truly takes effort to fail this hard. I've been working on installing this software for many hours due to broken links, failed prerequisites, mysterious errors and bugs that simply SHOULD NOT exist in production level software. SharePoint 2007 was much easier to install than this 'new version'. Lipstick on a Pig if you ask me. It appears that 2019 will be more of the same, since I'm having this EXACT issue on 2016, which has been in production for 5 years without any patches for this misery. I am even being VERY kind with my words. Please do better! Stop investing all efforts in your manipulative subscription model.

@Scott Mickelson  I understand your frustration, but it's important to note when installing SharePoint via the Prereq installer UI, this issue does not occur. This only occurs when admins are manually downloading and installing the SharePoint prerequisites. When downloading the software from the internet, some files become "blocked" for security reasons by the Browser / Operating System policies.  If the installer package is blocked, it would need to be executed as admin, or unblocked manually to ensure a successful installation.

 

Hope this helps.

 

-Mike