Could not find schema information for the element 'http://schemas.microsoft.com/.NetConfiguration/v2.0:system.serviceM

Question

using CTP bits i can rebuild the samples and all ok - building my own project i get the following error:

"Could not find schema information for the element 'http://schemas.microsoft.com/.NetConfiguration/v2.0:system.serviceModel'. C:\Documents and Settings\jim\My Documents\Visual Studio 2005\Projects\msnsearchclient\MSNsearchIndigo\app.config 3 6 MSNsearchIndigo"

????

all of this is using VS 2005 beta2.

jim

Answer 1

Hi Jim. Let's try something first: I often get this error when there's something wrong with my code, but the schema errors end up appearing first in the build window. When you have this, scroll through the entire list of warnings and errors and look for a coding error; if you have some fix them and see if the problem recurs.

If not, let us know. Cheers, Ralph

Answer 2

Sounds like you will also need to install the Visual Studio 2005 Extensions for WCF.

http://www.microsoft.com/downloads/details.aspx?familyid=EDE1A645-2A53-42E1-8482-3BF1FADADE06&displaylang=en

This will update DotNetConfiguration.XSD for WinFX.

Answer 3

tried that but did not find any code errors...
thx,
jim

Answer 4

thanks - i've tried that numerous times and the extensions installer keeps complaining that WCF is not installed (yet i can rode sample code that depends on WCF)....so that certainly could be the problem - but the fact that some samples rebuild cleanly makes me wonder what is really going on.
jim

Answer 5

Is this a warning or an error?

In short, are you blocked by this?

Answer 6

it exits the install w/o progress so i assume it is an error. there's nothing in any of the event logs that i can find related to it however.
thx,
jim

Answer 7

Could you uninstall winfx and company and try it again?

Answer 8

The warnings are caused by a line in web.config:

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

Remove the xmlns part so it is:

<configuration>

The warnings will not show up.  The "xmlns" part is added when you use Web Site Administration Tool.

Answer 9

hi jim

i also got erros around 'http://schemas.microsoft.com/.NetConfiguration/v2.' - just after un- and re-installing Framework 2.0 on a W2K Server. in my case i have forgotten to re-configure my webserver to ASP.NET version 2.0 (1.x is the default). after this change (IIS managment console - "your webserver" - properties - asp.net - asp.net version) everything was ok.

god luck, simon

 

Answer 10

I get the following message when I try to use the below configuration. I tried taking out the xmlns and got a real error. What am I doing wrong?? HELP!!!!

<configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0">

 

Message 1 Could not find schema information for the element 'http://schemas.microsoft.com/.NetConfiguration/v2.0:configuration'. C:\Inetpub\wwwroot\Data Source\kpmemorabilia.com\web.config 10 2 C:\...\kpmemorabilia.com\

Answer 11

For one thing, the address http://schemas.microsoft.com/.NetConfiguration/v2.0 does not exist.

Will MS fix this

Answer 12

It's not broken.  A namespace URI doesn't have to exist as such, it's just a unique identifier.

Answer 13

Hi Jim,

I had exactly the same problem but it was just a warning and the real problem was with the output.cs file created by the svcutil.exe for the client that I added to the project.  It did not recognize System.Runtime.Serialization.DataContractAttribute, etc. because I only added a reference to the System.ServiceModel.dll but it also needed a reference to System.Runtime.Serialization.dll before it would compile.

 

Answer 14

I've been banging my head against this Atlas *** since the Orlando VSLive conference and I just can't get it to work. Until it's a helluva lot easier than all this to code Atlas, then AJAX will continue to own Web 2.0.

 

Answer 15

If it's not broken, then how about MS fixing Visual Studio so that it doesn't report errors around it then?

Answer 16

Piotr K. wrote:

The warnings are caused by a line in web.config: <configuration xmlns="http://schemas.microsoft.com/.NetConfiguration/v2.0"> Remove the xmlns part so it is: <configuration> The warnings will not show up.  The "xmlns" part is added when you use Web Site Administration Tool.

 

I think this is the correct answer to the problem... it also affects intellesense inside of the web.config file if you leave the xmlns reference inside of your web.config. (Makes it hard to configure things you don't use often... eh?)

Answer 17

What is the purpose of "xmlns" for the WSA Tool to add it?

 

Answer 18

In my case, Im trying to register new elements into the web.config, using VS 2005. The messages which Ive received are like yours. But they are warnings ( I ) not errors ( X ). I have corrected the errors which were following bellow the warnings and so everything is OK.

Answer 19

I just installed Ajax and got this schema error stuff - sure enough, you were right on! At the bottom of my error list was a coding error! All is now well - at least for the moment!

Thanks, Ralph!

 

Answer 20

 

Well, I ran into the same issue and it turned out security patches reset our IIS server to 1.1 and cleared out the 2.0 extensions and configuration. We reset everything back to 2.0 and things were back in business.

Answer 21

At the bottom of my list were two coding errors -- both in the generated Reference.vb file.  Simple syntax errors

 

how can I fix an error like this in generated code?  I mean, certainly I can do something, but what's the point when I don't have control over the generator...

 

this is the error message:

'Results' is already declared as 'Private Dim results() As Object' in this class.

On this code

        Public ReadOnly Property Results() As CopyResult()
            Get
                Me.RaiseExceptionIfNecessary
                Return CType(Me.results(1),CopyResult())
            End Get
        End Property

 

 

 

 

Answer 22

I installed SP1 for .Net2.0 framework and got an error.  Then ended up re-installing Framework 2.0 and then the service pack.  Every site defaulted back to 1.x so thanks for the post to go back and select 2.0.

Answer 23

Remove the <System.webserver> from the web.config file... it shud work