Re: [foxboro] Historical Trends Lose Historian Cfg on One AW
- From: "Lowell, Timothy" <Timothy.Lowell@xxxxxxxxxxx>
- To: "foxboro@xxxxxxxxxxxxx" <foxboro@xxxxxxxxxxxxx>
- Date: Mon, 8 Nov 2010 11:47:35 -0600
Jack,
You could check d:\etc\histln, d:\etc\histlns, and d:\etc\histlocs on the
affected AW to make sure the correct historian name is in those files. If a
commit install was recently run that has the incorrect historian in it, those
files will get overwritten with the bad historian name (or the bad historian AW
name or host name if it is off-platform) and cause the symptoms you are seeing.
Tim Lowell
Control Systems Engineer
Tesoro Refining and Marketing Company | 19100 Ridgewood Parkway | San Antonio,
TX 78259
210-626-4929 (w) | 210-253-0225 (c) | timothy.lowell@xxxxxxxxxxx
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of Easley, Jack
Sent: Monday, November 08, 2010 11:22 AM
To: foxboro@xxxxxxxxxxxxx
Cc: Keiner, Danny; Adams, Clifford
Subject: [foxboro] Historical Trends Lose Historican Cfg on One AW
We have a problem AW which has a recurring problem losing the historian
configuration for the lines on the trend displays. We are at MESH 8.4.2 and
Foxview 10.1. These same trend displays have no problems on other WP/AWs. You
can reconfigure (permanent) the trend display with the right historian and it
still doesn't work and loses the new historian configuration when the display
is refreshed.
Anyone got any ideas?
Jack Easley
Sr. I&C Technician
Luminant Power, Martin Lake Plant
Phone 903.836.6290
jack.easley@xxxxxxxxxxxx
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
foxboro mailing list: //www.freelists.org/list/foxboro
to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
Other related posts:
