Video Screencast Help

OS X package install failure on some systems

Created: 12 May 2010 | 13 comments

Hey there,

Just trying to get SEP for OS X working and I can install the package on some systems and then it just fails on others.
All systems are up to date and this is SEP RU6 of course :)

I was wondering if anyone else had seen this at all?

Error messages are as follows:

May 12 16:36:50 mac02480001 Installer[46751]: Could not run InstallationCheck in the Symantec Endpoint Protection package. launch path not accessible
May 12 16:36:50 mac02480001 Installer[46751]: Installation checks failed.
May 12 16:36:51 mac02480001 Installer[46751]: Installation check failure.  Symantec Endpoint Protection can’t be installed on this computer.. An error occurred while running the InstallationCheck tool for “Symantec Endpoint Protection”. Try running the tool again..
May 12 16:36:51 mac02480001 Installer[46751]: Could not run VolumeCheck in the Symantec Endpoint Protection package. launch path not accessible

Comments 13 CommentsJump to latest comment

anand sankruthi's picture

If you have unzipped the Mac client using the "unzip" command line utility, then you may end up with this error. Try using the build it archive utility (just double click the zip file) and installing from there.

sandra.g's picture

"Systems up to date" -- which operating system/s?

sandra

Symantec, Information Developer
Installation, Migration, Deployment and Patching
User Protection & Productivity, Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best help

Grant_Hall's picture

As sandra asked...what operating systems? Also what generation of macs are you using? Trying to find some difference between the ones that failed and the ones that worked.

Grant-

Please don't forget to mark your thread solved with whatever answer helped you : )

zer0's picture

I have been trying to find the exact difference and am struggling as this is the first time I have tried to get SEP for MAC running.


  • Package is unzipped by double clicking
  • Standard package off the source media fails the same way as an exported one from the SEPM
  • Systems are standard 32 bit
  • SAV for Mac has not been installed previously
  • OS X 10.6 and above

It works fine on my virtualbox setup as well as a 2008 15" MBP and also a current 13" MBP
Fails on my clients imac and mac mini systems but I am trying to work out if that is the only difference.

Does anyone else have it running on mac mini, imac or mac pro ??

Any help appreciated

Z

sandra.g's picture

I have it running on a Mac Mini, Intel, 10.6.3.  Previously has had SAV for Mac and even NAV for Mac on it.

"launch path not accessible"--is it being run locally (from like the desktop)?  I presume you are an Administrator on the box since you've had successful installs on other machines.

One thought--is Rosetta installed on the ones that work, vs the ones that do not (Snow Leopard, 10.6)?  I am not aware of any Rosetta dependencies for SEP, but I know the installer for SAV for Mac has those dependencies.

Maybe try the old standby -- Disk Utility permissions repair and volume check -- and see if you have better results.

sandra

Symantec, Information Developer
Installation, Migration, Deployment and Patching
User Protection & Productivity, Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best help

zer0's picture

Thanks for the reply Sandra.
I have a support case open if you wanted to check in at all - 412181387

Admin...superuser...root...makes no difference.
Also tried using the command line install option rather than the gui but that didn't help either.
Tried running it from desktop and other folders but they all fail.

I will double check Rosetta and disk permissions repair and see if it helps but don't have access to the test systems as the guy is away this week

sandra.g's picture

I took a peek at the case and did some research regarding what that message typically means... is there anything unusual or different about this machine's operating system installation?  Was the installation package transferred via iChat or via USB drive?  Is the format of the volume case-sensitive?  It's not a common volume format but I would expect it to cause problems.

Is there anything more after this line?
May 12 16:36:51 mac02480001 Installer[46751]: Could not run VolumeCheck in the Symantec Endpoint Protection package. launch path not accessible

I would attempt installing again, then pull a System Profiler report as mentioned above from the affected machine, and upload it here and to the case.  When you can. :)

(I found this, which mentioned the iChat thing: http://scplugin.tigris.org/ds/viewMessage.do?dsFor...)

sandra
ps. There shouldn't be any Rosetta dependencies for installation or operation of the program... my neighbour installed it to his SL box and does not have Rosetta installed.

Symantec, Information Developer
Installation, Migration, Deployment and Patching
User Protection & Productivity, Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best help

sandra.g's picture

I looked at the files uploaded into the case.  The line that specifically caught my attention is (redacted for privacy):

May 13 09:31:10 mac02480001 installd[23305]: PackageKit: Executing script "./preflight" in /Users/xxxx/
Desktop/Symantec Endpoint Protection.mpkg/Contents/Resources
May 13 09:31:10 mac02480001 installd[23305]: PackageKit: *** launch path not accessible

(oddly, I do not see the 'VolumeCheck' message in the install log included with the Profiler.)

When I looked at my installer package, the preflight script has the permissions -rwxr-xr-x.  Can you confirm this to be the case on yours?  In fact, all of the scripts have the same permissions, as do the folders.

I looked through the (very long :) ) list of installed apps and couldn't really tell for sure, but it seems this machine is used for development--is that the case?  Is the machine on which the install worked used for development?  Just wondered if something about a development package might be affecting installations.

Thanks,
sandra

Symantec, Information Developer
Installation, Migration, Deployment and Patching
User Protection & Productivity, Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best help

pereiraashley's picture

Customer discovered that there was a program "The Unarchiver" that was installed on the systems facing the issue.
Uninstalled the program and ran the install for SEP and it installed without any issues
I was able to reproduce the issue in my lab with the program installed.

sandra.g's picture

Thanks for the update!  Glad to hear it's resolved.

Does that program take over unzip/unarchiving from the operating system?  If so, I bet it was interfering with the permissions, if so.

sandra

Symantec, Information Developer
Installation, Migration, Deployment and Patching
User Protection & Productivity, Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best help

pereiraashley's picture

Yes, Once installed this program is used by operating system for unzipping..

zer0's picture

It did change the persmissions but the weird thing is that this is the only application out of hundreds it has affected...

sandra.g's picture

Don't know why the permissions were so affected when other programs are not...

sandra

Symantec, Information Developer
Installation, Migration, Deployment and Patching
User Protection & Productivity, Endpoint Protection

Don't forget to mark your thread as 'solved' with the answer that best help