Client Management Suite

 View Only
  • 1.  Packages not downloading to Package server. Errors in log.

    Posted Mar 09, 2011 12:27 AM
      |   view attached

     

    The Package Server is not able to download any packages from the Notification Server. We are recieving the below error in the log files related to the package service.

    There is no communication problem as the client with the package server has already recieved the other plug-ins from the NS. This is the error that we have found.

     

    <event date='Mar 08 17:18:51' severity='1' hostName='DX04005SRACOCAV' source='Package Server Agent' module='AeXNSCPackageServer.dll' process='AeXNSAgent.exe' pid='2124' thread='3464' tickCount='161661734' >

      <![CDATA[CAeXNSCPkgSvr::Start failed. Failed to create CLSID_MSAdminBase. Server execution failed.]]>

    </event>

    <event date='Mar 08 17:18:51' severity='1' hostName='DX04005SRACOCAV' source='Agent' module='AeXNSAgent.exe' process='AeXNSAgent.exe' pid='2124' thread='3464' tickCount='161661765' >

      <![CDATA[Failed to start object Altiris.AeXNSCPkgSvr: Server execution failed (-2146959355)]]>

     

    I am attaching the whole log file for your review. In our environment we have migrated the clients from NS 6 to NS 7 by upgrading the base agents.

    Attachment(s)

    txt
    agent.log_.txt   99 KB 1 version


  • 2.  RE: Packages not downloading to Package server. Errors in log.

    Broadcom Employee
    Posted Mar 09, 2011 04:36 AM

    But first I would try to re-run the Package Server Agent installation, this can even things out sometimes.

    If it doesn't work you'll have to check permissions using the "Administrative Tools > DCOM" applet.



  • 3.  RE: Packages not downloading to Package server. Errors in log.

    Posted Mar 09, 2011 08:28 AM

    I'm a little confused.  I'm already helping you in a thread you started earlier this week, with the same log and same issue.

    As I recommended there, you need to be sure you're running the current version, SMP 7.0 SP5, because several issues existed in earlier releases that match exactly the errors you're receiving in your logs.

    I also asked if you were running behind a proxy.

    I also asked if agents are properly running tasks and policies, or whether it's just the package piece is broken.