Can you connect the target server from application server..?? can you paste the logs.. so that we can dig down some more..
I've attached a document to the orginal post. That's I that is in the RSCD.log file.
1 of 1 people found this helpful
Kyle, attached log does not give any details, because it's not in debug. Essentially here's what's happening..
BLPatchCheck2.exe starts to run on the target to perform analysis scan and fails with exit code 128.
If there will be more information about it, then it may be in c:\Trace.txt file (attach it, if you cannot resolve based on what you find there)
You may also try this on the failed target: go to Services / RSCD Agent Service / Properties, on the "Log On" tab check "Allow service to interact with desktop", restart the agent and retest.
I want to highlight one line
SERVERNAME 1228 SYSTEM (Not_available): (Not_available): Main: Wait Timeout
check below things before you go ahead with further troubleshooting:
1. you can ping the target server from the application server
2. you can telnet the target server from the application server
Avisekh, The first line in the log is this:
12/07/12 08:42:24.116 INFO1 rscd - 126.96.36.199 13496 BladeLogicRSCD@SERVERNAME->Manager$@SERVERNAME:PrivilegeMapped (BLAdmins:Sorg, Kyle): CM: > [PatchAnalysis] Deleting //SERVERNAME/C/Program Files/BMC Software/BladeLogic/RSCD//tmp/WindowsCatalog_2440954_111_SERVERNAME
It means that the agent is reachable, and initial metadata was copied to target to start analysis scan, that the analysts scan started and failed, and the temp folder has been deleted. When agent is not in debug, we only log that the temp folder was deleted. This implies that 1 and 2 are ok. Also the message that you see after is for house keeping purposes.
thanks Lazar..then we should go ahead with tracelog..
Error executing Analyzer - ExitCode=128
Running a Patch Analysis job against a target or doing a Live browse of the Hotfixes node in the CM can sometimes yield the error message "Error executing Analyzer: ExitCode = 128"
The problem is caused by a setting on the RSCD Agent Properties that does not allow the analyzer exectuable BLPatchCheck2.exe to function properly.
On the problem target, go to Start -> Run and execute "services.msc" then right-click on the BladeLogic RSCD Agent and select Properties. On the "Log On" tab enable the option for "Allow service to interact with desktop" and then restart the agent.
BMC, why did this work? Our other servers aren't configured this way.
Kyle, I'm not sure if we've ever figured that out. It's very likely that servers are not configured the same (policies, patches, applications, configurations, even acls maybe, etc). There would be some change that is basically countered by the "Allow service to interact with desktop" setting, but this is all I can offer at this point
unnecessary to ping or telnet : the only good test is agentinfo because the firewalls will block icmp or telnet