![]() |
Sergey Kornilov admin 1/15/2007 |
Looks like a SQL Server timeout issue. dbConnection.CommandTimeout=600 |
M
|
maurello author 1/16/2007 |
It does not work. Actually the server does not time out. The extract simply extract less rows and retrieves that error. |
![]() |
Sergey Kornilov admin 1/16/2007 |
Obviously connection was dropped. That's why I recommended to increase connection timeout. |
M
|
maurello author 1/17/2007 |
I tried again, but nothing changes. As a matter of fact, although the connection timeout is now 600 sec, the connection drops after 20-30 seconds and I retrieve an incomplete file with few rows and at the end the error message from SQL Server. |
![]() |
Sergey Kornilov admin 1/17/2007 |
Some people refer to update that needs to be installed: |
|
Alberto 1/17/2007 |
Sergey, this creation is really good and we appreciate what it does for us but I feel seriously exhausted when dealing with this problem and really doubt that it is related to what we have said in here. |
M
|
maurello author 1/18/2007 |
I think I managed to solve the problem. |
![]() |
Sergey Kornilov admin 1/18/2007 |
Alberto, |
M
|
maurello author 1/19/2007 |
It looks like I solved my problem modifying two value in TCP parameters in the registry of my server. |
|
Alberto 1/19/2007 |
Thanks Mauro. |
![]() |
Sergey Kornilov admin 1/21/2007 |
Alberto, |
M
|
maurello author 1/22/2007 |
Alberto, it looks to me that now the extract works for the database server. However, I think now IIS times out. You should set the ASP Script time out also in IIS for your website. Increase it to 600 for example and try again. I also got the same problem. |
M
|
maurello author 2/1/2007 |
I think I solved the connection timeout once for all. |
![]() |
Sergey Kornilov admin 2/1/2007 |
Mauro, |
|
Alberto 2/12/2007 |
Thanks Mauro, I have tryied your recomendations and there is a good progress. We are very close... |