Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. Web Development
  3. ASP.NET
  4. Operation has timed out in ASP.Net

Operation has timed out in ASP.Net

Scheduled Pinned Locked Moved ASP.NET
csharpasp-netwcfwindows-adminquestion
4 Posts 3 Posters 1 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • K Offline
    K Offline
    khurram rathor
    wrote on last edited by
    #1

    Hello, I'm developing a web appliation in ASP.Net. My web appliation communicates with Web Services for several operations. Everything is working fine except one operation. Web application uploads a file and send it to web service in the form of Bytes by calling its function. Web Service do some operations on that file, which may take several minutes to let Web Application to wait. But after 90 seconds, my Web Application throughs an exception that the "Operation has timed out". I tried to change the timeout parameters in web.config file like... < httpRuntime executionTimeout="1000" maxRequestLength="409600" useFullyQualifiedRedirectUrl="false" /> also doing this < sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="1000" stateNetworkTimeout = "1000" /> But these things are not controlling that TimeOut Exception. I also tried to change the TimeOut Parameters from IIS but non prevail. Are there any other parameters in web.config file for controlling this Exception? or I will have to do something else. khurram rathor

    B 1 Reply Last reply
    0
    • K khurram rathor

      Hello, I'm developing a web appliation in ASP.Net. My web appliation communicates with Web Services for several operations. Everything is working fine except one operation. Web application uploads a file and send it to web service in the form of Bytes by calling its function. Web Service do some operations on that file, which may take several minutes to let Web Application to wait. But after 90 seconds, my Web Application throughs an exception that the "Operation has timed out". I tried to change the timeout parameters in web.config file like... < httpRuntime executionTimeout="1000" maxRequestLength="409600" useFullyQualifiedRedirectUrl="false" /> also doing this < sessionState mode="InProc" stateConnectionString="tcpip=127.0.0.1:42424" sqlConnectionString="data source=127.0.0.1;Trusted_Connection=yes" cookieless="false" timeout="1000" stateNetworkTimeout = "1000" /> But these things are not controlling that TimeOut Exception. I also tried to change the TimeOut Parameters from IIS but non prevail. Are there any other parameters in web.config file for controlling this Exception? or I will have to do something else. khurram rathor

      B Offline
      B Offline
      Bill Dean
      wrote on last edited by
      #2

      Khurram, Have you tried changing the Timeout property on your proxy class? To do this: 1) make sure you have your web application project set to "show all files" (on the project menu) 2) expand your web application "Web References" 3) expand the web service you're having problem with 4) expand Reference.map 5) Open the Reference.cs file The Reference.cs is the definition of your proxy class, notice it derives from System.Web.Services.Protocols.SoapHttpClientProtocol. Try setting the Timeout property higher (I'd do this in the constructor). The default is 100000 ms (right about where you timeout, right?) You can set it to Timeout.Infinite if you want, at which point it's up to IIS to timeout the request. Hope this helps, Bill

      K V 2 Replies Last reply
      0
      • B Bill Dean

        Khurram, Have you tried changing the Timeout property on your proxy class? To do this: 1) make sure you have your web application project set to "show all files" (on the project menu) 2) expand your web application "Web References" 3) expand the web service you're having problem with 4) expand Reference.map 5) Open the Reference.cs file The Reference.cs is the definition of your proxy class, notice it derives from System.Web.Services.Protocols.SoapHttpClientProtocol. Try setting the Timeout property higher (I'd do this in the constructor). The default is 100000 ms (right about where you timeout, right?) You can set it to Timeout.Infinite if you want, at which point it's up to IIS to timeout the request. Hope this helps, Bill

        K Offline
        K Offline
        khurram rathor
        wrote on last edited by
        #3

        Yes, it did work, its working successfully.:rose: I really appreciate your help, you r great Bill. Thanks a lot. Hope for further cooperation.. in future. khurram rathor

        1 Reply Last reply
        0
        • B Bill Dean

          Khurram, Have you tried changing the Timeout property on your proxy class? To do this: 1) make sure you have your web application project set to "show all files" (on the project menu) 2) expand your web application "Web References" 3) expand the web service you're having problem with 4) expand Reference.map 5) Open the Reference.cs file The Reference.cs is the definition of your proxy class, notice it derives from System.Web.Services.Protocols.SoapHttpClientProtocol. Try setting the Timeout property higher (I'd do this in the constructor). The default is 100000 ms (right about where you timeout, right?) You can set it to Timeout.Infinite if you want, at which point it's up to IIS to timeout the request. Hope this helps, Bill

          V Offline
          V Offline
          vijrumbhan
          wrote on last edited by
          #4

          hi i have a similar problem "the operation timeout exception". actually mine is a device application which connects with the web service to send or fetch data. when my web service was on the local system everything was fine but when i deployed it on to server this exception araised. i tried by increasing timeout n maxlength too but it doesnt work can you help me

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups