Sierra macOS upgrade - Panorama 6 not working properly

I think using Terminal to change this setting, or retaining the allow apps from anywhere from a previous El Capitan system, will both disable Gatekeeper completely, including randomization. I’m not positive though, but I’m pretty sure I had not difficulty doing an install this way. Maybe someone else can confirm? Now that I’ve finally got Panorama 6 working perfectly underly 10.12.2 beta, I don’t want to experiment any further just yet!

When I went from El Capitan to Sierra I found that the “Anywhere” option was missing in the Security & Privacy preference pane even though I’m pretty sure it was checked while still in El Capitan. Regardless, I used the terminal command noted above to force that option to reappear. Jim also said to check to see if my existing Panorama 6 installer would open after the change (he said there was no need to actually do the install). I tried it and it opened without a problem so I’m guessing that Gatekeeper had also been disengaged.

That’s good to hear. They just released the latest 10.12.2 as a Public Beta, so anyone can download it now just by signing up for Apple’s Public Beta program, if anyone else needs the update now.

[quote=“dave, post:31, topic:727”]
You could also replace your existing Panorama folder with a copy of the one on your iMac.
I did try that replacement method, not with the entire folder but just the application replacing the non working app. It was still grayed out in parts.
Thanks for your help and I have now downloaded a new installer but when I click install this is the message I receive:
"SHELL ERROR: ps: No ruser named ‘thomas’ ps: No ruser named ‘hidderley’ " (That is my name)
I have no idea what it means or where to look for a solution. Any help gratefully received.

See my reply under Panorama on macOS Sierra about OS X Cocktail. The Gatekeeper issue is resolved.

I have updated the Panorama Classic FAQ page with the latest information on this topic.

Thanks for the suggestions. I have disabled the Gatekeeper in the terminal window, but I still receive the identical “SHELL ERROR” message as above when I click on the “Install” button.

This is a long running issue, having nothing to do with Sierra. Almost all macOS users have single word account names. For example, my account name is jimrea. The important part is there is no space in the account name. Usually macOS will not allow you to put a space in the account name. Occasionally, however, we’ll run into someone that has a account name with a space in it, as you apparently do. By occasionally I mean that we have encountered this three or four times in the past dozen years, so it is very rare.

Unfortunately, the Panorama Installer won’t work if the account name has a space in it, so that is the problem you are running into. There is no fix for this. You cannot change an existing account name, so the only thing you can do is create a new user account on your computer (see below), and use that to install Panorama. Once you’ve done that you can delete the new account and go back to your regular account, Panorama will work fine. (Or you can leave the new account around if you want, and just ignore it.)


I Googled and found these instructions for setting up a new user account. They are for Yosemite but I don’t think the steps have changed.

In step 4 it says to choose the type of user, you want administrator.

In step 5 you enter the name, and you can optionally enter an account name. Best bet is to let Apple generate the account name for you automatically, but if you do enter an account name, do not include any spaces.

Why don’t you try Dave’s advice and replace the entire Panorama folder with the working copy?

Thanks, Jim. I did set up a new user account, disabled the gatekeeper, and the installer started it’s work. However it stopped 6 times to tell me it could not write various files to disk and asked if I want to continue. I clicked “Yes” six times and was presented with the install log and on clicking “Exit Installer” was told Pan 6 would open.
It did but it was a stillbirth - everything frozen.
I can’t change permissions on the “Library” file, where I suspect some of these files have to go, as it says I don’t have permission. Further help please. Thank you.

@Tom9 I don’t see any mention of what version of macOS you are using. If you are using one of the recent macOS 10.12.1 or 10.12.2 builds that don’t work at all with Panorama 6, you’ll have to update – make sure you have macOS 10.12.2 (Build 16C41B) or later (the later is for any future readers of this post).

The Panorama installer doesn’t put any files in the Library folder.

Was it an administrator account? If it was a standard user account, that might account for the problems you encountered.

I am using 10.12.1 and will now upgrade to 10.12.2 and try everything again. It was indeed an administrator account.
Thanks,

Make sure it is at least Build 16C41B. I’m pretty sure there were earlier builds of 10.12.2 that did not work. The correct build might still be only available as part of the public beta, not thru the regular software update.

10.12.2 is generally not available but only through the beta program.

Robert Ameeti

I have downloaded the beta 10.12.2. Do I have to re-download the Pan 6 package through PanX again or can I use the previously down loaded Pan 6 package?

@tom9 You should be able to use the previously downloaded Pan 6 package.

Answering my own q. I did download Pan 6 again and after entering my licence site info for PanX it started to install. The installer again said it could not write 6 files to disk so I clicked “Yes” six times and it opened. I closed it then double clicked on a Pan db that opened, but opened in Pan sheets! The only way I can avoid this is to open Pan6 and open the db from inside the app.
I would like to thank all those people who put forward solutions to my problems. It took me a long time to implement them as I work on a film set and was trying to do all this on a portable router during downtimes. Thank you all.

Probably the easiest fix for this would be to simply remove Panorama Sheets from your system – I assume you aren’t using it. I think there is also an inexpensive utility you can buy that allows you to specify what exact application should open for each type of file, but the name of it is eluding me at the moment. Maybe it has the word “magic” in the name?

Click on the document that you want to change its ‘originator’. Do a Command-I. Change the ‘Open with’. Use the Change All… if you want all documents of that type to have a new originator app.

Robert Ameeti

Good news, Panorama 6.0 continues to function properly with the latest developer and public beta release of Sierra 10.12.2 (build 16C48b) which came out today. So, if you want to use Panorama 6.0 with one of the latest updates to Sierra, be sure you are using 10.12.2 build 16C41b or later.