Re: [foxboro] ICC to CP disconnect
- From: Sascha Wildner <swildner@xxxxxxxxxx>
- To: foxboro@xxxxxxxxxxxxx
- Date: Wed, 20 Feb 2008 13:07:41 +0100
Kevin Fitzgerrell wrote:
> One other possible cause of the problem is that you had a compound in
> a control station or work volume with the same name as the problem CP,
> and deleted the compound. As part of the cleanup, deleting a compound
> deletes the /opt/fox/ciocfg/COMPOUNDNAME directory - in this case also
> the /opt/fox/ciocfg/CPLBUG directory with the CP workfiles. Naming a
> compound with a CP letterbug is illegal but isn't impossible -
> entering a CP letterbug in the choice field in the compound selection
> screen of the ICC will cause the creation of a compound in volwrk with
> the same name as your CP. I'm not aware of this issue having been
> corrected.
>
> If you are missing the /opt/fox/ciocfg/CPLBUG directory, or it is
> empty except for an initialized workfile and .O files (they should
> have been recreated as initial files when you tried ICC on this CP and
> found nothing), I'd consider this scenario a possibility.
Hah, I had this very same problem when I created an API compound on a
Windows system, deleted it again and found to my astonishment that the
ICC had happily deleted the /opt/fox/ciocfg/api directory. Thank you, ICC.
It's rather embarassing if you have to explain to your customer why the
directory is gone.
Regards,
--
Sascha Wildner
erpicon Software Development GmbH
Neusser Str. 724-726
50737 Köln
Germany
Phone: +49 221 9746089
Fax: +49 221 9746099
Mobile: +49 174 9887655
eMail: swildner@xxxxxxxxxx
_______________________________________________________________________
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
- Follow-Ups:
- Re: [foxboro] ICC to CP disconnect
- From: Gunter, Matt
- References:
- [foxboro] ICC to CP disconnect
- From: Gunter, Matt
- Re: [foxboro] ICC to CP disconnect
- From: Kevin Fitzgerrell
- Re: [foxboro] ICC to CP disconnect
- From: Kevin Fitzgerrell
Other related posts:
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- » Re: [foxboro] ICC to CP disconnect
- Re: [foxboro] ICC to CP disconnect
- From: Gunter, Matt
- [foxboro] ICC to CP disconnect
- From: Gunter, Matt
- Re: [foxboro] ICC to CP disconnect
- From: Kevin Fitzgerrell
- Re: [foxboro] ICC to CP disconnect
- From: Kevin Fitzgerrell