Mac OS X Desktop Installation Problem

I am having a problem installing the desktop version of Manager for Mac OS. I have dragged the Manager icon from the dmg to the application folder but when I try to open it, instead of getting the activation code screen I get the following message:

Access to the path “/Users/sb/.local” is denied.

If you want to reset application data path to “/Users/sb/.local/share/Manager”, go to this folder and delete a file “data”.

I can not find a folder named .local, even with hidden files shown.

Does anyone have any ideas on how to resolve this?

What if you go to terminal window and try to navigate into this folder using commands?

Also, have you ever changed application data folder? The reason why I’m asking is that this sort of error should show only if you did and Manager cannot access your custom application data folder.

I’m not very familiar with using terminal but I will give it a try. I have not ever changed my application data folder so I am not sure why it is giving the error.

If you can’t find .local folder in that directory, can you manually create it?

Something must be wrong with my admin permissions on my Mac. I did a system update earlier today and I bet it messed things up. I did manually create a .local file and then I got the error message that it could not open .local/share so I created a share folder and then I got this very long message:

This must be permission issue. But I believe it’s easily solvable by giving your user writing rights to /Users/sb/.local/share/Manager

@ShariB23, it isn’t clear whether this was your first installation or you are updating a prior installation. You need the activation key only upon first installation.

@ShariB23 - can you try the following 4 commands in Terminal and either copy/paste, or screenshot, the output into the forum?

ls -lA /Users/sb | grep local
ls -lA /Users/sb/.local
ls -lA /Users/sb/.local/share
ls -lA /Users/sb/.local/share/Manager

(that’s lowercase “L”, followed by capital “A”)

This will show us what the current permissions are. The lowercase “L” says to list files in the long format which includes permissions, the uppercase “A” says to include hidden files in the list.

The “grep” in the first command filters out just the one we’re interested in, because your home folder is likely to have many files in it, and we don’t care about the permissions on the rest of them.

Thanks for the help. I changed the permissions to read/write on the .local and the share folders and it installed correctly and brought up the activation code page. I don’t know why those folders were missing nor why they were set to read only after I created them but the problem is solved. Thanks again!

As part of writing my post above, I installed Manager on a Mac running 10.11.6 (OS X El Capitan) today, which previously did not have it installed. I noticed that prior to installing, the .local directory did not already exist - it was created by Manager.

Manager clearly had problems creating it for you. It’s very strange, as your user should have no problem creating sub-folders under your own home directory.

I wonder if you ran into any permission issues when you manually created .local? Your post above seems to indicate that you did not.

Yes, I believe somehow when I updated some software on 10.11.6, it must have changed some of my permissions. I did have to enter a password to create the .local file, which I don’t normally have to do. I searched online about repairing my admin permissions and found that they could be reset using the password reset app. (In case anyone needs to do this, you do not enter a new password, nor hit save but at the very bottom is a section to reset the permissions). While doing this reset, my computer never reached the point stating the reset process was “done” but after several hours I gave up on the process and restarted my computer. All permissions appear to be correct for the files on my home folder now. I suppose if I find some that are not, I will now know what to do about it.

So thank you everyone for your input. The problem was obviously one with my computer and not with the Manager app. It now works fine and I am very happy.

Excellent, glad to hear it’s all good now.