11 Replies Latest reply on Apr 27, 2012 5:31 AM by Gurneet Singh Chopra

    Windows Servers Failing to Patch

      Alot of my Windows Servers are failing to patch seeing this error

       

      Error Apr 25, 2012 7:31:46 PM  Shavlik Packager Error: Found this service pack, but cannot find this patch in PD5.xml!

      2 IE8-WindowsServer2003.WindowsXP-KB2675157-x64.exe-MS12-023-en-INTERNET EXPLORER 8 (X64)-GOLD

       

      Error Apr 25, 2012 9:35:04 PM  Shavlik Packager Error: Found this service pack, but cannot find this patch in PD5.xml!

      3 IE7-WindowsServer2003-KB2675157-x86.exe-MS12-023-en-INTERNET EXPLORER 7-GOLD

        • 1. Windows Servers Failing to Patch

          This issue is caused most likely by corrupted Shavlik package. Deleting and re downloading package will help.

           

           

          1.     Delete the HFnecthk6b.cab/xml and PD5.xml/cab file from ‘Fileserver/template’ location

          2.     Open Tools / Patch Analysis Configuration / Shavlik URLs and click on download for HFnecthk6b.cab/xml and PD5.xml/cab

          3.     Rerun the analysis to verify.

           

          Also see https://kb.bmc.com/infocenter/index?page=content&id=KA359506&actp=search&viewlocale=en_US&searchid=1335354168113 if the above does not help. Mostly its the corrupted shavlik package.

          • 2. Windows Servers Failing to Patch

            That has not fixed the Issue, seems to be the latest Windows Patches causing the issue, so removed this months for now.

             

            Got another issue with Patching Failing on it seems to me Windows 2003 R2 Servers

             

            Error Apr 26, 2012 10:32:58 PM Parsing of file 'C:\Program Files\BMC Software\BladeLogic\8.0\RSCD\Transactions\abb24c2e7388344589b820f04857e91d\bldeploy.xml' failed at line 2: no element found

            • 3. Windows Servers Failing to Patch

              For the first issue, check if these patches exist in the xml file or not. If they have been released by MS, the latest shavlik files should have it too.

               

              And for the 2nd issue, is this happening while patch deploy? Can you attached bltargetjobmanager and bldeploy xml for this run?

              • 4. Windows Servers Failing to Patch

                The Second Issue is happening when deploying the Patches. Where will i find those Files?

                • 5. Windows Servers Failing to Patch

                  The entire bldeploy log should tell you what the problem is. Correction to above post, attach the log files and not xml ( major typo).  The no element found can be due to many reasons. An error before that should tell you the exact cause.

                   

                  Also check if https://communities.bmc.com/communities/message/211050#211050

                  • 6. Windows Servers Failing to Patch

                    it should be in the transactions directory of the target server.

                    • 7. Windows Servers Failing to Patch

                      BLDEPLOY

                       

                      04/26/12 22:32:56.958 DEBUG    bldeploy - [36][] Removing asset: 36

                      04/26/12 22:32:56.958 DEBUG    bldeploy - [37][] After initializing shavlik hotfix asset

                      04/26/12 22:32:56.958 DEBUG    bldeploy - [37][] Added new hotfix to the asset preprocessor

                      04/26/12 22:32:56.958 DEBUG    bldeploy - [37][] After initializing shavlik hotfix asset

                      04/26/12 22:32:56.958 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_USERNAME. Parameter value will be defaulted to a blank string

                      04/26/12 22:32:56.958 DEBUG    bldeploy - Could not find a parameter match to TARGET.MS_OFFICE_INSTALL_LOCATION. Parameter value will be defaulted to a blank string

                      04/26/12 22:32:56.958 DEBUG    bldeploy - Could not find a parameter match to HOTFIXNAME. Parameter value will be defaulted to a blank string

                      04/26/12 22:32:56.958 DEBUG    bldeploy - [37][] Removing asset: 37

                      04/26/12 22:32:56.958 INFO     bldeploy - Starting apply

                      04/26/12 22:32:56.974 DEBUG    bldeploy - [][] Starting pre-apply for BLPACKAGE

                      04/26/12 22:32:56.974 DEBUG    bldeploy - Running pre-package apply for type HOTFIX

                      04/26/12 22:32:56.974 DEBUG    bldeploy - chdir to PkgDir: 'C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik'

                      04/26/12 22:32:56.974 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=C:/Program Files/BMC Software/BladeLogic/8.0/RSCD\sbin\BlPatchCheck2.exe, cmd=BlPatchCheck2.exe 0 -s -pt 13 "C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik\hfnetchk6b.cab" "C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik\analysis_results.xml", cmdDir=C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik

                      04/26/12 22:32:57.521 DEBUG    bldeploy - ProcessExecutor::wiatForSingleProcess: exitCode = 1

                      04/26/12 22:32:57.521 DEBUG    bldeploy - chdir to original Dir: 'C:\'

                      04/26/12 22:32:57.521 WARN     bldeploy - BlPatchCheck2.exe failed. Return Code: 1

                      04/26/12 22:32:57.521 WARN     bldeploy - Patch Analysis failed.

                      04/26/12 22:32:57.521 WARN     bldeploy - Unable to extract Ms-Office deployment information (GUIDs). Deployment for MS-Office patches may fail

                      04/26/12 22:32:57.521 DEBUG    bldeploy - Processing 37 patches (Hotfixes)

                      04/26/12 22:32:57.521 DEBUG    bldeploy - chdir to PkgDir: 'C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik'

                      04/26/12 22:32:57.521 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=C:/Program Files/BMC Software/BladeLogic/8.0/RSCD\sbin\BlPatchCheck2.exe, cmd=BlPatchCheck2.exe 1 "C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik\pd5.cab" "C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik\shavlik_apply_config.xml", cmdDir=C:\temp\stage\b89d66e6588338938ac856f356c4293b\\shavlik

                      04/26/12 22:32:57.974 DEBUG    bldeploy - ProcessExecutor::wiatForSingleProcess: exitCode = 1

                      04/26/12 22:32:57.974 DEBUG    bldeploy - chdir to original Dir: 'C:\'

                      04/26/12 22:32:57.974 ERROR    bldeploy - BlPatchCheck2.exe failed. Return Code: 1

                      04/26/12 22:32:57.974 ERROR    bldeploy - Unable to run the Shavlik packager for generating deployment batch files

                      04/26/12 22:32:57.974 DEBUG    bldeploy - [][] Pre-apply for BLPACKAGE failed

                      04/26/12 22:32:57.974 DEBUG    bldeploy - [][] Pre-ApplyDo failed -processing sub-list: id =

                      04/26/12 22:32:57.974 DEBUG    bldeploy - [][] Package failed = BLPACKAGE

                      04/26/12 22:32:57.974 DEBUG    bldeploy - No Package items were processed. Package was already completed or empty.

                      04/26/12 22:32:57.974 INFO     bldeploy - Deployment ignoring copy on boot pending operations according to job configuration.

                      04/26/12 22:32:57.974 DEBUG    bldeploy - [1][WindowsServer2003-SP2-KB942831-x86-ENU.exe-MS08-005-en-INTERNET INFORMATION SERVICES 6.0-SP2] Removing asset: 1

                      • 8. Windows Servers Failing to Patch

                        04/26/12 22:32:32.958 DEBUG    bldeploy - TJM invoked with arguments:

                        04/26/12 22:32:32.958 DEBUG    bldeploy - args 0 = bltargetjobmanager

                        04/26/12 22:32:32.958 DEBUG    bldeploy - args 1 = -start

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 2 = -cmd

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 3 = bldeploy abb24c2e7388344589b820f04857e91d -N=/temp/stage/b89d66e6588338938ac856f356c4293b -P=HKX1GMM01 -Q=params.txt -PKG=Windows%20Security%20Patches-201%20@%202012-04-26%2022-18-54-609+0800-19443.1 -DryRun -Xr -V1 -Xp -js0 -jr1 -jc0

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 4 = -me

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 5 = abb24c2e7388344589b820f04857e91d

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 6 = -mp

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 7 = -sp

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 8 = -ps

                        04/26/12 22:32:32.974 DEBUG    bldeploy - args 9 = -h60

                        04/26/12 22:32:32.974 DEBUG    bldeploy - BlTargetJobManager started

                        04/26/12 22:32:32.974 DEBUG    bldeploy - Commandline: bltargetjobmanager -start -cmd bldeploy abb24c2e7388344589b820f04857e91d -N=/temp/stage/b89d66e6588338938ac856f356c4293b -P=HKX1GMM01 -Q=params.txt -PKG=Windows%20Security%20Patches-201%20@%202012-04-26%2022-18-54-609+0800-19443.1 -DryRun -Xr -V1 -Xp -js0 -jr1 -jc0  -me abb24c2e7388344589b820f04857e91d -mp -sp -ps -h60

                        04/26/12 22:32:32.989 DEBUG    bldeploy - Executing "C:\Program Files\BMC Software\BladeLogic\8.0\RSCD\sbin\bldeploy.exe" abb24c2e7388344589b820f04857e91d -N=/temp/stage/b89d66e6588338938ac856f356c4293b -P=HKX1GMM01 -Q=params.txt -PKG=Windows%20Security%20Patches-201%20@%202012-04-26%2022-18-54-609+0800-19443.1 -DryRun -Xr -V1 -Xp -js0 -jr1 -jc0  -StartNew

                        04/26/12 22:32:32.989 DEBUG    bldeploy - ProcessExecutor::createProcess batchFile=, cmd="C:\Program Files\BMC Software\BladeLogic\8.0\RSCD\sbin\bldeploy.exe" abb24c2e7388344589b820f04857e91d -N=/temp/stage/b89d66e6588338938ac856f356c4293b -P=HKX1GMM01 -Q=params.txt -PKG=Windows%20Security%20Patches-201%20@%202012-04-26%2022-18-54-609+0800-19443.1 -DryRun -Xr -V1 -Xp -js0 -jr1 -jc0  -StartNew, cmdDir=

                        04/26/12 22:32:33.802 DEBUG    bldeploy - Compare to blp_prog=bldeploy

                        04/26/12 22:32:33.802 DEBUG    bldeploy - Command has started

                        04/26/12 22:32:33.802 DEBUG    bldeploy - Received from PID=202644 EVENT=STARTED MSG=Package "Windows Security Patches-201 @ 2012-04-26 22-18-54-609+0800" UUID(abb24c2e7388344589b820f04857e91d) started

                        04/26/12 22:32:34.302 DEBUG    bldeploy - Compare to blp_prog=bldeploy

                        04/26/12 22:32:35.302 DEBUG    bldeploy - Received from PID=202644 EVENT=INFO MSG=Package "Windows Security Patches-201 @ 2012-04-26 22-18-54-609+0800" UUID(abb24c2e7388344589b820f04857e91d) initialized, entering wait queue for processing

                        04/26/12 22:32:35.302 DEBUG    bldeploy - Received from PID=202644 EVENT=INFO MSG=Package "Windows Security Patches-201 @ 2012-04-26 22-18-54-609+0800" UUID(abb24c2e7388344589b820f04857e91d) processing instructions

                        04/26/12 22:32:35.302 DEBUG    bldeploy - TJM return code 0 changed to succeeded. Correct code set in STOP event exitCode value

                        04/26/12 22:32:35.302 DEBUG    bldeploy - Received from PID=202644 EVENT=STOP MSG=Package "Windows Security Patches-201 @ 2012-04-26 22-18-54-609+0800" UUID(abb24c2e7388344589b820f04857e91d) completed. exitCode = 0 (DryRun successful)

                        04/26/12 22:32:35.302 DEBUG    bldeploy - Deleted event file: C:\Program Files\BMC Software\BladeLogic\8.0\RSCD\Transactions\events\abb24c2e7388344589b820f04857e91d.out

                        04/26/12 22:32:35.318 DEBUG    bldeploy - Deleted event file: C:\Program Files\BMC Software\BladeLogic\8.0\RSCD\Transactions\events\abb24c2e7388344589b820f04857e91d.in

                        04/26/12 22:32:35.318 DEBUG    bldeploy - Operation complete return code 0

                        04/26/12 22:32:55.427 DEBUG    bldeploy - TJM invoked with arguments:

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 0 = bltargetjobmanager

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 1 = -start

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 2 = -cmd

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 3 = bldeploy abb24c2e7388344589b820f04857e91d -N=/temp/stage/b89d66e6588338938ac856f356c4293b -P=HKX1GMM01 -Q=params.txt -PKG=Windows%20Security%20Patches-201%20@%202012-04-26%2022-18-54-609+0800-19443.1 -V1 -RegAllCOM -UnregAllCOM -TreatLockedAsErr -Xp -js0 -jr1 -jc0

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 4 = -me

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 5 = abb24c2e7388344589b820f04857e91d

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 6 = -mp

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 7 = -sp

                        04/26/12 22:32:55.427 DEBUG    bldeploy - args 8 = -ps

                        • 9. Windows Servers Failing to Patch

                          This is the error: BlPatchCheck2.exe failed. Return Code: 1

                           

                          See the KB article https://kb.bmc.com/infocenter/index?page=content&id=KA324245&actp=search&viewlocale=en_US&searchid=1335452981063 for its resolution. Quite a known issue this is. Hope this helps.

                          1 of 1 people found this helpful
                          • 10. Windows Servers Failing to Patch

                            Did you download the new set of cab files from Shavlik? I think both the issues maybe related to the original problem you posted. See this KB article as well: https://kb.bmc.com/infocenter/index?page=content&id=KA322916

                            1 of 1 people found this helpful
                            • 11. Windows Servers Failing to Patch
                              Gurneet Singh Chopra

                              Hi David,

                               

                              Both your problems are because of corrupted metadata (hfnet/pd5).

                               

                              To resolve this, you need to delete them from File server and depot permanently and download the new set.

                               

                              Also, before downloading the new one's. Change the shavlik file format from CAB to XML which will help you get rid of "Unable to download/decab" issue. You can change the format from CAB to XML by going to Shavlik URL Configuration.

                               

                              Once done, update the patch catalog and rerun the analysis.

                               

                              Thanks,

                               

                              -Gurneet