So you have Windows 7 desktops and your appserver is what version of bladelogic ?
Can you try and manually run the blpatchchk2 on the system? there should be some KAs about how to do that.
I believe its this: 8.3.00.115
I'll see what I can come up with for the blpatchchk2 command
sadly I don't think I have access to that utility. I do have some access to "Server Automation Console", at least enough to patch the servers under my collections.
blpatchcheck2 (sorry, wrong spelling before) is a binary that's used to do the analysis, it's something you'll run from the command line.
Try this :-
- Download http://xml.shavlik.com/data/oem/BMC-Bladelogic/data/8.0/hf7b.xml and copy it to target rscd_dir/sbin folder
- Run: BLPatchCheck2.exe 0 -pt 13 hf7b.xml results.xml (from rscd_dir/sbin)
If you have issue with downloading above link try http://xml.shavlik.com/data/oem/BMC-Bladelogic/data/8.0/hf7b.cab
Go inside of the cab file, there you will find hf7b.xml , right click on it and say extract.
In another thread I was fighting with my NSH shell. LOL Hopefully I can get that worked out also.
Let me see about getting this BLPatchCheck2 binary working and I will report back.
hope all had a great holiday
Ok so I ended up finding BLPartchCheck2, its a part of the agent install.
I used that against the command that "Chetan Lai Gupta" noted above. Here is the commandline output, the actual results file is over 34,000 lines long. Is there any way I can attach that here? Or how can I show you those results?
---- cut start ----
BlPatchCheck2 0 [-s] [-p] [-qf <QNumberFile>]
[-xqf <ExcludeQNumberFile>] [-pt <patchtypes>]
[-h <history_level>] [-ds] [-o <output_format>]
<hfNetChkFile> <Results File>
BlPatchCheck2 1 <pdFile> <ConfigFile>
C:\Bladelogic\RSC\sbin>BLPatchCheck2 0 -pt 13 c:\tmp\hf7b.xml c:\tmp\results.xml
Lock acquired successfully
Init:<HFNetChkInitialize xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.shavlik.com/SchemaHFNetChk6Initialize" xsi:schemaLocation="http://www.shavlik.com/SchemaHFNetChk6Initialize Initialize.xsd" > <Parameters> <Datasource Password="asdf1234asdf1234asdf1234asdf1234">c:\tmp\h
f7b.xml</Datasource> <Trace Enable="1" Path="c:\tmp\Trace.txt"/> </Parameters> </HFNetChkInitialize>
Scan:<HFNetChkScan xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.shavlik.com/SchemaHFNetChk6Scan" > <Parameters> <ScanID>1</ScanID><outputformat>xml4</outputformat> <outputfilepath>c:\tmp\results.xml</outputfilepath> <history>5</history><patchtypes>13</patchtypes></Paramete
Info: Resolving machines to scan
Info: Scanning 1 machines
Info: Started Scanning Machine Group. Machine Count: 1
Info: ScanID: 1
Info: Started Scanning Machine SERVER
Info: Progress Step: 1
Info: Progress Step: 2
Info: Progress Step: 3
Info: Progress Step: 4
Info: Progress Step: 5
Info: Progress Step: 6
Info: Progress Step: 7
Info: Progress Step: 8
Info: Progress Step: 9
Info: Progress Step: 10
Info: Progress Step: 11
Info: Progress Step: 12
Info: Progress Step: 13
Info: Progress Step: 14
Info: Progress Step: 15
Info: Progress Step: 16
Info: Progress Step: 17
Info: Progress Step: 18
Info: Progress Step: 19
Info: Progress Step: 20
Info: Progress Step: 21
Info: Progress Step: 22
Info: Progress Step: 23
Info: Progress Step: 24
Info: Progress Step: 25
Info: Progress Step: 26
Info: Progress Step: 27
Info: Completed Scanning Machine SERVER success
---- cut stop ----
Last thing I found was this code resolves to an access violation. -1073741819
but what and how?
Check the Windows Event logs (Application and System) for any information when the error occurs
When you ran that BLPatchCheck2 command, was it when the Patch Analysis Job was reporting the error, or after a clean install?
After installing the bladelogic x64 bit agent, it will allow me to scan and patch. But if I try the next morning it will fail
So, what happens overnight?
I think you should get a support issue created, so this can be looked at in more detail. If you go that route, please come back and post the findings for the benefit of the community.
I know this post is 3 years old but did you ever get a resolution to this? I just got the same error on a few of my agents version 18.104.22.1680