10 Replies Latest reply on Nov 21, 2012 8:05 AM by Lazar NameToUpdate

    Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error

    Yudi Maryanto

      Hi All,

       

      I run Bladelogic Server Automation 8.2.01.273. I created Windows Patch Catalog in Online Mode. I right-clicked it and click "Update Catalog" several times. But they are end up with error "Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error".

       

      I have changed Shalvik URL into xml file instead of cab file. I also deleted cab file from <BSA install dir>\NSH\storage\patch\catalog\catalog_xxx folder. I installed the BSA on Windows Server 2003 Enterprise Edition SP2

       

      Here I attach my screens and two log files from job log and appserver.log

        • 1. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error

          Have you tried registering the DLLs?

           

          CMD> cd C:\[bladelogic_agent]\RSCD

          CMD> regsvr32 stPackager.dll

          CMD> regsvr32 stPatchAssessment.dll

           

          More information can be found at https://kb.bmc.com/infocenter/index?page=content&id=KA312351&actp=search&viewlocale=en_US&searchid=1347279360943

          • 2. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error

            If no KBs help, also check the rscd log on the windows helpter server (may need to set it the agent to debug first). You should see the command that we execute and possibly some more information that can lead us to root cause.

            • 3. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error
              Yudi Maryanto

              I tried to register stPackager.dll and stPatchAssessment.dll but it still failed with the same error message. Here is my rscd.log messages

               

              ----

               

              remote command: regsvr32.exe /s C:/installer/ol-patches/temp_4144_-987481134/stPackager.dll

              bsasvr 4580 SYSTEM (Not_available): (Not_available): Workstation name: Service-0x0-3e7$

              windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

              windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

              windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

              windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

              win_nexec Process exit status 0

              RunProcess: Process return code = 0

              Set to return nexec stdout/stderr as is

              remote command: C:/installer/ol-patches/temp_4144_-987481134/BLPatchCheck2.exe 1 C:/installer/ol-patches/temp_4144_-987481134/pd5.xml C:/installer/ol-patches/temp_4144_-987481134//RequestInput.xml

              bsasvr 4580 SYSTEM (Not_available): (Not_available): Workstation name: Service-0x0-3e7$

              ReadPipe: Read = 35 Buf =  2Error: 80004005 Unspecified error 

              windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

              windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

              windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

              windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

              win_nexec Process exit status 1

              RunProcess: Process return code = 1

              Set to return nexec stdout/stderr as is

              access (C:/installer/ol-patches/temp_4144_-987481134, 0) = 0

              > [Patch-Metadata-Updator] Deleting //bsasvr/C/installer/ol-patches/temp_4144_-987481134

              lstat (C:/installer/ol-patches/temp_4144_-987481134, buf) = 0

              _get_dircontents (C:/installer/ol-patches/temp_4144_-987481134, 9) = 0

              remove (C:/installer/ol-patches/temp_4144_-987481134/BLPatchCheck2.exe) = 0

              remove (C:/installer/ol-patches/temp_4144_-987481134/hf7b.xml) = 0

              remove (C:/installer/ol-patches/temp_4144_-987481134/hfnetExecuteCommandFile.bat) = 0

              remove (C:/installer/ol-patches/temp_4144_-987481134/pd5.xml) = 0

              remove (C:/installer/ol-patches/temp_4144_-987481134/pd5ExecuteCommandFile.bat) = 0

              remove (C:/installer/ol-patches/temp_4144_-987481134/RequestInput.xml) = 0

              remove (C:/installer/ol-patches/temp_4144_-987481134/stPackager.dll) = 0

              rmdir (C:/installer/ol-patches/temp_4144_-987481134) = 0

              • 4. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error

                off-topic:

                note how in the rscd.log you have regsvr32.exe command. In 8.2 as a supportability feature we added automatic re-registration of the dlls, because of having to do it manually in the past a lot...

                 

                on to your issue:

                Here's the command that fails:

                 

                BLPatchCheck2.exe 1 C:/installer/ol-patches/temp_4144_-987481134/pd5.xml C:/installer/ol-patches/temp_4144_-987481134//RequestInput.xml

                 

                This command processes all the patches that were gathered for your filters (filter in your case) and stored in this file RequestInput.xml. I do not see any time stamps from the log, but can you check if the time from running the above command to the line below is some even number (1 minute, 5 minutes..)

                win_nexec Process exit status 1

                 

                what could happen is some timeout (possible on the network side that closes that connection. Here's how you can validate this manually...

                 

                Run the job again and once the BLPatchCheck2.exe 1 ... command starts execution, make a copy of that entire temp folder. Either kill the job or wait for it to fail, and then execute that command from the command line using the copied folder. Tell us if the command runs for longer than the time it takes it to "fail". If yes, then it's something on the network...

                 

                Another test is to run Catalog with different Filter that takes faster to process and see if the Catalog completes. Pick SQL2008 or WinZip - they have very few patches and the command should complete pretty quickly. If this Catalog creates successfully, then again it points to the network.

                • 5. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error
                  Yudi Maryanto

                  Hi Lazar,

                   

                  I rerun the update patch catalog for Windows Server 2003 and Winzip. The time for running the command in the log file is around 2 minutes for Windows Server 2003 and 1 minute and 58 seconds for Winzip (see the log excerpt below)

                   

                  I also tried to manually run the command from the temp_xxx_xxx folder and it failed as well. It run for around 19 seconds

                   

                  C:\installer\ol-patches-tmp\Copy of temp_4642_1621886457>BLPatchCheck2.exe 1 pd5.xml RequestInput.xml

                  Error: 80004005 Unspecified error

                   

                  So, is it related to network problem? I use RSCD agent that resides on the same machine as Bladelogic application server

                   

                   

                   

                   

                  ---

                  Windows Server 2003

                  ---

                  e29f3c301067eafc3f27 0000005041 09/11/12 10:34:28.883 INFO2    rscd -  192.168.129.34 2396 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: remote command: C:/ol-patches/temp_4397_-213424091/BLPatchCheck2.exe 1 C:/ol-patches/temp_4397_-213424091/pd5.xml C:/ol-patches/temp_4397_-213424091//RequestInput.xml

                  62fa2d1d08c17d0f6467 0000005042 09/11/12 10:34:28.883 DEBUG    rscd -  bsawin1 2396 SYSTEM (Not_available): (Not_available): Workstation name: Service-0x0-3e7$

                  d36ddc437916a310855a 0000005043 09/11/12 10:34:47.867 DEBUG    rscd -  192.168.129.34 2396 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: ReadPipe: Read = 35 Buf =  2Error: 80004005 Unspecified error 

                  f139f3e21bff87ebaa33 0000005044 09/11/12 10:34:48.086 DEBUG    rscd -  192.168.129.34 2396 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

                  d124b2d2243f5a406b9d 0000005045 09/11/12 10:34:48.086 DEBUG    rscd -  192.168.129.34 2396 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

                  cef06d9c81fc60dd3a39 0000005046 09/11/12 10:34:48.195 DEBUG    rscd -  192.168.129.34 2396 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

                  a62efee06983a22ffb7d 0000005047 09/11/12 10:34:48.195 DEBUG    rscd -  192.168.129.34 2396 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

                  e473385ef5555884ddcb 0000005048 09/11/12 10:34:48.195 DEBUG    rscd -  192.168.129.34 2396 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: win_nexec Process exit status 1

                   

                   

                    

                   

                  ---

                  WINZIP

                  ---

                  64cd848c5ebec497be3a 0000010094 09/11/12 10:57:19.398 INFO2    rscd -  192.168.129.34 3476 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: remote command: C:/ol-patches/temp_4462_-285362279/BLPatchCheck2.exe 1 C:/ol-patches/temp_4462_-285362279/pd5.xml C:/ol-patches/temp_4462_-285362279//RequestInput.xml

                  93643e9f32f2467eea8d 0000010095 09/11/12 10:57:19.414 DEBUG    rscd -  bsawin1 3476 SYSTEM (Not_available): (Not_available): Workstation name: Service-0x0-3e7$

                  fc8cc6fdb20c2e99e8cf 0000010096 09/11/12 10:57:37.273 DEBUG    rscd -  192.168.129.34 3476 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: ReadPipe: Read = 35 Buf =  2Error: 80004005 Unspecified error 

                  b79220f8b2327d581010 0000010097 09/11/12 10:57:37.492 DEBUG    rscd -  192.168.129.34 3476 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

                  e7c10366c0901d8d5b63 0000010098 09/11/12 10:57:37.492 DEBUG    rscd -  192.168.129.34 3476 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

                  559b69ef7a31ebbafcac 0000010099 09/11/12 10:57:37.601 DEBUG    rscd -  192.168.129.34 3476 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDOUT) failed: 0x00006d

                  71243b64844f18273bed 0000010100 09/11/12 10:57:37.601 DEBUG    rscd -  192.168.129.34 3476 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: windf/read_a_pipe PeekNamedPipe(STDERR) failed: 0x00006d

                  555f511793fdca257b43 0000010101 09/11/12 10:57:37.601 DEBUG    rscd -  192.168.129.34 3476 BladeLogicRSCD@BSAWIN1->Administrator@BSAWIN1:PrivilegeMapped (BLAdmins:BLAdmin): CM: win_nexec Process exit status 1

                  • 6. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error

                    No, the error is not relevant to network in this case, the command actually fails. I'm not sure exactly why the command would fail, but as a next troubelshooting step I'd rerun the command with procmon.exe running in the background (then save the log when you get the error). This log can get intence and not easily reviewed. It would probably be best to file a ticket with BMC Support and provide all this info (and ftp procmon log if possible to ftp.bmc.com/incoming). Also attach to the ticket your pd5.xml and input xml file (just use one WinZip filter to make it simpler).

                    • 7. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error
                      Yudi Maryanto

                      Hi Lazar, I have submitted a ticket to bmc. Waiting response from them.

                       

                      Meanwhile, I spotted from the log file that the path in the BLPatchCheck2.exe execution is rather strange. Is it expected that there is a double slashes (//) before "RequestInput.xml"? (see log messages that I posted above)

                       

                      for procmon.exe, when I run it, it give me a huge number of event (hundred of thousand events). How to filter them? what events are necessary to be monitored for this case?

                      • 8. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error

                        double slashes are fine in the paths.

                         

                        with regards to procmon log, start by applying a filter Process Name equals (your executable in question) BLPatchCheck2.exe. Double-click on any of these entries and review the executed full command, to make sure you have correct instance of blpatchckeck2.exe.

                         

                        Find the place where it fails (based on time stamps, or even you may see exit code 80004005, there is a search option), then review the traces upwards to see what has led to this failure.

                         

                        Look for issues in the Results column (red flags: file not found, access denied, etc). There will be a lot of noise, but it's the reality of procmon.

                         

                        Make sure to share procmon log with support as well. If the issue is resolved, please post solution.

                        • 10. Re: Windows Patch Catalog (Online Mode) Failed - Error executing BLPatchCheck2 (Exit code: 1): Error: 80004005 Unspecified error

                          Just to bring this to resolution, the problem was in fact on the windows helper server executing the command:

                           

                          /BLPatchCheck2.exe 1 xxxxx/pd5.xml xxxxx/RequestInput.xml

                           

                          the problem was traced to multiple win32.dll running on the helper server, which ended up to be environmental issue. While the system is under investigation, another windows server was used as a Windows Helper, on which the command ran successfully following by complete catalog job run.