That is my understanding, but Julie is the one that would know. Regards, Alex Johnson Invensys Operations Management 10900 Equity Drive Houston, TX 77041 +1 713 329 8472 (desk) +1 713 329 1600 (operator) +1 713 329 1700 (Central Fax) alex.johnson@xxxxxxxxxxxx -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of David R. Johnson Sent: Friday, March 15, 2013 7:14 AM To: foxboro@xxxxxxxxxxxxx Subject: Re: [foxboro] AIM*OPC Server CLOSE_WAIT errors Well that's good news. I'd still like to get the OPC interface working correctly, but I'm glad that fxbais is still going to be supported. I would assume the new foxbais would work at older I/A release levels with aim API installed. Do you know if that is the case? Regards, David "Johnson, Alex P (IOM)" <Alex.Johnson@xxxxxxxxxxxx> wrote: >Fxbais is update for V8.8 and is available from OSI. I saw the release notice. > >Grant and I helped them update it. > >Regards, > >Alex Johnson >Invensys Operations Management >10900 Equity Drive >Houston, TX 77041 >+1 713 329 8472 (o) >alex.Johnson@xxxxxxxxxxxx >Sent from my iPhone. Please forgive the typos. > >On Mar 15, 2013, at 6:36 AM, "Johnson, David" ><David.Johnson@xxxxxxxxxxxxxxxxxx> wrote: > >> The server has not been recently modified as far as we know. It seems the >> problem has been with us since we put AIM*OPC Server on the box. I believe >> there are other entries in the an_init.tcp file for the other AWs. I will >> check that tomorrow morning and post my findings. >> >> We are testing the OPC interface to PI (and I'm glad this is just a test) >> because I think the fxbais legacy interface is going to quit working at I/A >> version 8.8 when FoxAPI is no longer supported. Does anyone know for sure? >> >> That's all for today. >> >> Thanks everybody. >> David >> >> >> -----Original Message----- >> From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On >> Behalf Of Michael Toecker >> Sent: Thursday, March 14, 2013 3:35 PM >> To: foxboro@xxxxxxxxxxxxx >> Subject: Re: [foxboro] AIM*OPC Server CLOSE_WAIT errors >> >> Was the PI server recently upgraded to Windows 2008 R2, or received patches? >> I"m working a theory here. >> In the meantime, you can use TCPView from Microsoft Sysinternals to >> !!!!CAREFULLY!!!! kill zombie (close_wait) connections on a periodic basis. >> (http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx) >> >> Mike Toecker >> Digital Bond, Inc >> >> On Thu, Mar 14, 2013 at 12:57 PM, Ted Jirik <ted.jirik@xxxxxxxxxxxxxxx>wrote: >> >>> David, >>> >>> Also be sure there is nothing in the AIM* Servers field in the opc >>> server configurator / server parameters (advanced) tab >>> >>> Ted >>> >>> On Mar 14, 2013, at 10:37 AM, Ted Jirik <ted.jirik@xxxxxxxxxxxxxxx> wrote: >>> >>>> David, >>>> >>>> Just spoke to our field service rep and he verified my thinking. >>>> That is >>> what we did to solve it at two sites. >>>> >>>> Reboot after changes? >>>> >>>> Be sure other servers are not listed in your an_init.tcp file? >>>> >>>> Ted >>>> >>>> On Mar 14, 2013, at 8:48 AM, "Johnson, David" < >>> David.Johnson@xxxxxxxxxxxxxxxxxx> wrote: >>>> >>>>> Ted, >>>>> >>>>> That sounds like a potential problem, but we checked, and the >>>>> disable >>> broadcast box was checked in APIAdmin on ALL of the AWs listed. We >>> only have AIM*OPC Server on SRVONE, there are no other OPC servers or >>> clients on the DCS network. So I still don't know why the AIM*OPC >>> Server is attempting to talk to the other AWs. And although I only >>> listed 2 sample netstat lines with the CLOSE_WAIT there are many, >>> possibly hundreds, to each AW after a few days. >>>>> >>>>> Any other ideas? >>>>> Thanks, >>>>> David >>>>> >>>>> >>>>> >>>>> -----Original Message----- >>>>> From: foxboro-bounce@xxxxxxxxxxxxx >>>>> [mailto:foxboro-bounce@xxxxxxxxxxxxx] >>> On Behalf Of Ted Jirik >>>>> Sent: Thursday, March 14, 2013 9:32 AM >>>>> To: foxboro@xxxxxxxxxxxxx >>>>> Subject: Re: [foxboro] AIM*OPC Server CLOSE_WAIT errors >>>>> >>>>> David, >>>>> >>>>> We had the same problem. As I recall we had to disable broadcast >>> requests under edit server connection in apiadmin. We did this on all >>> stations and the problem went away. >>>>> >>>>> Ted >>>>> >>>>> On Mar 14, 2013, at 6:25 AM, Johnson, David wrote: >>>>> >>>>>> Hello All, >>>>>> We have an AIM*OPC server installed on an AW running Win 2003 Server. >>> The OPC server is working (will return data, no errors). We have an >>> OSI PI data collector running. It will connect to and get data from >>> I/A via the OPC link. This will work for several days, but then the >>> AW becomes so unresponsive, it must be rebooted. After a reboot the >>> problem goes away for a day or two, and then returns. >>> >>> >>> ______________________________________________________________________ >>> _ 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 >> >> >> -- >> >> Michael Toecker >> Head Dragon Slayer >> >> >> >> >> _______________________________________________________________________ >> 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: >> >> The information contained in this message is private and confidential. This >> information is intended only for the individual or entity named above. If >> the reader of this message is not the intended recipient, you are hereby >> notified that any use, review, dissemination, distribution, copying or >> action taken based on this message or its attachments, if any, is strictly >> prohibited. If you are not the intended recipient, please contact the >> sender by reply email and delete or destroy all copies of this message and >> any attachments. Thank you. >> >> >> _______________________________________________________________________ >> 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 > > _______________________________________________________________________ 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