未能启动。net应用，ConfigurationErrorsException

I've installed a clean XP virtual machine for test purposes, only .NET 3.5 SP1 redistributable is applied.

我已经为测试目的安装了一个干净的XP虚拟机，只应用了。net 3.5 SP1可重分发的。

When I try to start our WinForms app, it gives the following exception:

当我尝试启动我们的WinForms app时，它给出了如下的例外:

System.Configuration.ConfigurationErrorsException: Configuration system failed to initialize ---> System.Configuration.ConfigurationErrorsException: Unrecognized configuration section system.serviceModel. (C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Config\machine.config line 134)

System.Configuration。配置系统初始化失败——>系统配置。ConfigurationErrorsException:未被识别的配置节system.serviceModel。(C:\ WINDOWS \ Microsoft.NET \ Framework \ v2.0.50727 \ Config \机器。配置134行)

The app works on other systems, I've never seen this before. What is extra interesting is that it's such clean machine with "only" XP and .NET 3.5 installed. We are not explicitly using WCF in the app either.

这个应用可以在其他系统上运行，我以前从未见过这个。更有趣的是，它是如此干净的机器，安装了“只有”XP和。net 3.5。我们也没有在应用中显式地使用WCF。

I've seen on some forum that they have removed a section from machine.config, but it feels wrong to have to do that on a clean install, there should be a better solution. Any ideas?

我在一些论坛上看到他们从机器上删除了一个部分。配置，但是在一个干净的安装上做这个感觉是错误的，应该有一个更好的解决方案。什么好主意吗?

6 个解决方案

#1

Looks like an installation issue. There is a bug raise on Connect.

看起来像是安装问题。连接上有一个错误。

http://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=323659

This is offical Microsoft recommendation:

这是微软官方推荐:

In the meantime, you should be able repair your install by running:

同时，您应该能够修复您的安装通过运行:

"%windir%\Microsoft.NET\Framework\v3.0\Windows Communication Foundation\ServiceModelReg.exe" /r /x

”%列出% \ Microsoft.NET \ Framework \ v3.0 \ Windows Communication Foundation \ ServiceModelReg。exe”/ r / x

%windir%\Microsoft.NET\Framework\v3.5\WFServicesReg.exe /c

%列出% \ Microsoft.NET \ Framework \ v3.5 \ WFServicesReg。exe / c

#2

Here is a more relevant MS connect issue. I'm amazed MS haven't fixed this yet.

这里有一个更相关的MS connect问题。我很惊讶MS还没有解决这个问题。

Uninstall 3.5, 3.0 and 2.0 (and any updates) then re-install 3.5. That should do it.

卸载3.5、3.0和2.0(以及任何更新)，然后重新安装3.5。应该做的。

#3

Sounds like an MS config-issue: is the machine otherwise fully patched? Perhaps this got fixed after SP1.

这听起来像是MS config-issue的问题:这台机器是不是已经完全修补好了?也许这个在SP1之后得到了修正。

It's certainly unfortunate that you'd need to edit machine.config (I mean, imagine asking a user to do that...)

很不幸，你需要编辑机器。config(我的意思是，想象一下让用户这样做…)

#4

I have same problem, I am using windows xp 64, my resolve is modify machine.config in:

我有同样的问题，我使用的是windows xp 64，我的决心是修改机器。配置:

%windir%\Microsoft.NET\Framework\v2.0.50727\Config\machine.config

%列出% \ Microsoft.NET \ Framework \ v2.0.50727 \ Config \ machine.config
%windir%\Microsoft.NET\Framework64\v2.0.50727\Config\machine.config

%列出% \ Microsoft.NET \ Framework64 \ v2.0.50727 \ Config \ machine.config

Content of the machine.config you may see the example here: http://weblogs.asp.net/bhouse/archive/2005/11/10/430270.aspx

机器的内容。配置您可以在这里看到这个示例:http://weblogs.asp.net/bhouse/archive/2005/11/10/430270.aspx

#5

I started to get this problem after uninstalling Oracle Client Drivers and it removed my C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\machine.config!

我开始这个问题后卸载Oracle客户机驱动程序和它移除我的C:\WINDOWS\ Microsoft.NET \ Framework \ v2.0.50727 \ machine.config !

Copying it from another computer resolved the problem.

从另一台电脑上复制它解决了这个问题。

#6

-2

I think your application is built by using dotnet framework 2, so try to install 2 not 3.5 and check.

我认为您的应用程序是使用dotnet framework 2构建的，所以请尝试安装2而不是3.5，并进行检查。

C:\WINDOWS\Microsoft.NET\Framework\ v2.0.50727\Config\machine.config line 134

C:\WINDOWS\Microsoft.净框架\ \ v2.0.50727 \ Config \机器。配置134行

#1