Re: [foxboro] Load MESH FCP Using iccdrvr.tsk and Print File format

Tom,
I think Sean is right,  we have seen the inverse of this problem, 
where icc will not connect, but iccdrvr.tsk continues to work.  A 
reboot of the AW has fixed this problem in the past.  So did you have 
an iccdrvr.tsk process terminate abnormally prior to this 
problem.  Also weird icc things tend to start happening if CSA is 
lost during a session.

Good Luck, and vote for me..... I'm saner than Kuchinich, meaner than 
Guiliani, more optimistic than Obama, smarter than Ron Paul, prettier 
than Hillary and younger than any of them.

Regards,
David

PS from the email flood of out of the office replies it's a wonder 
that anything get's done in December.  Merry Christmas ya'll.

At 02:27 PM 12/20/2007, you wrote:
>Tom,
>
>Looks like the IPC task name has already been registered.  Try 
>running sipc to see if you currently have a process registered with 
>something like ICCAPI[CPNAME]
>cd /opt/fox/bin/tools
>sipc
>list dt
>

 
 
_______________________________________________________________________
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: