After the SQL server2008 is loaded, the Machine.config line136 is always present, or a configuration section system.servicemodel that is not recognized by the configuration error.

Source: Internet
Author: User

Suspect that the problem is caused by a conflict between VS and SQL Server2008 installation.

There is one such argument:

With win8.1 64-bit system, if first installed VS2010, and then installed SQL Server R2, not at all, the initial error.

So first install SQL Server R2 success, and then install vs2010/2013 also successful, then SQL Server MANAGEMEMT Stiduo will not open!

The error is. NETFramework, said to be the exception that occurred in the application's components, the details inside a bunch of exception text, click Continue! Finally, the connection window pops up! Attempt to connect, error message prompt appears again

See the message that it pops up, knowing that the configuration system failed to initialize and that the configuration node (System) could not be recognized. Configuration), (c:\windows\microsoft.net\framework\v2.0.50727\config\machine.config,line136), it seems that the problem is here.

Check online, there is no good solution, or vague. The way I take it is

1) Install SQLSERVER2008R2 First, and then back up the file C:\Windows\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config

2) Install the vs2010/2013, and then restore the backup files, the new files are discarded.

With this method, both SQLSERVER2008R2 and vs2010/2013 operate normally.

However, you can use this method to resolve the problem without reinstalling:

<sectiongroup name= "System.ServiceModel" type= "System.ServiceModel.Configuration.ServiceModelSectionGroup, System.ServiceModel, version=3.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089 "> <section name=" Behaviors "Type=" System.ServiceModel.Configuration.BehaviorsSection, System.ServiceModel, version=3.0.0.0, Culture =neutral, publickeytoken=b77a5c561934e089 "/> <section name=" bindings "type=" System.ServiceModel.Configuration.BindingsSection, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "/> <section name=" Client "type=" System.ServiceModel.Configuration.ClientSection, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "/> <section name=" comcontracts "type=" System.ServiceModel.Configuration.ComContractsSection, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "/> <section name=" commonbehaviors "type=" System.serviceModel.Configuration.CommonBehaviorsSection, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken= b77a5c561934e089 "allowdefinition=" MachineOnly "allowexedefinition=" MachineOnly "/> <section name=" Diagnostics "Type=" System.ServiceModel.Configuration.DiagnosticSection, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "/> <section name=" extensions "type=" System.ServiceModel.Configuration.ExtensionsSection, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "/> <section name=" machinesettings "type=" System.ServiceModel.Configuration.MachineSettingsSection, Smdiagnostics, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "allowdefinition=" MachineOnly "allowexedefinition=" MachineOnly "/> <section Name= "serviceHostingEnvironment" type= "System.ServiceModel.Configuration.ServiceHostingEnvironmentSection, System.ServiceModel, version=3.0.0.0, culture=nEutral, publickeytoken=b77a5c561934e089 "/> <section name=" Services "type=" System.ServiceModel.Configuration.ServicesSection, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "/> </sectionGroup> <sectiongroup name=" system.serviceModel.activation "Type=" System.ServiceModel.Activation.Configuration.ServiceModelActivationSectionGroup, System.ServiceModel, version=3.0.0.0, Culture=neutral, publickeytoken=b77a5c561934e089 "> <section name=" Diagnostics "type=" System.ServiceModel.Activation.Configuration.DiagnosticSection, System.ServiceModel, version=3.0.0.0, culture= Neutral, publickeytoken=b77a5c561934e089 "/> <section name=" net.pipe "type=" System.ServiceModel.Activation.Configuration.NetPipeSection, System.ServiceModel, version=3.0.0.0, culture= Neutral, publickeytoken=b77a5c561934e089 "/> <section name=" net.tcp "type=" System.ServiceModel.Activation.Configuration.NetTcpSection, System.ServiceModel, Version=3.0.0.0, culture=neutral, publickeytoken=b77a5c561934e089 "/> </sectionGroup>  

  

Add it to the configsections in the C:/windows/microsoft.net/framework/v2.0.50727/config/machine.config file.

http://blog.csdn.net/zdw_wym/article/details/40892535

Can take a look at this paste description

http://tieba.baidu.com/p/3556607480

After the SQL server2008 is loaded, the Machine.config line136 is always present, or a configuration section system.servicemodel that is not recognized by the configuration error.

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.