Re: [foxboro] AP failed to connect

Kevin,
Thanks, will add this to my list of things to check when a "feature" pops
up. Guess that for some reason the process didn't start on a boot --r.
Rebooted again late last night and this time everything started backup.
Troy


Troy L. Brazell
Duke Energy Field Services
Sr. Process Control Analyst
ISA CCST
Phone (405) 263 4810 ext. 24
Cell    (806) 898 4340

Okarche C&M
Route 4 P.O. Box 40
Okarche, OK. 73762



                                                                                
                                                       
                      kevin.fitzgerrell@i                                       
                                                       
                      nvensys.com                To:       
foxboro@xxxxxxxxxxxxx                                                       
                      Sent by:                   cc:                            
                                                       
                      foxboro-bounce@free        Subject:  Re: [foxboro] AP 
failed to connect                                          
                      lists.org                                                 
                                                       
                                                                                
                                                       
                                                                                
                                                       
                      10/27/2004 06:47 PM                                       
                                                       
                      Please respond to                                         
                                                       
                      foxboro                                                   
                                                       
                                                                                
                                                       
                                                                                
                                                       





Troy,

My previous reply could have been a little more informative.

If "mles" wasn't running, you can restart by running the go_Amisc script in
/usr/fox/bin.  Then you should look at what else isn't running, and why.
Check if any instances of S99FOXBORO are still running.

Regards,

Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
------------------------------------
Tel:  +64 (9) 573 7690
Fax:  +64 (9) 573 7691



                      kevin.fitzgerrell@i

                      nvensys.com                To:
foxboro@xxxxxxxxxxxxx

                      Sent by:                   cc:

                      foxboro-bounce@free        Subject:  Re: [foxboro] AP
failed to connect
                      lists.org



                      28/10/2004 12:40 PM

                      Please respond to

                      foxboro








Troy,

Check to see if the "mles" process is running.

Kevin FitzGerrell
Systems Engineer
Foxboro New Zealand
------------------------------------
Tel:  +64 (9) 573 7690
Fax:  +64 (9) 573 7691



                      Troy L Brazell

                      <tlbrazell@duke-e        To:
foxboro@xxxxxxxxxxxxx

                      nergy.com>               cc:

                      Sent by:                 Subject:  [foxboro] AP
failed to connect
                      foxboro-bounce@fr

                      eelists.org



                      28/10/2004 11:58

                      AM

                      Please respond to

                      foxboro







Have never had this one before. After a reboot I set the time and then
tried to open the ICC, returned the error "AP failed to connect".
Any suggestions?
Thanks


Troy L. Brazell
Duke Energy Field Services
Sr. Process Control Analyst
ISA CCST
Phone (405) 263 4810 ext. 24
Cell    (806) 898 4340

Okarche C&M
Route 4 P.O. Box 40
Okarche, OK. 73762



_______________________________________________________________________
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








_______________________________________________________________________
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








_______________________________________________________________________
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




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