Http error # 12002 The request has timed out. The session is ending.

[Brian Holmes]

Hello,

I am hoping someone can help me. I have a Win 2003 server Sp2. When I access
a program on the server via the Internet and run a report, I get "Http error
# 12002 The request has timed out. The session is ending." at exactly 30
seconds.

Is there a registry setting I can expand the time to say 30 minutes before
time out?

Thanks

Cheers

Brian

[Jason Viers]

Post by Brian Holmes
Hello,
I am hoping someone can help me. I have a Win 2003 server Sp2. When I access
a program on the server via the Internet and run a report, I get "Http error
# 12002 The request has timed out. The session is ending." at exactly 30
seconds.
Is there a registry setting I can expand the time to say 30 minutes before
time out?

Googling for "Winhttp timeout" returns this as the 4th hit:

http://msdn2.microsoft.com/En-US/library/aa384074.aspx#settimeout

Are you sure that the website you're querying is supposed to take more
than 30 seconds to process your request? It sounds like you might be
solving the symptom, rather than the problem.

Jason

[Jason Viers]

Thanks.
Some of the reports are complicated and take 5-10 minutes to generate

before

the data is sent to the client. It looks link WinInet on the server

views

this as inactivity and Timesout the connection.

That's because there _is_ inactivity in the connection. :) With
something that takes that long to do, a more proper way would be to have
the request kick off background processing and immediately return, and
have further requests check on its status / get the results.

But if this is an internal app and you're ok with the 10 minute idle
connection, then it should work.

Jason