I have seen a similar situation occur at another customer site. During the upgrade between IA versions they had many CP's that they did not want to reboot. So they copied older workfiles onto a newer version of IA Iccdrvtsk would then get hung because the pfef/olist files on the upgraded host had many extra parameters to support the new version of IA When an iccdrvtsk command was attempted ...those pdef/olist parameters attempted to make the parameter request in the old workfile and this would cause the iccdrvtsk command to hang.... So main point......be sure a similar situation has not occurred where old workfiles are resident on a newer version host. Their way out of this issue was to perform loadalls onto a offline lab upgraded system...and then copy those workfiles to the online host. -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Ricardo Abech Sent: Friday, November 23, 2012 5:55 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] ICCDRVR - Workfile corruption? Hi Hizamri, Yes, one of the CPs also behave like that (endless dump) .. Those issues it only happens in CPs from stations where they had a bad VIRUS problem ... so even after day 0ing the machine, I guess the workfiles are still corrupted ... They cant initialize the CPs for now, so I guess we are stuck with this problem ... Thanks On Nov 23, 2012, at 4:19 AM, Hizamri Johari wrote: Dear Recardo Optimal do not have windows version yet.. But we do have a couple of CP workfile corruptted.. If we execute GET *:* ALL or do db_sync.. it will goes to endless loops.. the output file will grow until we ran out of hdd space.. I am not sure of the exact best solution, but initialize, reboot and load all will do the trick.. we have done successfully on one CP.. we will initialize the the next CP when ever permissible... God knows best.. Best regards.. Hizamri ----- Original Message ----- From: "Ricardo Abech" <abech@xxxxxxxxxxxx> To: <foxboro@xxxxxxxxxxxxx> Sent: Friday, November 23, 2012 6:38 AM Subject: [foxboro] ICCDRVR - Workfile corruption? > Hi List, > > I have a issue in a client that when running iccdrvr.tsk on windows and > getting data from a CP (using: GET *:* ALL) we end up with TRASH on the > output file. > > see one example below: > > SUPOPT = MAN_HTM_PATHS=/D=/nutc/etc/htm/perl:/D=/nEND > > It shows at least 5 or 6 times in the CP dump, and every time we dump > looks like it is in a different place (different parameters). > > I believe it must be some sort of workfile corruption or maybe some > version of the api? But it is happening in at least 15% of the CPs in the > plant... The CPs looks like it is working normally, but also after > ICCDVR.TSK is finished it trows a lot of Nutcracker errors causing the CP > to lock, then the + file needs to get deleted (from /usr/fox/sp/locks) > before the ICC be able to open the CP again .. > > Anyone has seem this before? > > Any ideas? Fixes? QF? > > Thanks! > > _______________________________________________________________________ > 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 > > > > ----- > No virus found in this message. > Checked by AVG - www.avg.com > Version: 2013.0.2793 / Virus Database: 2629/5910 - Release Date: 11/21/12 > _______________________________________________________________________ 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 _______________________________________________________________________ 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 *** 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 email comes from a division of the Invensys Group, owned by Invensys plc, which is a company registered in England and Wales with its registered office at 3rd Floor, 40 Grosvenor Place, London, SW1X 7AW (Registered number 166023). For a list of European legal entities within the Invensys Group, please select the Legal Entities link at invensys.com. You may contact Invensys plc on +44 (0)20 3155 1200 or e-mail reception@xxxxxxxxxxxx. This e-mail and any attachments thereto may be subject to the terms of any agreements between Invensys (and/or its subsidiaries and affiliates) and the recipient (and/or its subsidiaries and affiliates). _______________________________________________________________________ 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