This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.
BladeLogic Server Automation Suite
TrueSight Server Automation
Windows patch analysis job failed against a particular target server with the following error in the log:
<job run log>
TARGET,Info,"Jul 25, 2019 8:16:09 PM","Analyzer execution complete on server: TARGET , exitCode: -3" TARGET,Error,"Jul 25, 2019 8:16:09 PM",STDERR: Error: No machines were scanned.Error: Analysis failed. ...
APP::[25 Jul 2019 20:16:09,342] [Job-Execution-2] [ERROR] [xxx:BLAdmins:] [PatchAnalysis] __JobRun-71111,2-74529__ STDERR: Error: No machines were scanned.Error: Analysis failed. APP::[25 Jul 2019 20:16:43,154] [Job-Execution-2] [INFO] [xxx:BLAdmins:] [PatchAnalysis] __JobRun-71111,2-74529__ Debug logs for the analysis is copied at location : //APP/C/Program Files/BMC Software/BladeLogic/NSH/tmp/debug/application_server//Windows PAJ/<job run time>/TARGET ...
In case of TSSA 8.9.03+, 'AnalysisTrace.log' can be found on the following location of the target server as below.
<RSCD agent install dir>\RSCD\Transactions\analysis_archive\
... 2019-07-25T10:16:09.2236668Z 2064 I ProductsScanner.cpp:105 *** Detection of Microsoft Visual C++ 2015 Redistributable (x64) (15429) Gold (6452) - Done scanning for patches. 2019-07-25T10:16:09.2236668Z 2064 V ProductsScanner.cpp:81 *** Detection of Remote Desktop Client 6.3 (10753) Gold (5021) - Not scanning for patches. Filtered. 2019-07-25T10:16:09.2236668Z 2064 V ProductsScanner.cpp:81 *** Detection of Microsoft-Windows-DNS-Server DNS Server (15768) Gold (6498) - Not scanning for patches. Filtered. 2019-07-25T10:16:09.2236668Z 2064 V ProductsScanner.cpp:81 *** Detection of MMC Snap-In (3757) Gold (1894) - Not scanning for patches. Filtered. 2019-07-25T10:16:09.2456668Z 2064 E MultiMachineScanner.cpp:841 Error in patchScanEngine::CMultiMachineScanner::TargetMachineScanComplete: class STXml::CXmlException at XmlDomManagement.cpp:72: An invalid character was found in text content.
invalid character in the registry key value
The following error is the key error in this case: An invalid character was found in text content.
This suggests that there is an invalid character found in a registry value.
How to find invalid character?
Check the AnalysisTrace.log on Notepadd++ that is created when executing patch analysis
Trace and analysis results xml can be found on target <RCSD\Transactions\Analysis_Archives>
You will see an strange character as below:
Remove the character following below instructions, make sure that you select all the value
1- launch regedit as administrator
2- navigate to Registry key indicated in the log
3- double-click the "Version" value (note that the value data is all highlighted, you can use ctrl+a to select all)
4- with the value data entirely highlighted, type in correct value (On screenshot example "220.127.116.110") (without the quotes, of course) and click OK
In order to find the exact problem registry key causing the issue, use Ivanti's DPDTrace tool and their tool to detect registry related issues.
Run the DPDTrace tool with the following options:
- Run the DPDTrace as a local Administrator
- Un-select all in 'Versions' on "DPDTrace - GUI"
- Select '9.3.02644' in 'OEM Version'
- Select all patch types that were selected in your patch analysis job
Here is a video :