By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,853 Members | 1,034 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,853 IT Pros & Developers. It's quick & easy.

Missing required Web services section of Web.config when determining Soap Protocol version

P: n/a
ken
We have a user that has reported the following error when starting up
our client application that uses a web service on our back end:

System.Configuration.ConfigurationException: Missing required Web
Services section of the Web.config file.
at
System.Web.Services.Configuration.WebServicesConfi guration.get_Current()

at System.Web.Services.Protocols.SoapClientType..ctor (Type type)
at System.Web.Services.Protocols.SoapHttpClientProtoc ol..ctor()

This is in the call to instantiate the web services proxy on the client
side, which has a class declaration like the following (this is just to
show you it's the standard web service in a client):

public class MyWebService :
System.Web.Services.Protocols.SoapHttpClientProtoc ol
>From what I can tell, the user has .Net 2.0 (we compile with 1.0) and
in 2.0, the client has the ability to choose to use Soap 1.1 or Soap
1.2 and it goes to the web.config file to figure this out. In the
web.config file that comes with .Net 2.0, there is no webservices
section and I think that is why we get this error.

I added a web services section to a copy of the web.config file and
placed it in our "program files" application startup directory, but
still get the missing required section error. What I added to the
web.config file is the following:

<webServices >
<protocols>
<remove name="HttpSoap12"/>
</protocols>
</webServices>

Any ideas or suggestions?
Thanks,
Ken

Nov 7 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
<ke*@soundflavor.comwrote in message
news:11*********************@m7g2000cwm.googlegrou ps.com...
We have a user that has reported the following error when starting up
our client application that uses a web service on our back end:

System.Configuration.ConfigurationException: Missing required Web
Services section of the Web.config file.
at
System.Web.Services.Configuration.WebServicesConfi guration.get_Current()

at System.Web.Services.Protocols.SoapClientType..ctor (Type type)
at System.Web.Services.Protocols.SoapHttpClientProtoc ol..ctor()

This is in the call to instantiate the web services proxy on the client
side, which has a class declaration like the following (this is just to
show you it's the standard web service in a client):

public class MyWebService :
System.Web.Services.Protocols.SoapHttpClientProtoc ol
>>From what I can tell, the user has .Net 2.0 (we compile with 1.0) and
in 2.0, the client has the ability to choose to use Soap 1.1 or Soap
1.2 and it goes to the web.config file to figure this out. In the
web.config file that comes with .Net 2.0, there is no webservices
section and I think that is why we get this error.

I added a web services section to a copy of the web.config file and
placed it in our "program files" application startup directory, but
still get the missing required section error. What I added to the
web.config file is the following:
Is your client application a web application? If not, it won't be using
web.config.

If the application is named C:\program files\something\foo.exe, then you
need a C:\program files\something\foo.exe.config.

John
Nov 8 '06 #2

P: n/a
Did you ever find a work-around for this? I'm having the exact same
problem. What did you add to your app.config in order to mimic the
presence of a web.config with a services section? I've tried just
cutting and pasting the "system.web" section from the web.config into
the app.config but that didn't work. I must be missing something but I
don't know what.

John Saunders wrote:
<ke*@soundflavor.comwrote in message
news:11*********************@m7g2000cwm.googlegrou ps.com...
We have a user that has reported the following error when starting up
our client application that uses a web service on our back end:

System.Configuration.ConfigurationException: Missing required Web
Services section of the Web.config file.
at
System.Web.Services.Configuration.WebServicesConfi guration.get_Current()

at System.Web.Services.Protocols.SoapClientType..ctor (Type type)
at System.Web.Services.Protocols.SoapHttpClientProtoc ol..ctor()

This is in the call to instantiate the web services proxy on the client
side, which has a class declaration like the following (this is just to
show you it's the standard web service in a client):

public class MyWebService :
System.Web.Services.Protocols.SoapHttpClientProtoc ol
>From what I can tell, the user has .Net 2.0 (we compile with 1.0) and
in 2.0, the client has the ability to choose to use Soap 1.1 or Soap
1.2 and it goes to the web.config file to figure this out. In the
web.config file that comes with .Net 2.0, there is no webservices
section and I think that is why we get this error.

I added a web services section to a copy of the web.config file and
placed it in our "program files" application startup directory, but
still get the missing required section error. What I added to the
web.config file is the following:

Is your client application a web application? If not, it won't be using
web.config.

If the application is named C:\program files\something\foo.exe, then you
need a C:\program files\something\foo.exe.config.

John
Jan 5 '07 #3

This discussion thread is closed

Replies have been disabled for this discussion.