I did it myself, but it was caused by the first situation. Alas, I did not solve it for an hour or two.
Site: http://kb.cnblogs.com/a/1620639/
There are two common causes for this error:
One is, in the config file, configsections is not placed on the top, see the following blog explanation: http://blogs.msdn.com/jongallant/archive/2008/03/02/configuration-system-failed-to-initialize-one-possible-solution.aspx
The other one is that the user. config file is damaged when the configuration items in the user scope are included ......, The user. config file is generally in C:/Documents and Settings/[username]/Local Settings/Application Data/[appcompany]/[appname]/[appversion]/
Of course, you can find it through View details in the error dialog box in the debug debugger of. For more information, see: http://thesprage.com/DasBlog/2008/05/23/ConfigurationSystemFailedToInitialize.aspx
I encountered the second situation, but I haven't done it for a long time.