system.net.webclient: The operation has timed out


hi experts,

"system.net.webexception: operation has timed-out.
at system.net.httpwebrequest.finishgetresponse()
at system.net.httpwebrequest.getresponse()
at system.web.services.protocols.webclientprotocol.getwebresponse()
at system.web.services.protocols.httpwebclientprotocol.getwebresponse()
at system.web.services.protocols.soaphttpclientprotocol.doinvoke()
at system.web.services.protocols.soaphttpclientprotocol.invoke()
at smartdeviceapplication2.localhost1.service.helloworld()
at smartdeviceapplication2.connection.getallkonumlist()
at smartdeviceapplication2.form1.getallkonumlist()
at smartdeviceapplication2.form1.initializeall()
at smartdeviceapplication2.form1._btn_guncelle_click()
at system.windows.forms.control.onclick()
at system.windows.forms.button.onclick()
at system.windows.forms.buttonbase.wnproc()
at system.windows.forms.control._internalwnproc()
at microsoft.agl.forms.evl.entermainloop()
at system.windows.forms.application.run()
at smartdeviceapplication2.form1.main()"

i suffering above mentioned error 2 days. tried solution mentioned on internet such adding the <httpruntime executiontimeout="30000"/>  in web.config. increased time out value in iis but unfortunately i still having same problem. 

i calling web service below

                wshelloworld.service1 obj1 = new wshelloworld.service1();
                string str1 = obj1.helloworld();
                messagebox.show(str1);
                obj1.dispose();
it hello world web service. 

it works 2 calls after throws time out exception.
please me solve problem.



a learner

you need find out why service taking long finish.

john saunders
wcf is web services. not 2 separate things.
use wcf new web service development, instead of legacy asmx or obsolete wse
use file->new project create web service projects


Archived Forums A-B  >  ASMX Web Services and XML Serialization



Comments

Popular posts from this blog

BizTalk Server 2013 Azure VM Log Shipping and HA for hosts

Azure DocumentDB Owner resource does not exist

SQL Server 2008 - High Memory Usage