> =20 > Subject: Could not Call up ICC Control Configrator in I/A=20 > V6.1.2 AW51B >=20 > Ken Heywood forwarding this message to foxboro@xxxxxxxxxxxxx for Tom > VandeWater, >=20 > Mohamed, > You don't mention what software release you are running. We > recently experienced a similar issue when we were running=20 > Ver.6.2.1 on all > of our 51 series sun boxes and Ver.7.1 on our new AW-XP=20 > boxes. We were > unable to access the ICC on the AW-XP box, even though it=20 > hosted a CP), > until we made it the CSA server. I'm assuming by your AW=20 > names, (AW5101-02) > that you only have AW51's but are they running the same=20 > software version. > If not, it is NOW important that the CSA server be running on the most > current software version!! =20 > If this is not the problem, have you tried rebooting=20 > AW5101. That > is the universal Foxboro answer and it sometimes works, even=20 > though I like > to know the reason why things quit working. > I hope this helps and please let everyone know what=20 > finally fixes > your problem. >=20 > Thanks, > Tom VandeWater > Control Systems Developer/Analyst > Dow Corning Corp. > Carrollton, KY USA >=20 >=20 > -----Original Message----- > From: foxboro-bounce@xxxxxxxxxxxxx > [mailto:foxboro-bounce@xxxxxxxxxxxxx]On Behalf Of Nasif, Mohamed > Sent: Sunday, January 11, 2004 3:29 PM > To: foxboro@xxxxxxxxxxxxx > Subject: [foxboro] Could not Call up ICC Control Configrator in I/A > V6.1.2 AW51B >=20 >=20 > Hi all, > Anybody faced similar problem, recently, the Control=20 > Configurator could not > be called up > when invoked from AW5101 using the CIO_Config pulldown menu,=20 > or using the > CIO_STN_Cfg to pick individual stations, expect station=20 > AW5102 (hosts DI50 > gateway) that is called properly. >=20 > * After picking CIO_Config from AW5101 or picking=20 > CIO_STN_Cfg > for any CP or GWY (except AW5102), I'm getting the messages=20 > like "Sending > Message to.............", then "Failed to send message to AP"=20 > and "Error in > sending message to AP" >=20 > * From AW5101 or AW5102 the ICC is called with no single > problem (called from AW5101 by picking CIO_STN_Cfg for the=20 > AW5102 station). >=20 > * Once ICC is running (only for AW5102 station),=20 > it displays > all the compounds and blocks in the Configurator listing,=20 > however picking a > compound in any CP or GWY will lead to same error messages.=20 >=20 > * After the ICC call, I checked that if rem_strt=20 > is running, > ps -aef|grep rem_strt returns nothing, i.e. rem_strt 5 not running. >=20 > * I checked that if CSA Server is running, ps -aef|grep > CSA_SERV returns that CSA_SERVER is running. >=20 > * I'm not sure how to check if TMHST is set in CIO_Config > script. >=20 > * Checked that logical host is defined properly=20 > (AW5101) in > etc/fox/loghost.=20 >=20 > * Checked that related files/scripts exists, but how can I > know if they are intact. > /usr/fox/wp/bin/mk_glbs.sh > /usr/fox/sp/IIF.prm, > /usr/fox/bin/rem_strt > /usr/fox/bin/run_cio=20 > /etc/fox/rc/deflbug =20 >=20 > * Checked if that environment files in /opt/fox/env or > opt/customer/env altered or deleted. Found no change. >=20 > * Is it possible that CSA database is corrupted? >=20 > How to get back the ICC, any ideas ? >=20 > Thanks alot in advance for input. >=20 > Regrads, >=20 > Mohamed Nasif > Control & Inst. Engineer >=20 >=20 >=20 >=20 >=20 >=20 >=20 >=20 _______________________________________________________________________ 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