4 Replies Latest reply on Dec 8, 2019 10:41 PM by Anuj Bathvi

    Failed to Move Payload to Temporary Directory

    Anuj Bathvi
      Share This:

      Hi Experts,

       

      We are doing offline patching for SQL Server 2012, 2014 and 2016. We have successfully downloaded the patches and moved to repository. Catalog was created and updated successfully as well.

       

      We have analyze the server successfully but when we are doing remediation, we are getting below error. We are following the standard procedure for remediation.

       

      11/25/19 16:10:53.333 DEBUG    bldeploy - Running pre-package apply for type HOTFIX

      11/25/19 16:10:53.333 INFO     bldeploy - Command line to package is : "C:/Program Files/BMC Software/BladeLogic/RSCD/\sbin\BlPatchCheck2.exe" 1  -i "INS_CONS"  50249c88-156b-363a-91bb-636d0000e4f4 58612 0002f1e6-0000-0000-0000-000000000000 1033 "C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\payload\SQLServer2016-KB4505220-x64.exe" "C:\temp\stage\50249c88156b363a91bb636ddabfc004\\shavlik\WindowsPatchData.zip" "C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\3.zip"

      11/25/19 16:10:53.333 DEBUG    bldeploy - chdir to PkgDir: 'C:\temp\stage\50249c88156b363a91bb636ddabfc004\\shavlik'

      11/25/19 16:10:53.333 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=C:/Program Files/BMC Software/BladeLogic/RSCD/\sbin\BlPatchCheck2.exe, cmd="C:/Program Files/BMC Software/BladeLogic/RSCD/\sbin\BlPatchCheck2.exe" 1  -i "INS_CONS"  50249c88-156b-363a-91bb-636d0000e4f4 58612 0002f1e6-0000-0000-0000-000000000000 1033 "C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\payload\SQLServer2016-KB4505220-x64.exe" "C:\temp\stage\50249c88156b363a91bb636ddabfc004\\shavlik\WindowsPatchData.zip" "C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\3.zip", cmdDir=C:\temp\stage\50249c88156b363a91bb636ddabfc004\\shavlik

      11/25/19 16:10:56.755 DEBUG    bldeploy - ProcessExecutor::wiatForSingleProcess: exitCode = 0

      11/25/19 16:10:56.755 DEBUG    bldeploy - chdir to original Dir: 'C:\'

      11/25/19 16:10:56.817 ERROR    bldeploy - Failed to move payload C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\SQLServer2016-KB4505220-x64.exe to temporary payload directory C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\payload\SQLServer2016-KB4505220-x64.exe. Error Code: 2

      11/25/19 16:10:56.817 DEBUG    bldeploy - [3][SQLServer2016-KB4505220-x64.exe-MS19-07-SQL-4505220-en-SQL SERVER 2016 X64-SP2] Pre-ApplyDo failed -processing sub-list: id = 3

      11/25/19 16:10:56.817 DEBUG    bldeploy - [3][SQLServer2016-KB4505220-x64.exe-MS19-07-SQL-4505220-en-SQL SERVER 2016 X64-SP2] Apply failed -processing sub-list: id = 3

      11/25/19 16:10:56.817 DEBUG    bldeploy - [][] Package failed = BLPACKAGE

      11/25/19 16:10:56.817 DEBUG    bldeploy - Package items were processed

      11/25/19 16:10:56.817 INFO     bldeploy - Deployment ignoring copy on boot pending operations according to job configuration.

      11/25/19 16:10:56.817 DEBUG    bldeploy - [3][SQLServer2016-KB4505220-x64.exe-MS19-07-SQL-4505220-en-SQL SERVER 2016 X64-SP2] Removing asset: 3

      11/25/19 16:10:56.817 DEBUG    bldeploy - [3][SQLServer2016-KB4505220-x64.exe-MS19-07-SQL-4505220-en-SQL SERVER 2016 X64-SP2] Asset count in the preprocessor is 0. Cleaning up the asset preprocessor object

      11/25/19 16:10:56.973 DEBUG    bldeploy - Creating SUCCESS return code overide list: S:2359303

        • 1. Re: Failed to Move Payload to Temporary Directory
          Bill Robinson

          does this exist on the target:

          C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\SQLServer2016-KB4505220-x64.exe

          ?

          does this exist:

          C:\temp\stage\50249c88156b363a91bb636ddabfc004\\58612.1\payload\

          ?

           

          you can re-run the job w/ the 'preserve staging area on failure' to see if everything gets copied over and created when it fails.

          • 2. Re: Failed to Move Payload to Temporary Directory
            Anuj Bathvi

            Thanks for the reply Bill.

             

            The files were not present on the stage on the target but as u suggested i have made changes and execute the job again, Now i can see the files under stage but below file was missing and payload failed to move the same file. Please refer the below error.

             

            SQLServer2016SP2-KB4052908-x64_English.exe

             

            11/26/19 10:19:28.072 ERROR    bldeploy - Failed to move payload C:\temp\stage\ad97e181c9b53c55907a57b4f113422c\\58001.1\SQLServer2016SP2-KB4052908-x64_English.exe to temporary payload directory C:\temp\stage\ad97e181c9b53c55907a57b4f113422c\\58001.1\payload\SQLServer2016SP2-KB4052908-x64_English.exe. Error Code: 2

            • 3. Re: Failed to Move Payload to Temporary Directory
              Bill Robinson

              if the file wasn't in the staging directory on the target, then it wasn't copied over for some reason.  so i'd start looking in the logs to see why that might not have happened.

              • 4. Re: Failed to Move Payload to Temporary Directory
                Anuj Bathvi

                Hi Bill Robinson

                 

                Just to update you, we have opened the case with BMC and found that it was a defect doing remediation, where more than 1 instance running for SQL Servers. We try to remediation one instance and it got successful, but when we try to remediation the server with more than one instance running on it, its failing with the same error. BMC Support informed us that the defect will be addressed in the future release.

                 

                As a workaround we are doing remediation one instance at a time.