4 Replies Latest reply on Apr 1, 2010 1:33 AM by Attila Polinger

    Error installing VSE 8.7i via EPO

    kink80

      Has anyone ran into this when trying to install VSE 8.7i via ePO? This machine did have VSE 8.5i previously. The mcscript.log is attached below as well. I also get an error when trying to install from commnad line "error code 74".

       

      2010-03-30 09:57:11 I #3552 ScrptMgr Error occurred while installing VIRUSCAN8700.
      2010-03-30 09:57:11 I #3552 MueEep Invoking events withEventId " 0" Severity " 4" Productid " VIRUSCAN8700" Locale " 0000" UpdateType " Install" UpdateError " -1" New Version " 8.7.0" Date Time " " Script Id" 6457"

        • 1. Re: Error installing VSE 8.7i via EPO

          Hi

           

          I have not had a change to look at this extensively, but the issue seems to occur in the line above the ones listed here:

           

          2010-03-30 10:50:21.675 I #5920 ScrptExe Running "C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VIRUSCAN8700\Install\0000\setupvse.exe" /leimo "C:\temp\VSEinstall.log"   /q


          2010-03-30 10:50:21.675 I #5920 ScrptExe Did not match searched path

           

          HTH

          • 2. Re: Error installing VSE 8.7i via EPO
            Attila Polinger

            Hi,

             

            you need to enable agent level 2 debug logging so that you can see deep script errors. Please consult KB58966.

            Some script errors never show even on log level 8.

             

            Attila

            • 3. Re: Error installing VSE 8.7i via EPO
              kink80

              Here are the updated log files with Log Level 2 running. I looked at them and I still can't see what the problem is.

              • 4. Re: Error installing VSE 8.7i via EPO
                Attila Polinger

                Hi,

                 

                some vague references has been found in the McScript.log. The Agent starts the setupvse.exe and waits until it finished. It receives  a return code of 74:

                 

                2010-03-31 11:05:32 I #2908 ScrptExe Running "C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VIRUSCAN8700\Install\0000\setupvse.exe" /leimo "C:\temp\VSEinstall.log"   /q
                2010-03-31 11:05:32 I #2908 ScrptExe Did not match searched path
                2010-03-31 11:05:32 X #2908 ScrptExe allocated parameter array successfully
                2010-03-31 11:05:32 I #2908 ScrptExe Executing "C:\Documents and Settings\All Users\Application Data\McAfee\Common Framework\Current\VIRUSCAN8700\Install\0000\setupvse.exe" /leimo "C:\temp\VSEinstall.log"   /q
                2010-03-31 11:05:32 X #2908 ScrptExe Waiting for child process to terminate
                2010-03-31 11:05:35 X #2908 ScrptExe Setting dwRet to 74
                2010-03-31 11:05:35 X #2908 ScrptExe Return
                2010-03-31 11:05:35 X #2908 ScrptUtl Resolve factor dwRet
                2010-03-31 11:05:35 X #2908 ScrptUtl Resolved factors 74
                2010-03-31 11:05:35 X #2908 ScrptExe Line 1778:  Return 74

                 

                Then it maybe translates this into another retcode it returns itself: a 3010 (Reboot needed):

                2010-03-31 11:05:35 X #2908 ScrptExe Line 622:  CallIf FALSE, bRebootNeeded=CheckRebootNeededDuringUninstall

                ...

                2010-03-31 11:05:35 X #2908 XmlWrap Found RebootReturnCode (element) in the element map.  It's value is 3010.
                2010-03-31 11:05:35 X #2908 ScrptExe Got the value of RebootReturnCode.  Setting dwRebootReturnCode to 3010

                 

                This does not tell much about the real reason, to me at least. From the script I saw that it does not find VSE 8.5 installed and VSE 8.7 installed, either (or maybe I missed it).

                The child process returns the error 3 seconds after start, so it might be a failure during preliminary checks.

                If you attempted to deploy VSE onto this host where no previous VSE was installed, then the only viable solution I see here is to grab the installation package from ePO and install it manually, without the /q switch. I sometimes need to do the same, where a mysterious error occurs that cannot be resolved to any human meaning.

                When manual installing, a display of the error should show and tell you more of the cause. I think it is faster than trying to look up error 74 on the internet.

                 

                Two things that could be checked beforehand: 1) %TEMP% space, and 2) reboot then repush to see if the error recurs /i.e. root cause was not a reboot need/

                 

                Attila