7 Replies Latest reply on Apr 3, 2020 7:05 AM by Bill Robinson

    TSSA patching deploy problem

    Raul Calderon de la Barca
      Share This:

      Platform: TSSA 8.9.04.200

       

      Hello,

       

      We have a Windows 2012R2 server in which we have launched an analysis and remediation patching job.

       

      • In the analysis job the server appears with a pending reboot:

       

      Info 03/31/2020 01:20:08 Creating analysis result items for server: GDCVODLDR01PR.bcp.ptc.bt.es

      Info 03/31/2020 01:20:08 Parsing analysis results for server: GDCVODLDR01PR.bcp.ptc.bt.es

      Warning 03/31/2020 01:20:08 Reboot is pending on this machine, analysis results may be in-correct.

      Info 03/31/2020 01:20:08 Copying analysis results xml from server: GDCVODLDR01PR.bcp.ptc.bt.es

      Info 03/31/2020 01:20:07 Analyzer execution complete on server: GDCVODLDR01PR.bcp.ptc.bt.es , exitCode: 0

      Info 03/31/2020 01:19:56 Starting analyzer execution on server: GDCVODLDR01PR.bcp.ptc.bt.es

      Info 03/31/2020 01:19:56 Generating white-list (includes) file on target: GDCVODLDR01PR.bcp.ptc.bt.es

      Info 03/31/2020 01:19:56 Metadata WindowsPatchData.zip copied to the server: GDCVODLDR01PR.bcp.ptc.bt.es

      Info 03/31/2020 01:19:47 Copying metadata WindowsPatchData.zip to the server: GDCVODLDR01PR.bcp.ptc.bt.es

       

      • In the remediation job there is a fail and the deployment finishes with a fail (in the commit phase):

          

                Error 03/31/2020 01:21:48 APPLY failed for server WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es. Exit code = -4001

                Warning 03/31/2020 01:21:48 Deploy failed. Cleaning up staging area.

                 (Time in agent's deploy log:: 03/31/2020 01:21:41)

                Warning 03/31/2020 01:21:48 Deploy failed. Cleaning up staging area.

                 (Time in agent's deploy log:: 03/31/2020 01:21:41)

                Warning 03/31/2020 01:21:48 Copy on reboot files present, reboot not allowed - quitting

                 (Time in agent's deploy log:: 03/31/2020 01:21:41)

       

      Could you help me please?

       

      Thank you very much.

       

      BR

        • 1. Re: TSSA patching deploy problem
          Rohit Sharma

          Can you please attach the complete bldeploy log from the target server?

          • 2. Re: TSSA patching deploy problem
            Sanjay Singh Dhami

            Raul Calderon de la Barca

             

            For reliable results, reboot the impacted server/s and rerun the Windows Patch Analysis Job before proceeding with patch remediation.

            To confirm the Server is in the Reboot Required state, check the following registry keys on the Target Server:
            - Go to "run" and "regedit"
            - Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\WindowsUpdate\Auto Update\RebootRequired
            - Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations


            If the value data is present in the Value name "PendingFileRenameOperations", it means that the server requires a reboot.

             

            GO through this article- TSSA/BSA : Warning from Windows Patch Analysis Job - Reboot is pending on this machine, analysis results may be incorrect

            1 of 1 people found this helpful
            • 3. Re: TSSA patching deploy problem
              Raul Calderon de la Barca

              Hello Rohit,

               

              I attach the bldeploy presents in /Transactions/log path in the server.

               

              I add that the same job was executed fr other servers and only for the server pending on reboot failed. For the rest the execution finished fine.

               

              Thank you very much.

               

              Best regards.


              Raúl

              • 4. Re: TSSA patching deploy problem
                Raul Calderon de la Barca

                Hi Rohit,

                 

                In this job (remediation patching job), all the servers finished correctly except those which had a pending reboot in the analysis phase.

                I put screenshots with the remediation part configuration:

                 

                I put below the deploy log (I don't know if yesterday I attached the file correctly):

                 

                03/31/20 01:20:42.898 INFO     bldeploy - Bldeploy started for package: 4a3e5748e8d73f5abb5fb3458b3c8a30

                03/31/20 01:20:42.898 DEBUG    bldeploy - Bldeploy Arguments:

                03/31/20 01:20:42.898 DEBUG    bldeploy - C:\Program Files\BMC Software\BladeLogic\RSCD\sbin\bldeploy.exe

                03/31/20 01:20:42.898 DEBUG    bldeploy - 4a3e5748e8d73f5abb5fb3458b3c8a30

                03/31/20 01:20:42.898 DEBUG    bldeploy - -N=/temp/stage/bf78151227db3c70ac955d4af4e9206f

                03/31/20 01:20:42.898 DEBUG    bldeploy - -P=WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es

                03/31/20 01:20:42.898 DEBUG    bldeploy - -Q=params.txt

                03/31/20 01:20:42.898 DEBUG    bldeploy - -PKG=WIZINK_PRIMER_SABADO_NOCHE_BBDD_CRITICOS-2277655-4151098-1%20@%202020-03-31%2001-20-32-419+0200-2933656.1

                03/31/20 01:20:42.898 DEBUG    bldeploy - -DryRun

                03/31/20 01:20:42.898 DEBUG    bldeploy - -Xr

                03/31/20 01:20:42.898 DEBUG    bldeploy - -S

                03/31/20 01:20:42.898 DEBUG    bldeploy - -V1

                03/31/20 01:20:42.898 DEBUG    bldeploy - -OverwriteReadOnlyFiles

                03/31/20 01:20:42.898 DEBUG    bldeploy - -Xp

                03/31/20 01:20:42.898 DEBUG    bldeploy - -js1

                03/31/20 01:20:42.898 DEBUG    bldeploy - -jr1

                03/31/20 01:20:42.898 DEBUG    bldeploy - -jc0

                03/31/20 01:20:42.898 DEBUG    bldeploy - -StartNew

                03/31/20 01:20:42.898 DEBUG    bldeploy - C:\Program Files\BMC Software\BladeLogic\RSCD\sbin\bldeploy.exe  - 8.9.04.200

                03/31/20 01:20:42.898 INFO     bldeploy - Reboot is not allowed

                03/31/20 01:20:42.898 DEBUG    bldeploy - Cleanup staging area on failure

                03/31/20 01:20:43.913 DEBUG    bldeploy - Utilizing configuration file: C:\temp\stage\bf78151227db3c70ac955d4af4e9206f\4a3e5748e8d73f5abb5fb3458b3c8a30.cfg

                03/31/20 01:20:43.913 DEBUG    bldeploy - Fresh start of deployment, deleting any pre-existing configuration file

                03/31/20 01:20:50.788 DEBUG    bldeploy - Could not open file "C:\Program Files\BMC Software\BladeLogic\RSCD\\params.txt" for reading

                03/31/20 01:20:50.788 DEBUG    bldeploy -

                DEPLOYNAME = 4a3e5748e8d73f5abb5fb3458b3c8a30:

                DEPLOYPATH = C:\temp\stage\bf78151227db3c70ac955d4af4e9206f:

                FQHOST = WZGDCVODLDR01PR:

                HOST = WZGDCVODLDR01PR:

                HOSTIP = 10.61.105.38:

                NAMESPACE = WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es:

                ROLLBACKPATH = C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\4a3e5748e8d73f5abb5fb3458b3c8a30:

                RSCDIR = C:\Program Files\BMC Software\BladeLogic\RSCD\:

                WINDIR = C:\Windows:

                XMLFILEPATH = C:\temp\stage\bf78151227db3c70ac955d4af4e9206f\bldeploy.xml:

                03/31/20 01:20:50.788 DEBUG    bldeploy - Full command line C:\Program Files\BMC Software\BladeLogic\RSCD\sbin\bldeploy.exe 4a3e5748e8d73f5abb5fb3458b3c8a30 -N=/temp/stage/bf78151227db3c70ac955d4af4e9206f -P=WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es -Q=params.txt -PKG=WIZINK_PRIMER_SABADO_NOCHE_BBDD_CRITICOS-2277655-4151098-1%20@%202020-03-31%2001-20-32-419+0200-2933656.1 -DryRun -Xr -S -V1 -OverwriteReadOnlyFiles -Xp -js1 -jr1 -jc0

                03/31/20 01:20:50.788 DEBUG    bldeploy - Resetting username size to 4096

                03/31/20 01:20:50.788 DEBUG    bldeploy - GetUserNameExA failed for NameUserPrincipal re-attempting GetUserNameA: (1332 No mapping between account names and security IDs was done.

                 

                 

                )

                03/31/20 01:20:50.788 DEBUG    bldeploy - Running as User: BladeLogicRSCD

                03/31/20 01:20:50.788 DEBUG    bldeploy -  Privileges:

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeIncreaseQuotaPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeSecurityPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeTakeOwnershipPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeLoadDriverPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeSystemProfilePrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeSystemtimePrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeProfileSingleProcessPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeIncreaseBasePriorityPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeCreatePagefilePrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeBackupPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeRestorePrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeShutdownPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeSystemEnvironmentPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeChangeNotifyPrivilege - Enabled by default

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeRemoteShutdownPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeUndockPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeEnableDelegationPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeManageVolumePrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeImpersonatePrivilege - Enabled by default

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeCreateGlobalPrivilege - Enabled by default

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeIncreaseWorkingSetPrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeTimeZonePrivilege - Disabled

                03/31/20 01:20:50.788 DEBUG    bldeploy -   SeCreateSymbolicLinkPrivilege - Disabled

                03/31/20 01:20:50.788 INFO     bldeploy - Maintenance / Exclusion Window Timeout not configured

                03/31/20 01:20:50.788 DEBUG    bldeploy - Validating existence of wait lock C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\locks\reboot.lck

                03/31/20 01:20:50.788 DEBUG    bldeploy - Deployment running in single-job mode

                03/31/20 01:20:50.788 DEBUG    bldeploy - Acquired appropriate lock: C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\locks\writer.lck

                03/31/20 01:20:50.804 WARN     bldeploy - Copy on reboot files present - ignoring

                03/31/20 01:20:50.804 DEBUG    bldeploy - Creating directory C:\Program Files\BMC Software\BladeLogic\RSCD\Transactions\4a3e5748e8d73f5abb5fb3458b3c8a30

                03/31/20 01:20:50.804 INFO     bldeploy - Bldeploy "WIZINK_PRIMER_SABADO_NOCHE_BBDD_CRITICOS-2277655-4151098-1 @ 2020-03-31 01-20-32-419+0200" UUID(4a3e5748e8d73f5abb5fb3458b3c8a30) started using file C:\temp\stage\bf78151227db3c70ac955d4af4e9206f\bldeploy.xml with rollback directory C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\4a3e5748e8d73f5abb5fb3458b3c8a30

                03/31/20 01:20:50.804 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_USERNAME. Parameter value will be defaulted to a blank string

                03/31/20 01:20:50.804 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_PWD. Parameter value will be defaulted to a blank string

                03/31/20 01:20:50.804 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_LOCATION. Parameter value will be defaulted to a blank string

                03/31/20 01:20:50.804 DEBUG    bldeploy - Creating REBOOT return code overide list: R:3010

                03/31/20 01:20:50.804 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_USERNAME. Parameter value will be defaulted to a blank string

                03/31/20 01:20:50.804 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_PWD. Parameter value will be defaulted to a blank string

                03/31/20 01:20:50.804 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_LOCATION. Parameter value will be defaulted to a blank string

                03/31/20 01:20:50.804 DEBUG    bldeploy - Creating REBOOT return code overide list: R:3010

                03/31/20 01:20:50.804 INFO     bldeploy - Starting dryRun

                03/31/20 01:20:50.804 INFO     bldeploy - Package contains reboot instructions, and does not contain single-user mode instructions

                03/31/20 01:20:50.804 DEBUG    bldeploy - [][] Dryrun id =

                03/31/20 01:20:50.804 DEBUG    bldeploy - [1][remediate-2049101-PRIMER SABADO DE MES SLOT3 BBDD CRITICOS22018-08-09 18-53-07-817+02002020-03-31 01-20-27-329+0200] Dryrun id = 1

                03/31/20 01:20:50.804 DEBUG    bldeploy - [2][Windows8.1-2012-R2-KB4541505-x64.msu-MS20-03-SO81-4541505-en-WINDOWS SERVER 2012 R2 STANDARD (X64)-CU1] Dryrun id = 2

                03/31/20 01:20:50.804 DEBUG    bldeploy - [3][windows8.1-2012-R2-kb4540725-x64.msu-MS20-03-SSU-4540725-en-WINDOWS SERVER 2012 R2 STANDARD (X64)-CU1] Dryrun id = 3

                03/31/20 01:20:50.804 INFO     bldeploy - Dryrun succeeded

                03/31/20 01:20:50.804 DEBUG    bldeploy - Dryrun does not delete staging nor rollback directories

                03/31/20 01:20:50.804 DEBUG    bldeploy - DeletePkg = 0 DeleteUndo = 0

                03/31/20 01:20:50.804 INFO     bldeploy - Bldeploy done - nRet = 3 (DryRun successful) exitCode = 0 (Deployment succeeded)

                 

                 

                03/31/20 01:21:33.319 INFO     bldeploy - Bldeploy started for package: 4a3e5748e8d73f5abb5fb3458b3c8a30

                03/31/20 01:21:33.319 DEBUG    bldeploy - Bldeploy Arguments:

                03/31/20 01:21:33.319 DEBUG    bldeploy - C:\Program Files\BMC Software\BladeLogic\RSCD\sbin\bldeploy.exe

                03/31/20 01:21:33.319 DEBUG    bldeploy - 4a3e5748e8d73f5abb5fb3458b3c8a30

                03/31/20 01:21:33.319 DEBUG    bldeploy - -N=/temp/stage/bf78151227db3c70ac955d4af4e9206f

                03/31/20 01:21:33.319 DEBUG    bldeploy - -P=WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es

                03/31/20 01:21:33.335 DEBUG    bldeploy - -Q=params.txt

                03/31/20 01:21:33.335 DEBUG    bldeploy - -PKG=WIZINK_PRIMER_SABADO_NOCHE_BBDD_CRITICOS-2277655-4151098-1%20@%202020-03-31%2001-20-32-419+0200-2933656.1

                03/31/20 01:21:33.335 DEBUG    bldeploy - -Xc

                03/31/20 01:21:33.335 DEBUG    bldeploy - -S

                03/31/20 01:21:33.335 DEBUG    bldeploy - -V1

                03/31/20 01:21:33.335 DEBUG    bldeploy - -OverwriteReadOnlyFiles

                03/31/20 01:21:33.335 DEBUG    bldeploy - -RegAllCOM

                03/31/20 01:21:33.335 DEBUG    bldeploy - -UnregAllCOM

                03/31/20 01:21:33.335 DEBUG    bldeploy - -Xc

                03/31/20 01:21:33.335 DEBUG    bldeploy - -Xp

                03/31/20 01:21:33.335 DEBUG    bldeploy - -js1

                03/31/20 01:21:33.335 DEBUG    bldeploy - -jr1

                03/31/20 01:21:33.335 DEBUG    bldeploy - -jc0

                03/31/20 01:21:33.335 DEBUG    bldeploy - -StartNew

                03/31/20 01:21:33.335 DEBUG    bldeploy - C:\Program Files\BMC Software\BladeLogic\RSCD\sbin\bldeploy.exe  - 8.9.04.200

                03/31/20 01:21:33.335 INFO     bldeploy - Reboot is not allowed

                03/31/20 01:21:33.335 DEBUG    bldeploy - Cleanup staging area on failure

                03/31/20 01:21:34.351 DEBUG    bldeploy - Utilizing configuration file: C:\temp\stage\bf78151227db3c70ac955d4af4e9206f\4a3e5748e8d73f5abb5fb3458b3c8a30.cfg

                03/31/20 01:21:34.351 DEBUG    bldeploy - Fresh start of deployment, deleting any pre-existing configuration file

                03/31/20 01:21:41.241 DEBUG    bldeploy - Could not open file "C:\Program Files\BMC Software\BladeLogic\RSCD\\params.txt" for reading

                03/31/20 01:21:41.241 DEBUG    bldeploy -

                DEPLOYNAME = 4a3e5748e8d73f5abb5fb3458b3c8a30:

                DEPLOYPATH = C:\temp\stage\bf78151227db3c70ac955d4af4e9206f:

                FQHOST = WZGDCVODLDR01PR:

                HOST = WZGDCVODLDR01PR:

                HOSTIP = 10.61.105.38:

                NAMESPACE = WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es:

                ROLLBACKPATH = C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\4a3e5748e8d73f5abb5fb3458b3c8a30:

                RSCDIR = C:\Program Files\BMC Software\BladeLogic\RSCD\:

                WINDIR = C:\Windows:

                XMLFILEPATH = C:\temp\stage\bf78151227db3c70ac955d4af4e9206f\bldeploy.xml:

                03/31/20 01:21:41.241 DEBUG    bldeploy - Full command line C:\Program Files\BMC Software\BladeLogic\RSCD\sbin\bldeploy.exe 4a3e5748e8d73f5abb5fb3458b3c8a30 -N=/temp/stage/bf78151227db3c70ac955d4af4e9206f -P=WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es -Q=params.txt -PKG=WIZINK_PRIMER_SABADO_NOCHE_BBDD_CRITICOS-2277655-4151098-1%20@%202020-03-31%2001-20-32-419+0200-2933656.1 -Xc -S -V1 -OverwriteReadOnlyFiles -RegAllCOM -UnregAllCOM -Xc -Xp -js1 -jr1 -jc0

                03/31/20 01:21:41.241 DEBUG    bldeploy - Resetting username size to 4096

                03/31/20 01:21:41.241 DEBUG    bldeploy - GetUserNameExA failed for NameUserPrincipal re-attempting GetUserNameA: (1332 No mapping between account names and security IDs was done.

                 

                 

                )

                03/31/20 01:21:41.241 DEBUG    bldeploy - Running as User: BladeLogicRSCD

                03/31/20 01:21:41.241 DEBUG    bldeploy -  Privileges:

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeIncreaseQuotaPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeSecurityPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeTakeOwnershipPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeLoadDriverPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeSystemProfilePrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeSystemtimePrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeProfileSingleProcessPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeIncreaseBasePriorityPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeCreatePagefilePrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeBackupPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeRestorePrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeShutdownPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeSystemEnvironmentPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeChangeNotifyPrivilege - Enabled by default

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeRemoteShutdownPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeUndockPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeEnableDelegationPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeManageVolumePrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeImpersonatePrivilege - Enabled by default

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeCreateGlobalPrivilege - Enabled by default

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeIncreaseWorkingSetPrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeTimeZonePrivilege - Disabled

                03/31/20 01:21:41.241 DEBUG    bldeploy -   SeCreateSymbolicLinkPrivilege - Disabled

                03/31/20 01:21:41.241 INFO     bldeploy - Maintenance / Exclusion Window Timeout not configured

                03/31/20 01:21:41.241 DEBUG    bldeploy - Validating existence of wait lock C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\locks\reboot.lck

                03/31/20 01:21:41.241 DEBUG    bldeploy - Deployment running in single-job mode

                03/31/20 01:21:41.241 DEBUG    bldeploy - Acquired appropriate lock: C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\locks\writer.lck

                03/31/20 01:21:41.257 WARN     bldeploy - Copy on reboot files present, reboot not allowed - quitting

                03/31/20 01:21:41.257 WARN     bldeploy - Deploy failed. Cleaning up staging area.

                03/31/20 01:21:41.257 WARN     bldeploy - Deploy failed. Cleaning up staging area.

                03/31/20 01:21:41.257 DEBUG    bldeploy - DeletePkg = 1 DeleteUndo = 1

                03/31/20 01:21:41.257 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/1.xml) = 0

                03/31/20 01:21:41.257 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2.xml) = 0

                03/31/20 01:21:41.257 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2928460.1/Windows8.1-KB4541505-x64.msu) = 0

                03/31/20 01:21:41.257 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2928460.1) = 0

                03/31/20 01:21:41.257 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2928544.1/windows8.1-kb4540725-x64.msu) = 0

                03/31/20 01:21:41.257 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2928544.1) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2933655.1/scripts/WindowsPatchData.zip) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2933655.1/scripts/WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2933655.1/scripts/WIZINK-WZGDCVSQSG002PR.bcp.ptc.bt.es) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2933655.1/scripts) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/2933655.1) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/3.xml) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/4a3e5748e8d73f5abb5fb3458b3c8a30.cfg) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/bldeploy.xml) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/params.txt) = 0

                03/31/20 01:21:41.273 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/shavlik/WindowsPatchData.zip) = 0

                03/31/20 01:21:41.288 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/shavlik/WIZINK-WZGDCVODLDR01PR.bcp.ptc.bt.es) = 0

                03/31/20 01:21:41.288 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/shavlik/WIZINK-WZGDCVSQSG002PR.bcp.ptc.bt.es) = 0

                03/31/20 01:21:41.288 DEBUG    bldeploy - DirUtil::remove: pf->remove (C:\temp\stage\bf78151227db3c70ac955d4af4e9206f/shavlik) = 0

                03/31/20 01:21:41.288 DEBUG    bldeploy - Deleted the folder: C:\temp\stage\bf78151227db3c70ac955d4af4e9206f

                03/31/20 01:21:41.288 DEBUG    bldeploy - Deleted the folder: C:\Program Files\BMC Software\BladeLogic\RSCD\\Transactions\4a3e5748e8d73f5abb5fb3458b3c8a30

                03/31/20 01:21:41.288 INFO     bldeploy - Bldeploy done - nRet = 10 (Deployment failed to process) exitCode = -4001 (Deployment failed)

                 

                Thank you.

                 

                BR

                • 5. Re: TSSA patching deploy problem
                  Bill Robinson

                  "In this job (remediation patching job), all the servers finished correctly except those which had a pending reboot in the analysis phase."

                  you need to reboot those servers and re-run analysis before running any patch-generated deploy job.

                  • 6. Re: TSSA patching deploy problem
                    Raul Calderon de la Barca

                    Hi Bill,

                     

                    Thank you for your help. Only one last question?

                     

                    Always when a Windows server has a pending reboot the patch deploy job will fail?

                     

                    BR.

                    • 7. Re: TSSA patching deploy problem
                      Bill Robinson

                      what can happen is this:

                      - you patch a system but don't reboot it.  some patches may need a reboot to complete their installation and to show up as installed on the system. 

                      - before rebooting, you run analysis and patches that are half installed are shown as missing (since they aren't done installing), and that analysis job will bundle up those half-installed patches to deploy to the target

                      - you again patch the system, pushing some patches that are in a half-installed state, and they have errors.

                       

                      there's not really a way to differentiate between 'this patch is kind of installed, but just needs a reboot' and 'the patch is not installed'.  and you should always be rebooting after patching, if a reboot is needed.