RJK Solutions wrote:Hi Tomas,
As OLEDB is translated to PISDK calls, I would check the pipc.log file on the machine running your asp.net application to see if it lists any connection issues.
Is there anything consistent like the time in between failures of your query?
Hi, thanks for the response. the pipc.log on the server has just has these entries (the last timeout was at 9:52:08am). PNPICLNT.exe is not the app that had the Timeout error though and the log is full of connects with PNPICLNT.ext (ProcessNet i'm sure). There is no consistent pattern for timeouts as far as we can tell. Is there some log settings that should be set to gather better data? Thanks!
28-Jul-10 09:46:58
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:52:34
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:52:34
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:52:34
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:52:35
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:52:35
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:52:35
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:56:01
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
28-Jul-10 09:58:41
PNPICLNT.exe>PI-API> Initial connection to [FPIPRD001:5450][0]
I did find several of these errors for the PNPICLNT.EXE so it seems to have intermittent timeouts as well.
25-Jul-10 18:05:04
PNPICLNT.exe>PI-API> pinetread> select timeout, host FPIPRD001:5450 not responding
(FPIPRD001 is our primary node)