>-----Original Message-----
>One of three things,
>1. A connection timeout
>2. A command timeout
>3. A script timeout
>
>At the top of your ASP page add
><%
>SERVER.SCRIPTTIMEOUT = 360
>%>
>to solve 3
>
>In your connection string or within your with statement
>for your connection string add the following lines.
>
>..connectiontimeout = 360
>..commandtimeout=360
>_________________________________________________________
>WARNING:
>This is only a temporary fix, it does not solve the
>underlying problem which is that your connection, command
>or script is taking too long.
>
>You choices in truely fixing this are varied.
>1. Check your Network (3rd Party tools)
>2. Check your connections (ENT MAN)
>3. Chekc you LOCKS (ENT MAN)
>4. Analyze your transactions (PROFILER)
>__________________________________________________________
>
>Large networks can have a lot of overhead. If your
network
>is just busy all the time, then you may need to bump up
>the timeout setitngs as stated above. I would not go a
>long as 360, I just use this for testing to make sure
that
>I can connect.
>
>Remeber these are captureable errors, and you can
redirect
>to an error page explaining the problem to the user
>delicately.
>
>cjones
>DBA
>
>>-----Original Message-----
>>Need help ....
>>
>>why does this error appears ?
>>
>>Page Cannot be Displayed
>>
>>Error Type
>>Microsoft OLE DB Provider for PDBC Drivers (0x80040E31)
>>[Microsoft][ODBC SQL Server Driver] Timeout expired
>>/login/login_body.asp,line 457
>>
>>Is it the system connection between the SQL server and
>the
>>Web server having problem ?
>>
>>Or scripting on the application ?
>>
>>Pls advise
>>.
>>
>.