Symantec client install error "This installation package could not be opened"

[Migration User]

After creating a new client package install for a 64bit Win 7 machine, it ran fine on several computers. I come to the one I am working on now and once I run the setup.exe or even the Sep64.msi I get the following error "This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package."

I will attach the "SEP_INST" log file for review if that is helpful. Let me know of any other information that is needed.

Attachment(s)

SEP_INST.txt   8 KB 1 version

[ℬrίαη]

I beleive this has more to do with Windows than is SEP related.

Is this an upgrade from a previous version of SEP? If so uninstall SEP and run the Run the Windows MSI CleanUp utility

http://gallery.technet.microsoft.com/MSI-cleanup-utility-3889c8db

[Migration User]

hi,

what sep package do you have install ?

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/this-installation-package-could-not-be-opened/49bed5b7-9569-44de-a14f-47f70e4da25e

 

1620

This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.

ERROR_INSTALL_PACKAGE_INVALIDd

 

[Rafeeq]

right click on the setup.exe file and there should be option called Unblock, 

Unblock it and run the setup again.

go to Properties, you see a Security section which reads: "This file came from another computer and might be blocked to help protect this computer." There is also an option to Unblock the file.  unblock the file, it runs as per normal.

[Migration User]

Are you running the setup.exe directly from network share or locally? Check if you can execute when copied locally and make sure no other instance of the installer is already running.

[Migration User]

This isn't specifially with sep.

http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/this-installation-package-could-not-be-opened/7b227505-ae7f-4ed3-9299-bb92bfe52c1d

 

[Migration User]

@Brian81 This is on a fresh install of windows with no previous Anti-Virus. That clean up tool seemed like it was for office, but it did not work regardless.

@K33 I'm not sure what you are reffering to. It's a client install package for a 64 bit machine, with some specific client install settings and feature sets.

@Rafeeq I do not see an unblock option on any of the tabs for the "Setup.exe". 

[Migration User]

@SebastianZ Ive tried to run the setup from both network, and copying it to the local drive. Both return the same error. Ive insured that the process is not running already with Process explorer.

@theexplorer I have already ran through that microsoft forum and the suggestions did not work for me.

[Migration User]

Few more suggestions i have found on another forums:

1.  try running sfc /scannow from your command prompt to check for and repair any system files or registry issues.

2. is the .msi blocked? Right click on the .msi file and select properties. There will be a button near the bottom of the dialog Unblock. Click this and try running the files again.

3.  make sure that the folder you've got the files in have the appropriate permissions. Check the security settings for the folder these files are in and make sure that the user SYSTEM has full access. After all, the msiexec will run as SYSTEM and will need full control of the directory and all files inside it.

4. Try to re-register windows installer on that machine:

Re-register Windows Installer. To do this, follow these steps:

1. On the “Start” menu, click “Run:.

2. In the “Open” box, type “msiexec /unregister”, and then press ENTER.

3. On the “Start” menu, click “Run”.

4. In the “Open” box, type “msiexec /regserver”, and then press ENTER.

 

5. Can we exlude here any possible corruption of the files while being downloaded to this machine? You have mentioned few other installations were without issues?

6. What is the available free disc space on that machine?

[Migration User]

@sebastianZ I have already tried steps 1-4 several times, unfortunately without any success. I am certain there is no file corruption, i have done file integrity checks, multiple attempts/methods at transferring the files from the SEP server to the machine. I have also tried re-exported the SEP client package. There is more than enough disk space on the computer as well.

[Migration User]

Based on the log you attached below could be the issue. Please check if this helps. If not please post the sis_inst.log if the SEP is version 12.XX

http://social.technet.microsoft.com/Forums/en-US/operationsmanagerdeployment/thread/84a72004-4ef1-4f1f-83c0-0ce1b2fa6f99

SIS_INST.LOG

C:\ProgramData\Symantec\Symantec Endpoint Protection\12.1.671.4971.105\Data\Install\Logs\

C:\Documents and Settings\All Users\Application Data\Symantec\Symantec Endpoint Protection\12.1.XXXX\Data\Install\Logs

[Migration User]

I ran the debug tool and will post the results, as well as the other logs requested. For some reason it seems like symantec doesn't detect any supported applications when it tries to install. Ive tried installing under different user accounts on local and domain without any success.

Attachment(s)

Debug.txt   2 KB 1 version

SIS_INST_4.txt   6.78 MB 1 version

[Migration User]

Make sure C:\windows\TEMP\ is clean

I would need to further investigate this..

[Migration User]

Ive been on this for a few days now. May just do another clean OS install to get it over with.

[Migration User]

Are there any obvious differences on the OSs that the install failed to those that were successful - staying in the scope of win 7 64 bit?

[Migration User]

This the only machine that Ive had a problem with thus far. Nothing is different with the setup. All machines are Win 7 64 bit professional.

I should also note that this machine can run other .msi and .exe files without any hitches.

[Migration User]

Give a last try...

Turn off Windows defender......

[Migration User]

Windows defender has been off for the duration of this event. Going to be reloading the machine today and will update with results.

[Migration User]

ok.. good luck!

[AjinBabu]

Hi, 

Any update on this case.

Regards

Ajin

[Migration User]

Sorry for not getting back to you guys. After reloading the OS onto the machine, the client installed as it should. No further problems have been found with the rest of the batch that were due for upgrades. I will chalk this one up to a weird OS install bug that would have taken Bill Gates to find. Thank you for all the recomondations!

[Migration User]

Hi Guys...the answer of reinstalling the OS is suboptimal and not the real issue.

The problem Sam ran into is what I'm looking at right now: running the MSI across the network as part of GPO can fail.

The test is to run the MSI as the SYSTEM account..."psexec -i -s cmd" will open a command window (sysinternals suite). From there I can generate the failure immediately: msiexec /i [\\server\share\path_to_sep.msi].

Funny thing: I can run the SETUP.EXE from the SEPM-created SEP client install package.

Also, a privileged domain account can run the MSI across the network on this failing host with no problem.

So...this is a permissions issue specific to running MSI from the local system account. In our environment the default OS install is hardened significantly so it's definitely a permissions problem I need to solve.

I'll check back in when I have the fix for this. procmon is definitely your friend in cases like this where event logs / install logs have zero useful information.