You probably have a locked IPC channel (the channel reserved for ICC)
Call GCS and have them step you through SOL2974 or SOL2483
________________________________________
From: foxboro-bounce@xxxxxxxxxxxxx [foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of
Jordan B [jordanjbraun@xxxxxxxxx]
Sent: Friday, January 06, 2017 11:27 AM
To: foxboro@xxxxxxxxxxxxx
Subject: Re: [foxboro] ICC not connecting to FCP270
Checked, there are no active locks on the win host
Checking "ps | grep ciocfg" - application isn't running
The same host launches ICC against a second CP without issue (TRCP01)
I tried running check_db_sync.ksh against the CP (LRCP01) it gives the
error "ICCAPI FAILED - icConnectCp: icCpConnect problem"
Running check_db_sync against TRCP01 (on the same AW) comes back as in
proper sync.
On Thu, Jan 5, 2017 at 6:36 PM, Goldie, Shaun S
<Shaun.Goldie@xxxxxxxxxxxxxxxxxx> wrote:
Assuming there are no lock files on the win host
Check for and kill ICC if its running
Standard caveat I Know What I Do
Ps for ciocfg and the result will show if ciocfgtask is running
It can be killed there is a chance the change being done when the session got
left open will get lost
-----Original Message-----
From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On ;
Behalf Of Jordan B
Sent: Friday, 6 January 2017 10:28 a.m.
To: foxboro-request@xxxxxxxxxxxxx; foxboro@xxxxxxxxxxxxx
Subject: [foxboro] ICC not connecting to FCP270
Our site has a mix of primarily old Unix AW’s as well as a small MESH
installation. The MESH side only has a single AW (P90) with two WP’s
(P92s) and acts as the CSA host for the network, ICC is still used for
configuration.
The MESH AW (P90) hosts two FCP270’s, both of which have been in production
for a number of years now.
Over the holiday, one of the CP’s (LRCP01) stopped working with ICC
- Launch ICC against LRCP01
- "Communication to CP (-23) Failed. Select CONTINUE to Proceed"
- I select CONTINUE
- "iuc_ or uc_open Failed. Select CONTINUE to Proceed"
- I select CONTINUE and it drops back to COMPOUND select
Here's what I've looked at / tried so far:
- Rebooted AW
- Checked sldb, MESH AW shows as host for that CP
- CP is online
- CP can be pinged from the AW
- Detail displays show good data
- STATION block doesn't show wrong
- 82% station idle time, no Overruns
- CP can be selected from System Management Display Handler
- Rebooted each CP individually
One unusual thing I found was one of the UNIX AW's had a lock file for the
LRCP01, the sldb showed that it was not hosted by the UNIX AW, I deleted the
LRCP01 files on that node and checked all the other UNIX nodes, none had
anything. Now, when I try and launch ICC against
LRCP01 from the UNIX node it gives "New SP Error - lck_chkpt Failed.
Select CONTINUE to Proceed", which is what I expect when trying to launch ICC
on a UNIX node against a MESH CP.
The ICC Foxboro Documentation lists the IUC or UC_OPEN Error, but in regards
to the database being locked.
There are probably a couple other things I've tried but forgot to document
during troubleshooting.
I'd appreciate any help!
Thanks,
Jordan Braun
KapStone Paper, Longview, Wa
_________________________________________________________________________
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
________________________________
NOTICE - This message and any attached files may contain information that is
confidential, legally privileged or proprietary. It is intended only for use
by the intended recipient. If you are not the intended recipient or the
person responsible for delivering the message to the intended recipient, be
advised that you have received this message in error. Any dissemination,
copying, use or re-transmission of this message or attachment, or the
disclosure of any information therein, is strictly forbidden. BlueScope Steel
Limited does not represent or guarantee that this message or attachment is
free of errors, virus or interference.
If you have received this message in error please notify the sender
immediately and delete the message. Any views expressed in this email are not
necessarily the views of BlueScope Steel Limited.
_________________________________________________________________________
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
