| |
| Publicado el 29,noviembre 2017 - 14:26 |
Hi,
We have application developed in WINDEV. We have used SQL server. For one procedure we are getting following error:
---------------------------
Adage - VTest - mode DEBUG - base ADAGE_PROD
---------------------------
StatElt - Echec requête Req_Stat_CompDsDossier
OLE DB access error.
Error Number = 170129
Failure opening file.
System Error Details: Description = Query timeout expired
Source = Microsoft OLE DB Provider for SQL Server
SQL State = HYT00
Error Number = -2147217871
Does anyone know why it's happening? How to resolve this? |
| |
| |
| | | |
|
| | |
| |
| Publicado el 29,noviembre 2017 - 17:32 |
Hi
Give it a shout by running SSMS with followings
sp_configure 'remote login timeout', 600
go
reconfigure with override
go
// 600 secs and 0 means unlimited
HTH
King |
| |
| |
| | | |
|
| | |
| |
| Publicado el 29,noviembre 2017 - 17:41 |
You might also need to run "c:\windows\system32\odbcad32.exe" and
click "Connection Pooling" Tab, highlight/click right drivers eg
"Sql Server Native Client 11.0" then change Pool Connetctions to this driver
to 600 secs.
Pls let us know if it works
HTH
King |
| |
| |
| | | |
|
| | |
| |
| Publicado el 29,noviembre 2017 - 17:55 |
| |
| |
| | | |
|
| | |
| |
| Publicado el 29,noviembre 2017 - 20:20 |
It means the query take quite some time to finish, so I would first take the sql-text of your query from within the Windev query editor and paste in the microsoft sql manager to analyze it. See if you need 1 or more extra indexes to speed things up.
If your query is used in a user window (not in some background proces) and runs more than 30 or 60 seconds the user might find this anyoing. Maybe you can break it up in smaller steps and then show some progres between each step. |
| |
| |
| | | |
|
| | |