Endpoint Protection

We are deploying SEP 11 via a batch file which does the following.
"MSIEXEC.EXE /I "%APPL%\Symantec AntiVirus.msi" /qb REBOOT=ReallySuppress RUNLIVEUPDATE=0 /l*v %APPL%\INSTALLLOG.TXT"
Everything installs fine, but it is taking to long to complete.  I've identified in the log file where the install just hangs, but I don't know how to interpret it.  As you can see it is attempting to do something 25 times, incrementing the wait by 1 second each time, totalling over 5 minutes.  I've also attached the full log file.  Does anyone know what could be causing this?

Thanks

  MSI (s) (04:A4) [03:46:05:015]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (04!2C) [03:46:05:015]: Ignoring failure to remove product during upgrade - product already uninstalled.
Action ended 3:46:05: RemoveExistingProducts. Return value 1.
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 1 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 2 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 3 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 4 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 5 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 6 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 7 seconds before trying again
MSI (s) (04:00) [03:46:41:484]: Running as a service.
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 8 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 9 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 10 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 11 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 12 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 13 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 14 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 15 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 16 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 17 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 18 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 19 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 20 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 21 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 22 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 23 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 24 seconds before trying again
ADMINMOVEFILES: OpenFileMapping() returned 2, waiting 25 seconds before trying again
ADMINMOVEFILES: Unable to open file mapping object after 25 attempts (2)
MSI (s) (04:3C) [03:51:55:031]: Doing action: SetRebootMessageJustInternetEmailNeededArgument

What build are you installing? This issue was addressed in SEP 11 MR4 MP1.

Thomas

Cycetech,

Thanks for such a quick response.  The version we are installing is 11.0.4000.2295
Other then updating the build, is there a way around this?

 hi RHSteeleOH,

Cycletech might have a possible workaround for you, but I don't know of a workaround and they only documentation I can find on this error says that the upgrade is the only fix. I think you will want the upgrade anyways because the newest version fixes other issues, and in my opinion is much more stable. Why were you hesitant on upgrading? 

Grant-

Grant_Hall,

No issue with upgrading, we're downloading it at this moment for testing.  I'm very curious though to what was causing this issue, it may come up again with other products in the future.  Thanks for your reply.

RHSteeleoH

 That portion of the install times-out after 25 attempts when two registry keys are not set properly.This happens when upgrading from certain versions of SAV to SEP.

I hope this answers your question.

Thomas

Solution was to upgrade.  Thanks for all the replys.