[maddoggpt]

Note: There is an article on how to resolve this issue located here:
http://support.jki.n...ror-on-osx-10-7

===
hello all,
I am trying to install the VIPM for Mac and I seem to be gathering an error about not having permission to write to certain areas. My question is how can I go about fixing these permissions? I am the only user and administrator for my mac and running OSX 10.7. I have a feeling it is something to do with Lion changing permissions folders and such but hopefully there is a workaround. Also I have no anti virus installed so I don't think that is the issue either.

Thanks in advanced for the help

PS... I attached a screenshot of the error screen

[jgcode]

[Cross-posted to LAVA]

[Michael Aivaliotis]

Is this an upgrade from a previous version or is it a clean install.
Also, are you trying to install it in the applications folder?

Please attach any error log files located here:
Mac:private:var:folders:04:zdv4h9zj1q567pzfchldfnlw0000gn:T:TemporaryItems:error

[maddoggpt]

Thanks for the quick replies I have never installed VIPM before so this will be a clean install and i attached the error file that you requested.

Attached File(s)

•  July-26-2011.txt (947bytes)
  Number of downloads: 144

[Michael Aivaliotis]

Can you locate the following file?

Mac:Library:Preferences:jki.conf

If it exists, try to delete it. Then try the install again.

[maddoggpt]

There was no jki.conf file and upon re trying the installer I receive the same errors as before

[Pablo Roque]

Hi there,

the problem seems to be due to writing permissions in both '/Library/Preferences' and '/private/var/folder' folders. Since now (OS X 10.7) incorporates some kind of 'security sandbox', you cannot change yourself permission from Finder, I had to make it from the Terminal using sudo. Note here that chmod 775 did not worked for me, so either you add a new user ('username' provided by 'whoami' command) or you make the quick and dirty trick of change the permission temporally to 777.

After that, VI PM installed successfully for me. To install VI's however I had to make the last trick to link successfully VIPM to Labview (8.5 in my case): go to Labview- Preferences - VI Server: Machine Access. Add there 'localhost'.

After that I could make it work, hope it helps,

Best

[maddoggpt]

Pablo Roque, on 02 August 2011 - 10:06 AM, said:

Hi there,

the problem seems to be due to writing permissions in both '/Library/Preferences' and '/private/var/folder' folders. Since now (OS X 10.7) incorporates some kind of 'security sandbox', you cannot change yourself permission from Finder, I had to make it from the Terminal using sudo. Note here that chmod 775 did not worked for me, so either you add a new user ('username' provided by 'whoami' command) or you make the quick and dirty trick of change the permission temporally to 777.

After that, VI PM installed successfully for me. To install VI's however I had to make the last trick to link successfully VIPM to Labview (8.5 in my case): go to Labview- Preferences - VI Server: Machine Access. Add there 'localhost'.

After that I could make it work, hope it helps,

Best

hey pablo thanks alot for your help! Im hoping you could help me even further as I am fairly incompetent in the osx file system haha. How would I go creating the permission using sudo?

Thanks!

[maddoggpt]

can anyone help with the commands for this please?

[Michael Aivaliotis]

We've created an internal case for this #12416. It appears that VIPM 2010 is not compatible with Mac OSX 10.7. We never planned to support OSX Lion with VIM 2010. We are investigating this at JKI and looking at a solution for the next Mac release.

In the meantime, If anyone has found a good workaround for this please post your suggestions.

[Michael Aivaliotis]

Just an FYI. Ni has issued a document describing compatibility issues with Some of their products and Mac OS X (10.7) Lion

See here:
http://digital.ni.co...62578B0006458A5

[Fred]

Is there any news on this? I was able to use VIPM through the fall, because it upgraded fine with from 10.6 to 10.7 (so it works on 10.7, it just won't install), but now both of my primary machines are running 10.7, and I haven't found a way to install VIPM.

A number of my favorite hobby projects are using VIPM exclusively for distribution, and this is locking me out from developing/using this code.

Could we get a timeline and/or a workaround for when the installer might be fixed?
Thanks!

[Erich]

Im also looking for that work around.

Any progress?

Fred, on 18 January 2012 - 05:37 AM, said:

Is there any news on this? I was able to use VIPM through the fall, because it upgraded fine with from 10.6 to 10.7 (so it works on 10.7, it just won't install), but now both of my primary machines are running 10.7, and I haven't found a way to install VIPM.

A number of my favorite hobby projects are using VIPM exclusively for distribution, and this is locking me out from developing/using this code.

Could we get a timeline and/or a workaround for when the installer might be fixed?
Thanks!

[trigger]

Erich, on 28 March 2012 - 07:38 PM, said:

Im also looking for that work around.

Any progress?

Here's a blow by blow of how I got it to work. You must be logged in as administrator:

-open a terminal session (applications>utilities>terminal)

-in the terminal type the following then hit enter:
sudo chmod 777 /volumes/"Macintosh HD"/Library/Preferences

-it will prompt you for your password. Enter it then hit enter

-type in the following and again hit enter:
sudo chmod 777 /volumes/"Macintosh HD"/private/var/folders/p9/0k9fs74n5nz_3bq015z52c340000gn/T/TemporaryItems

-now run the VIPM installer, it should work.

-now restore the original permissions so you don't muck up the files later. Do this by repeating the previous two lines in but change the 777 to 755. They should look like:
sudo chmod 755 /volumes/"Macintosh HD"/Library/Preferences
sudo chmod 755 /volumes/"Macintosh HD"/private/var/folders/p9/0k9fs74n5nz_3bq015z52c340000gn/T/TemporaryItems

You can now close the terminal window and you're done.

[Michael Aivaliotis]

Thanks Trigger for the response. It should be pointed out that the temporary folder path contains a long 'GUID-like' number which is unique on each Mac machine. The error message should tell you what the path is.