Symantec Management Platform (Notification Server)

 View Only
  • 1.  Site Servers dropping out of Site Server list

    Posted Jun 21, 2010 05:06 PM
    Hi

    I've deployed about 40 site servers in a customers environment and am having trouble with 2 specific site servers.  After I have deployed the Task Service and they appear in the list of Site Servers, all appears to work fine for about 12-16 hours.  Clients register through them, there are no errors in the Agent or Task Service log files.  Then, after about 12 hours, they disappear from the list of site servers, and in the taskmanagement.log on the Site Server I get the following entries :

     <entry process="AtrsHost" source="unk" time="22/06/2010 8:49:11 a.m." type="Error" >
      <![CDATA[Error getting work to do.  System.Exception: Error response returned from server: Altiris.NS.Exceptions.AeXSecurityException: A machine (IP: 10.10.10.1: Host: 10.10.10.1) other than a Task Server configured through Site Servers is trying to access the database.
       at Altiris.TaskManagement.ClientTask.BaseWeb.ExecSqlCommand.WriteResponse(XmlTextWriter wr)
       at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr)
       at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)
       at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.PostToNotificationServerAndCheckResponse(String url, NSWebConnectionBuildRequestStreamDelegate requestStreamDelegate, Stream& responseStream, StreamReader& sr, XmlTextReader& r, Int32 nMaxAttempts, Int32 nTimeout)
       at Altiris.ClientTask.Server.Communication.NotificationServerWebConnection.ExecSqlCommand(SqlCommandDefinitionCollection commands, Boolean bQuery, Boolean bTransaction)
       at Altiris.ClientTask.Server.Data.RemoteAltirisSqlConnection.ExecuteReader(SqlCommandDefinition command, Boolean transaction)
       at Altiris.ClientTask.Server.Data.RemoteAltirisSqlConnection.ExecuteReader(SqlCommandDefinition command)
       at Altiris.ClientTask.Server.Execution.ClientTaskExecutionEngine.GetDatabaseWorkToDo()]]>
     </entry>

    I can see the following events in the NS event logs too :

    <event date="Jun 21 20:04:34 +00:00" severity="1" hostName="NSSERVER" source="Altiris.TaskManagement.ClientTask.*" module="w3wp.exe" process="w3wp" pid="8684" thread="51" tickCount="135246171"><![CDATA[BaseXmlHttpCallback Exception: Altiris.NS.Exceptions.AeXSecurityException: A machine (IP: 10.10.10.1: Host: 10.10.10.1) other than a Task Server configured through Site Servers is trying to access the database.
       at Altiris.TaskManagement.ClientTask.BaseWeb.ExecSqlCommand.WriteResponse(XmlTextWriter wr)
       at Altiris.TaskManagement.Common.XmlHttp.BaseXmlXmlHttpCallback.WriteResponseRaw(XmlTextWriter xwr)
       at Altiris.TaskManagement.Common.XmlHttp.BaseXmlHttpCallback.ProcessRequest(HttpContext context)]]></event>

    Both the servers are behind firewalls, and while I'm pretty sure thats the issue, I cant see any traffic being blocked between these 2 site servers and the NS server.  The ports configured in the console for site server communication are all open between the NS server and the Site Servers.

    Any ideas?

    Thanks

    Bevan


  • 2.  RE: Site Servers dropping out of Site Server list

    Posted Jun 21, 2010 05:39 PM


  • 3.  RE: Site Servers dropping out of Site Server list

    Posted Jun 22, 2010 03:37 AM

    Unfortunately no - I saw that just after I posted this and have tried the steps outlined in Resolution 1 - but to no avail.  The site servers just drop out of the Site Server list.  There are no errors in any of the logs which makes it even more annoying.

    I'm trying to get the firewall admins to do some more logging to ensure its not a port being blocked (which I wouldnt be surprised if it is).

    Thanks anyway.



  • 4.  RE: Site Servers dropping out of Site Server list
    Best Answer

    Posted Jul 19, 2010 06:57 PM
    The problem is a routing issue with traffic on port 50124.  Once the routing issue was resolved, the problem was too.

    Thanks anyway.