In this type of scenario it's possible there's a detection issue. It would be best to contact support directly, and if you can go through the below steps to clear out your current logs and obtain trace logs from a scan of one system with this issue it would help us greatly in figuring out what could be going on:
Steps to clear out and obtain trace logs:
-In Protect go to Tools > Options > Logging and make sure both User Interface and Services are set to “All”. Save. -Close Protect. -Stop the VMware vCenter Protect Console service. -Delete all the logs from: -Vista, 2008, & Win7: C:ProgramDataShavlik TechnologiesLogs -Windows XP & 2003: C:Documents and SettingsAll UsersApplication DataShavlik TechnologiesLogs -Start the VMware vCenter Protect Console service and open Protect. -Reproduce the error/issue. (Run a scan using the built in Security Patch Scan template on one system displaying this issue) -Afterwards please zip and send all the logs.
1 of 1 people found this helpful
From the log you can see where we detect the patch here:2013-01-31T12:11:22.9405654Z 0a64 V PatchTest.cpp:523 Testing 'APSB13-02'.2013-01-31T12:11:22.9405654Z 0a64 V PatchTest.cpp:546 Install key exists - adminaccount, 1/30/2013 8:10:20 AM.2013-01-31T12:11:22.9405654Z 0a64 V PatchTest.cpp:628 Bulletin 'APSB13-02', filecount = 1, regcount = 1.2013-01-31T12:11:22.9405654Z 0a64 V PatchTest.cpp:1219 File '\xxx.xxx.xxx.xxxC$Program Files (x86)AdobeReader 11.0ReaderACRORD32.DLL' error: 0.2013-01-31T12:11:22.9405654Z 0a64 V PatchTest.cpp:1222 File \xxx.xxx.xxx.xxxC$Program Files (x86)AdobeReader 11.0ReaderACRORD32.DLL (188.8.131.529) C 2 184.108.40.206 (AC 5).2013-01-31T12:11:22.9405654Z 0a64 V PatchTest.cpp:654 A file was tested.2013-01-31T12:11:22.9405654Z 0a64 V PatchTest.cpp:658 Did not pass file tests.
From what I can see it's testing the patch correctly, and it is definitely missing if ACRORD32.DLL is at the version we found on the target system (220.127.116.119).
If the patch is failing to install can you try the following?
-Go to C:WindowsPropatchesPatches on the target system. (This is where we copy patch files for deployment)
-Locate the latest Adobe Reader patch. I believe it should be named "AdbeRdrUpd11001.msp".
-Double click the patch file to run it manually.
Do any errors come up during the patch installation?
1 of 1 people found this helpful
If you go into Control Panel > Programs & Features (or Add/Remove Programs for older OS's) what version do you see listed for Adobe Reader? Also, check under "View Installed Updates" from the left menu here to see if this shows the same version number for Adobe Reader.
Can you manually check the file that we're seeing at an outdated version as well:
\xxx.xxx.xxx.xxxC$Program Files (x86)AdobeReader 11.0ReaderACRORD32.DLL
I just want to verify the version numbers listed before moving further.
Here is the info…. Thanks much
Programs & Features (or Add/Remove Programs for older OS's) what version do you see listed for Adobe Reader? 11.0.01
xxx.xxx.xxx.xxxC$Program> Files (x86)AdobeReader 11.0ReaderACRORD32.DL = 18.104.22.1689
We found the problem. For some reason the latest Adobe did not update the .dll file as it was supposed to do. We re-released the update and it appears to be scanning properly now that the expected .dll file is there.
Thanks much for your help