5 Replies Latest reply on Jun 1, 2009 9:36 AM by cknott

    Failed MSI Distribution

    Rookie

      Landesk 8.8 SP3 push to Windows XP SP2

       

      I have created a Push Delivery that is run from source, never reboot, tried both no feedback and full feedback (no difference), changed both options to downgrade and fail (no change), discovery to UPD, TCP, and both (no change).

       

      Distribution is MSI, took command line out (no change), additional files pointed to path, did auto detect, added all files (no change), no dependent packages, no prereqs, tried both localsystem and current user accounts.

       

      All files are pulled to the client to C:\Program Files\LANDesk\LDClient\sdmcache\(foldername on server) then nothing

       

      get error on server task that says Failed, "The client does not support the features required by the specified package and connot be downgraded"

       

      This is the log file from Scheculed tasks  "Processing package : Bedtrack install"  nothing else

       

      Log from server

       

      5/29/2009 8:41:37 AM : loading distribution task (125) for global scheduler client.
      5/29/2009 8:41:37 AM : performing hash calculations on package : Bedtrack install
      5/29/2009 8:41:39 AM : ERROR: Additional files in packages are not supported for pre 8.5 clients
      5/29/2009 8:41:39 AM : ERROR: Additional files in packages are not supported for pre 8.5 clients
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:39 AM :          125 : Updating allowed machines if needed.
      5/29/2009 8:41:39 AM :          125 : Calling method to perform remote operations.
      5/29/2009 8:41:39 AM :          125 : Before hasherize of D:\Program Files\LANDesk\ManagementSuite\landesk\files\WTH09203-task-125.pmf
      5/29/2009 8:41:39 AM :          125 : After hasherize
      5/29/2009 8:41:39 AM : Core name obtained from database : WTH09203
      5/29/2009 8:41:40 AM :          125 : Troubleshooting guidelines
      The global scheduler has delegated task 125.
        The task was delegated by (source): WTH09203
        This task was delegated to (dest) : WTH09203
        Using GlobalTask_Idn              : 10
      This delegation was done by creating an entry in the GlobalTask table on the destination core (the task id is provided above).
      The Entry in the GlobalTask should have set to state column to 1 to indicate that it is a new task and should be processed.
      The scheduler service should detect and process this delegated task, please check scheduler service log on the destination core to see if it successfully detected the GlobalTask entry.

      5/29/2009 8:41:40 AM :          125 : Waiting for task 125 from WTH09203 to complete on WTH09203.  Checking every 10 seconds, inactivity timeout after 1200 seconds.
      Fri, 29 May 2009 08:41:43 1 machines targeted to task
      Fri, 29 May 2009 08:41:45 Creating a pool of 1 worker threads
      Fri, 29 May 2009 08:41:45 Worker thread started
      Fri, 29 May 2009 08:41:45 Thread pool created
      Fri, 29 May 2009 08:41:45 Processing package
      Fri, 29 May 2009 08:41:45 Item placed in the Machine Node Queue
      Fri, 29 May 2009 08:41:45 Thread is activating, 1 active threads
      Fri, 29 May 2009 08:41:45 Queue Item 94519616: Preparing to process node
      Fri, 29 May 2009 08:41:45 processing machine IS--IS--DLTD04T
      Fri, 29 May 2009 08:41:45 HttpPing xml = <?xml version="1.0" encoding="utf-8" ?><pong><name>IS--IS--DLTD04T</name><osversion><platform>WIN32_NT</platform></osversion><inventoryid>{B68B1090-062F-B644-A1F4-6B1941624248}</inventoryid></pong>
      Fri, 29 May 2009 08:41:47 Remote execute of application 'C:\Program Files\LANDesk\LDClient\fileversion.exe', params '"C:\Program Files\LANDesk\LDClient\sdclient.exe"' on IS--IS--DLTD04T (683a070a)
      Fri, 29 May 2009 08:41:47 sdclient file version characterized as LDMS8
      Fri, 29 May 2009 08:41:47 [IS--IS--DLTD04T] : 1078
      Fri, 29 May 2009 08:41:47 Thread has completed processing, 0 active threads remaining
      Fri, 29 May 2009 08:41:47 The Machine Node Queue is now empty
      Fri, 29 May 2009 08:41:47 Shutting down thread pool
      Fri, 29 May 2009 08:41:47 The Machine Node Queue is now empty
      Fri, 29 May 2009 08:41:47 Thread pool shutdown
      Fri, 29 May 2009 08:41:48 Task complete, status 8
      5/29/2009 8:41:50 AM :          125 : WTH09203 has completed task with status 5 (Delegated task complete.)
      5/29/2009 8:41:50 AM :          125 : Proxy work thread for core WTH09203 is complete.
      5/29/2009 8:41:50 AM :          125 : Thread is complete, synchronizing status information.
      5/29/2009 8:41:50 AM : Warning: No link entries were returned.  No tasks will be synchronized
      5/29/2009 8:41:50 AM : Warning: No link entries were returned.  No tasks will be synchronized
      5/29/2009 8:41:50 AM :          125 : Remote operations complete, synchronizing status information.
      5/29/2009 8:41:50 AM :          125 : Task complete, returning status 7

      notice the line that says error: pre 8.5 client.  by the screenshot below you can see we are 8.8 sp3 and i have done a full scan with the /f and /sync options

       

      there is no logfile on the client or events in eventviewer

       

      Please Help!

       

      Jason

        • 1. Re: Failed MSI Distribution
          egarlepp Employee

          I have seen this, what i found is that for some reason during the initial upgrade of the agent, some older files were left behind although they were from 8.7.  I ran an uninstallwinclient on it let it restart and then installed the v8.8 agent again and the issue disappeared.  Not the ultimate answer but worth a try.

          • 2. Re: Failed MSI Distribution
            cknott SupportEmployee

            In the properties of the delivery method there is a section for Downgrade.

             

            You can choose to downgrade functionality to level of operating system and to the level of the agent.

             

            By default these are set to fail, I would try changing the agent config so that it tries to do the job with whatever agent it detects.

             

            ScreenHunter_01 May. 29 09.25.gif

            • 3. Re: Failed MSI Distribution
              ahe Expert

              Hello Jason,

               

               

              I miss the installation parameters of your application...

               

              And I found this line:

                   sdclient file version characterized as LDMS8

               

              but for 8.8 it must be:

                   sdclient file version characterized as LDMS8_8

               

              So it could be helpful to reinstall the agent as "EGarlepp" mentioned.

               

               

               

              Regards

              Axel

              • 4. Re: Failed MSI Distribution
                Rookie

                to Egarlapp,

                 

                I tried this but still receive same result.

                 

                To Chad,

                 

                I had already tried this, there was no change with this configuration.

                 

                to ahe,

                 

                I had reinstalled it.  What would be causing it to use this configuration.  if you check the screenshot you will see that we are 8.8 sp3.

                • 5. Re: Failed MSI Distribution
                  cknott SupportEmployee

                  It sounds like the CBA8 agent is corrupted.  Try running the Uninstallwinclient.exe with the /forceclean switch.

                   

                  You might need to download this patch and use the uninstallwinclient.exe that is in the image folder of the extracted patch.

                   

                  http://community.landesk.com/downloads/patch/CLN-1050388.zip

                   

                  Try removing the agent with the /forceclean switch, and then reinstalling the agent.

                   

                  Good luck!