2 Replies Latest reply on Sep 14, 2014 8:08 PM by bphang

    Comms failed after migrating to EPO 5.1.1 from 5.1.0

    bphang

      Just wondering if anyone come across similar situation.

       

      We are running 1 EPO with 5 Agent handlers spread all over the geo.

      No agent are allowed to talk back to EPO, comms only to AH.

       

      After migrating to EPO 5.1.1 last Thursday night , only today we were alerted by our users that are getting pop up of DAT not updated for a week now.

       

      When we perform agent wake up call, we see the following in AH server log

       

      20140903203119I#341208NAIMSERVWake up agent on DNS name W99999979.au.companydomain.com...
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119I#341208NAIMSERVWake up agent on NetBIOS name W99999979...
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119I#341208NAIMSERVWake up agent on IP Addr 10.62.42.104...
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(205): Error 10054 reading from socket
      20140903203119E#341208NAIMSERVnaSPIPE.cpp(476): Failed to read SPIPE http response, err=-14
      20140903203119E#341208NAIMSERVServer failed to wake up W99999979.au.companydomain.com, detailed error = -14

       

      Upon closer inspection to the affected machines SiteList.xml , looks like it is still using the old SiteList.xml and not updated to the new ones.

       

      <SpipeSite Type="master" Name="ePO_P02CLP1W8969" Local="0" Server="P02CLP1W8969.au.companydomain.com:8071" Enabled="1" Order="5" ServerIP="10.38.52.36:8071" ServerName="P02CLP1W8969:8071" Version="5.1.0" SecurePort="8072">

      <RelativePath>Software</RelativePath><UseAuth>0</UseAuth><UserName/><Password Encrypted="1">f2mwBTzPQdtnY6QNOsVexH9psAU8z0HbZ2OkDTrFXsR/abAFPM9B3Q==</Passwor d></SpipeSite>

       

      Just wondering if there is a way to force update the new SiteList.xml without reinstalling agents?

      And also what might cause this issue?

       

      Thanks