YetAnotherForum
Welcome Guest Search | Active Topics | Log In | Register

PIOLEDB timing out issues Options · View
tomasgendron
#1 Posted : Wednesday, July 28, 2010 8:01:24 PM
Rank: Newbie
Groups: Member

Joined: 7/28/2010
Posts: 2
Location: Canada
Hello, I have frequent problems with my PI server timing out on even simple queries through OLEDB driver (in ASP.NET). A query that sometimes takes < 1 sec will timeout sometimes. Anything obvious to check?

Its against a PI collective PI 3.4.375.80

Any ideas are appreciated! Thanks

Tomas
Sponsor  
 

OSIsoft vCampus is a subscription-based, online offering that consists of providing everything people need to develop applications on the PI System.
We invite you to take a "tour" of the OSIsoft Virtual Campus - also feel free to consult the FAQ  or contact OSIsoft vCampus for more details.
RJK Solutions
#2 Posted : Wednesday, July 28, 2010 10:46:42 PM
Rank: Administration

Groups: Administration

Joined: 6/20/2008
Posts: 617
Location: Cheshire, United Kingdom.
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?
Principal Consultant
Real-Time Data Management @ Wipro Technologies
tomasgendron
#3 Posted : Wednesday, July 28, 2010 11:00:13 PM
Rank: Newbie
Groups: Member

Joined: 7/28/2010
Posts: 2
Location: Canada
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)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.