Re: [foxboro] Alarm History Update Problem

Could this be your problem?

Regards,

Patrick Martens


From an earlier thread:


When I found that the problem I created extended beyond our in-house
applications and prevented Alarm History from functioning, I called Invensys
for help.  Gianluca Alfani found the answer.  What he found was curious.
Since I believe I am not the only who will ever swap two WPs, I thought I
would pass along the information.
There is an ASCII file, /etc/fox/loghost, that should contain the name of
the logical host, i.e. the local AP or AW.  The two stations I swapped had
their own identity in /etc/fox/loghost. The other WPs in the room had the
correct information in /etc/fox/loghost.  The modification date on the
loghost files of the swapped stations was the same as the day that I first
tried to swap the machines.  The loghost file on the workstations I did not
change had a modification date that corresponded to the date we last
upgraded our software.

I believe I created a problem for myself when I forgot to change the DNBIs
the first time I tried to swap the workstations.  Apparently, when the ID of
the workstation and the ID of the DNBI did not match at boot up, the loghost
file got changed.  I don't know what did it or why... I only know that it
happened.

The proper procedure for swapping the location of two WPs is to power down
both workstations and their DNBIs.  Swap the annunciator panels and swap the
letterbugs on the DNBI.  Power up the DNBIs, then power up the WPs.


Chuck Jones
Refinery Automation Technologist
Tate & Lyle -- Lafayette South Plant
765.477.5324 - Office  | 877.536.9219 - Pager

"Growing up, I always wanted to be somebody.  I guess I should have been
more specific." -- Lily Tomlin


----- Original Message ----- 
From: "Ali Ahmed" <alizahidi@xxxxxxxxxxx>
To: <foxboro@xxxxxxxxxxxxx>
Sent: Friday, December 30, 2005 11:04 AM
Subject: [foxboro] Alarm History Update Problem


Hi All,
We have three WP51Ds connected with an AW51E on nodebus. We are facing alarm
history update problem on alarm history display page on two of the three
WPs. When we call alarm history page from Current Alarm Display (CAD) the
following error message appears.

"Unable to open alarm history file for hist02 on 03AW02"


where, hist02 is our historian instance name and 03AW02 is letter ID of our
AW51E. To rectify this problem we rebooted the WPs but the problem remains
same. We cannot reboot the AW for some time due to some reason. Is there any
way to get rid of this problem without rebooting AW. Kindly advise.

Thanks & Best Rgds,
Ali Ahmed Zahidi
Pakistan Refinery Ltd.
Karachi, Pakistan.

_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/



_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave



 
 
_______________________________________________________________________
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:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: