Memory of the server.
I see things in there like "Mcafee\\xxx" or things like c//users//LOCALAPP
but mainly things like
.
Hopefully it does no harm to the windows OS as it is just reading but still,
it does not look good!
-----Oorspronkelijk bericht-----
Van: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
Namens Boulay, Russ
Verzonden: zaterdag 14 november 2015 16:28
Aan: foxboro@xxxxxxxxxxxxx
Onderwerp: Re: [foxboro] ECB CHAN parameter new but not in ICC ??
Not sure why you are getting different results, but again, depending on the
number of blocks and the offset of parameters, I can see why some may be
good and others not.
But those request from ICC are not going to the CP itself to retrieve info.
They are reporting what is in the workfile.
So not sure when you mention memory locations.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of foxpat
Sent: Saturday, November 14, 2015 7:21 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] ECB CHAN parameter new but not in ICC ??
Thanks for this clear response.
Could we revert back to the 8.8 olist files or would that be a bad idea?
If I understand correctly it is not really something to worry about?
We've got exactly 500 ECB's with the CHAN parm now of which 18 contain
garbage.
A next icc get seems to give different results.
It looks like it is reading from random memory locations as I see some
readable text in there in a few instances.
I do not feel comfortable when parts of memory are read by applications
which should not access that part of memory.
Kind regards,
Patrick Martens
-----Oorspronkelijk bericht-----
Van: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx]
Namens Boulay, Russ
Verzonden: zaterdag 14 november 2015 15:43
Aan: foxboro@xxxxxxxxxxxxx
Onderwerp: Re: [foxboro] ECB CHAN parameter new but not in ICC ??
Your issue is that your current CP workfile (which is what ICC displays when
you open it) and also should match what is running in the CP, is missing
those parameters which are now in your host new updated pdef/olist files.
So when you request an ICCprint or other maintenance type function, the
pdef/olist files are referenced ...create a so called block template for
which the parameters get displayed, but the workfile is missing those
parameters so garbage characters can get into the results because of no real
value...garbage can sometimes get substituted.
This usually occurs if there are many blocks in the workfile that are
missing those parameters, the bigger the list of blocks the more opportunity
for the characters to wraparound and cause garbage characters.
The blocks in the workfile and CP that were there before the upgrade....can
only get those new parameters applied by opening the blocks and selecting OK
to re-apply them....or during a loadall of the CP the new parameters get
added to the workfile and CP as they load.
Obviously cant occur on a running plant.
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On
Behalf Of foxpat
Sent: Saturday, November 14, 2015 4:51 AM
To: foxboro@xxxxxxxxxxxxx
Subject: [foxboro] ECB CHAN parameter new but not in ICC ??
Dear list,
After upgrading 2 of our host servers to I/A 9.2 we noticed a new parameter
CHAN in some of the ECB blocks (ECB1,2,5). This parameter does not show in
ICC but does show up with an icc get all parameters command. Most of the
time the value is empty but sometimes it contains garbage exceeding the
length of a normal parameter value. This caused our in house 'FoxRay' (not
by a long way as good as FoxRay) to crash. As it is 'in-house' I could
simply solve it by trimming the parm value so at least is will continue the
import.
What could be the cause of this?
Wrong iom files or something?
CP images were not upgraded (still 8.8)
The problem is reported to our local support but it would be nice to present
them with the solution on monday.
Kind regards,
Patrick Martens
Zeeland Refinery NL
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which it
is addressed. This e-mail is confidential and may well also be legally
privileged. If you have received it in error, you are on notice of its
status. Please notify the sender immediately by reply e-mail and then delete
this message from your system. Please do not copy it or use it for any
purposes, or disclose its contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________
*** Confidentiality Notice: This e-mail, including any associated or
attached files, is intended solely for the individual or entity to which it
is addressed. This e-mail is confidential and may well also be legally
privileged. If you have received it in error, you are on notice of its
status. Please notify the sender immediately by reply e-mail and then delete
this message from your system. Please do not copy it or use it for any
purposes, or disclose its contents to any other person.
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
_________________________________________________________________________
This mailing list is neither sponsored nor endorsed by Schneider Electric
(formerly The Foxboro Company). Use the info you obtain here at your own
risks. See the disclaimer at 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
