Screencasts - Hilfsvideos
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

MS13-023 Failing with Error Code 17031

Created: 11 Juni 2013 • Aktualisiert: 11 Juli 2013 | 8 Kommentare
das Bild der Nandus
Dieses Problem wurde gelöst. Siehe Lösung.

MS13-023 (vviewer2010-kb2687505-fullfile-x86-glb.exe) is failing on Windows 7 Machines with 17031 Error: General Detection error.

It is installing on some and failing on some machines. Both the installed and failed machines have Microsoft Visio Viewer 2010 version 14.0.4763.1000.

Are anyone facing this issue?

Operating Systems:

Kommentare KommentareZum neuesten Kommentar

das Bild der MyITGuys

The patch has been failing in our environment as well. When we download and manually install Security Update for Microsoft Visio Viewer 2010 (KB2687505) 32-Bit Edition the following error is presented (see attachment).

The expected version of the product was not found on the system.

KB2687505_Manual_Install_Error.png

MyITGuy | Automating your life to make my life easier.

das Bild der Nandus

Can some one help us on this? Any help is much appreciated.

das Bild der MyITGuys

Additional Information

MS13-023: Description of the security update for Visio 2010 Viewer Service Pack 1: March 12, 2013 states:

Prerequisites to apply this security update

To apply this security update, you must have Service Pack 1 for Microsoft Visio 2010 Viewer installed on the computer.

Our systems did not have Service Pack 1 for Microsoft Visio 2010 Viewer installed. After installing Service Pack 1 for Microsoft Visio 2010 Viewer, MS13-023 installed without issue.

On another note, our vulnerability assessment tool showed that MS12-059 was not applied to these systems. MS13-023 supersedes MS12-059.

MyITGuy | Automating your life to make my life easier.

das Bild der Joshua Rasmussens

Please review KM: TECH180083. If the solution process does not resolve this issue; create a support case and attach the data detailed on KM: HOWTO60789 for rules research.

das Bild der Nandus

Thanks for the information! I will check this and get back to you

das Bild der Nandus

SP1 is missing on failed machines. I have installed SBSP-visioviewer2010sp1-kb2460065fullfile on one of the affected machine and vviewer2010-kb2687505-fullfile-x86-glb.exe update is successfully installed.

Resolution is rollout SBSP-visioviewer2010sp1-kb2460065fullfile on failed machines and then install vviewer2010-kb2687505-fullfile-x86-glb.exe update. :)
 

LÖSUNG
das Bild der MyITGuys

To be clear, installing SP1 is a workaround. The problems that needs to be addressed by Symantec are:

  1. Update the applicability rule for MS13-023 so that this patch only applies to systems that have Microsoft Visio 2010 Viewer with SP1.
  2. Add an applicability rule for Microsoft Visio 2010 Viewer with SP1 so that the service pack can be applied to system that have Microsoft Visio 2010 Viewer with SP0. (Not sure if they have this ability in Patch Management, but that would be the idea.)

MyITGuy | Automating your life to make my life easier.

das Bild der Joshua Rasmussens

The rule for MS13-023 follows the IsApplicable Data for KB2687505 as it is only applicable to clients with Visio 2010 Viewer with SP1 installed. The rules target the precise file to be updated as detailed by the vendor. If the checks line up; the update shows applicable.

My experience with most Microsoft Office Software rules cases; different versions of different components are installed, and that can cause integrity issues with the software to confirm which version is actually installed. This needs to be reviewed per each environment, for the Microsoft Office Software is not always deployed / installed in the traditional methods and the varying software bundled is not always kept under release versions (example: some environments use Visio 2010 and Outlook 2007 simultaneously). This tends to cause anomaly 'rules issues' as the rules get crossed trying to target this type of setup.

This is why I advised to check the resolution on KM: TECH180083, and if this failed to resolve the issue; open a support case and provide the data detailed on KM: HOWTO60789. This data is manditory to review the rule and how it is targeting the client.

However, if further assistance is required; the process on HOWTO60789 will need to be followed through and a support case opened for review, but as this is not being seen among multiple enivornments; it appears to be as detailed above as a one-off anomaly.