Config Initialization Failed Windows 11

[Beronike Watkin]

SummaryThe Configuration System Failed to Initialize error usually appears when you try to launch a newly installed app. System file corruption or wrong configuration can be the primary reasons. Fix this issue by running an SFC scan, deleting the old Config file, and other suggested workarounds in this blog.

Missing or corrupted system files could be responsible for the Configuration System File to Initialize error and several other errors like SYSTEM_SERVICE_EXCEPTION and PFN_LIST_CORRUPT errors. You can run the System File Checker (SFC) utility, a Windows built-in troubleshooting utility that can replace the corrupted or damaged versions of system files with the correct ones. Thus, solving the error.

The process may take a while to complete. Once done, see the results; if further instructions are given, follow them. Finally, exit the command prompt and reboot your system to check if the issue is fixed.

Sometimes, third-party applications and related services could be the reason behind Configuration System Failed to Initialize error. You can also perform a clean boot with the following steps to solve the issue.

Update Windows as a last resort. Outdated Windows may also cause issues with your perfectly running system and apps or services and throw the configuration system failed to initialize error. You can look for the pending updates and install them following the given steps:

Bad System Config error is a BSoD (Blue Screen of Death) category error. This error is also called a system configuration error that contains the bug check value of 0xc0000001. It could occur due to outdated device drivers, faulty hard drives, corrupted Windows registry, etc.

System errors can cause issues accessing your programs, services, files and other data. You can use a dedicated data recovery software such as Stellar Data Recovery to recover data even after receiving any error.

It happened to me that I created a webservice in a class library project, then I copied (overwriting) the config file (in order to bring the endpoints configuration) to my windows app and I started to have the same problem. I had inadvertently removed configSections.

If you've added your own custom configuration sections to your App.Config, make sure you have defined the section in the element. I added the my config XML but forgot to declare the configuration section up top - which caused the exception "Configuration system failed to initialize" for me.

I know this has already been answered but I had exactly the same problem in my unit tests. I was tearing my hair out - adding an appSettings section, and then declaring the configuration section as per the answer. Finally found out that I had already declared an appSettings section further up my config file. Both sections pointed to my external settings file "appSettings.config" but the first appSettings element using the attribute file whilst the other used the attribute configSource. I know the question was about the connectionStrings. Sure enough, this happens if the appSettings element is the connectionStrings element being duplicated with different attributes.

Hopefully, this can provide someone else with the solution before they go down the path I did which leads to wasting an hour or two. sigh oh the life of us developers. We waste more hours some days debugging than we spend developing!

Wow it took me forever to figure out this one. For some reason changing the attribute [assembly: AssemblyCompany("CompanyName")] at AssemblyInfo.cs made this error disappear. I was referencing a project that had a different value for the attribute [assembly: AssemblyCompany("CompanyName")]. I maked sure both projects had the same attribute value and it worked great!

It is worth noting that if you add things like connection strings into the app.config, that if you add items outside of the defined config sections, that it will not immediately complain, but when you try and access it, that you may then get the above errors.

This is kinda dumb, but for me I fixed it by doing a get latest from source control on my code. I think there was some new configuration element that was added by someone else, and I needed to overwrite my configuration files. OP shows the error I had gotten, which wasn't really pointing me in the right direction.

I too faced the same problem, But accidentally i written the without writting the ,the previous one should go inside this tags. thus the 'Configuration System Failed to Initialize' error was arising.Hope it will help

In my case, within my .edmx file I had run the 'Update Model From Database' command. This command added an unnecessary connection string to my app.config file. I deleted that connection string and all was good again.

As @Flash Gordon mentioned in his comment, you will need to define any custom tag (as a section) in your App.config file, under . For example, you're working on a test automation project with SpecFlow & adding tag, then a simplest version of App.config will look like this:

Please check your transform files, make sure you remove the unnecessary tags.only the section that are going to vary needs to be there in transform files. dont mention config section in the transform files if not needed. this would also cause the problem.

I upgraded from .net to .netcore. App.config remained in my project, but I had migrated my settings to Settings.settings. The fix for me was removing the .config file from the Debug/Release folders, renaming/removing App.config and re-compiling/re-running the project.

I created a .NET windows service that installs without any issues on the dev machine. On the server that has only the .NET framework (and no VS installed), since I don't have the VS 2008 prompt, I did the following.

Received this error running InstallUtil.exe from the C:\Windows\Microsoft.NET\Framework\v4.0.30319 folder. To fix, try copying the machine.config.default to machine.config (maybe backup your current machine.config if it is actually present in the Config directory).

However, if I recycle the application pool manually and wait 10 seconds, when I then reload the website, I still have to wait another 10 seconds for the website to warm up. This indicates that the website is not starting.

It turned out to be a whole load of settings which all had to be correct. You go through all of the steps to install the relevant components and make the various config changes as per this link: -started/whats-new-in-iis-8/iis-80-application-initialization

The key part which was missing for me was an instruction in the Web.config as below. I had it going to just "/Login" which is a valid route, but as soon as I switched it to "/[Controller]/[Action]" it worked.

The advantage of this route is that you can create a custom action which will also hit the database (initialising Entity Framework), and perform any other slow initialisation you wish. For me, I just read a record out of a DB table, so I get ASP.NET auto-starting, and also save the few seconds it takes to warm up EF too :)

I had similar issues and tried very hard with IIS 8.5 Windows Server 2012 R2. Everything in the IIS was set correctly after referring to so many sites however had missed the Application Initialization setup. Refer to the below link, Setup section.

I have no idea what happened as this appeared to work at first, then weeks later during development it stopped. No amount of tinkering/rework fixed it and I started to suspect I never actually saw this working.

If anyone's wondering what to do in MVC when you have multiple areas to initialise, you need to put the area at the start, all within the root web.config file. I was stuck for a while trying to put it in the area's web.config. Also it's perfectly compatible with hybrid applications.

2014-12-18 09:11:17 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for CentralUsers functional alias, check configuration.

2014-12-18 09:11:34 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for DocumentHistory functional alias, check configuration.

2014-12-18 09:11:52 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ISCoreAudit functional alias, check configuration.

2014-12-18 09:12:08 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ISInternal functional alias, check configuration.

2014-12-18 09:12:28 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ProcessAudit functional alias, check configuration.

2014-12-18 09:12:46 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for ProcessEngine functional alias, check configuration.

2014-12-18 09:13:07 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for TN functional alias, check configuration.

2014-12-18 09:13:26 IST [ISS.0096.0001C] JDBCConnectionManager: initialization failed for Xref functional alias, check configuration.

2014-12-18 09:13:26 IST [ISS.0025.0024I] JDBC Connection Manager started

2014-12-18 09:13:45 IST [ISS.0095.9998E] AuditLogManager Exception: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-12514 Connection refused, the specified service name (orcl) was not recognized by the Oracle server.

com.wm.dd.jdbc.oraclebase.ddej: [SoftwareAG][Oracle JDBC Driver][Oracle]ORA-12514 Connection refused, the specified service name (orcl) was not recognized by the Oracle server.

at com.wm.dd.jdbc.oraclebase.ddcq.b(Unknown Source)

Hello,

I created a storage credential and an external location. Test is ok, I'm able to browse it from the portal.

I have a notebook to create a table :

%sql

CREATE OR REPLACE TABLE myschema.mytable

(

data1 string,

data2 string

)

USING DELTA LOCATION "abfss://mycon...@myaccount.blob.core.windows.net/";

When I'm executing the notebook with a SQL warehouses cluster, it works fine ; with a standard cluster it failed with this error "Failure to initialize configuration for storage account myaccount.dfs.core.windows.net: Invalid configuration value detected for fs.azure.account.key"

I thought it was no longer needed to set fs.azure.account.key. with an external location, am I wrong ? Am I missing something ?

3a8082e126