Run-Time Errors on Mac M1 Configuration
I’m trying to install PRC2020.3.10 Gold on a Mac M1 running Excel 2019 on Big Sur. Right after I enable the macros I get this error message:
"Run-Time error ’91’: Object variable or With block variable not set"
Are there known issues that could cause this problem?
Mac computers with Apple’s M1 CPU (instead of Intel’s CPU) do not fully support Excel 2019 (and possibly other versions as well) and this results in run-time errors when attempting to run Pralana Gold on the Mac M1 architecture. Until such time as this is resolved, Excel must run in conjunction with Rosetta. Here’s a link to an article that gives a little background on the issue: https://appletoolbox.com/what-is-rosetta-2/ . Here’s another article that provides guidance on specifically what you need to do to make your M1 system run Excel 2019 correctly: https://support.apple.com/en-us/HT211861 .
Here's some specific guidance on how to work around this problem if you have a Mac with the M1 chip, shared by one of our helpful users (thanks, Larry!):
If you control-click on the Excel icon in the Finder, and then on “Get Info”, you can check the box labeled “Open Using Rosetta.”
I am using an M1 also. However, when I click on the "Open With" in the Finder, I am provided a drop down with the options of choosing Excel, Numbers, App Store or Other. There is not a box to check.
Does that make sense?
Just to add to this, I have confirmed that Rosetta is running in the background, so the Runtime error 91 message I am getting might be related to something else.
I am having the same issue with my new mac (M1 chip). Did yours get resolved?
I just encountered this error and so I downloaded Rosetta. I seem to have the same problem as above, when I try to use the open with feature the choice Rosetta does not come up. Any other ideas? How do I verify Rosetta is running in the background?
Not sure if you every got an answer. I was not able to get the issue resolved as Pralana maintains this is an apple/excel issue. I'm not convinced of that since rosetta should solve any of those incompatibility issues. I confirmed I have rosetta installed on my mac mini so it should run in the background if needed. This was my last communication to the admin at Pralana:
Stuart, thanks for your reply. I have Rosetta 2 installed on my Mac but this is obviously not a fix. According to the guidance, I should be prompted to install rosetta if i try to launch an intel based app but that does not happen. In fact when you look at Excel in software section it now shows as a “universal” app which should run fine with M1:
I'm not expecting any help on this so pretty frustrated about paying for the gold version and unable to use the software
@clarke461 Michael, yes, that makes sense but I don't personally have a Mac with the M1 architecture or Rosetta, so I'm relying on other users to help with this. I did go through this on my newest Mac and after clicking Get Info I am seeing another "Open With..." option. I'm just guessing that this is where Rosetta might appear if it was installed.
@holbrook304 Mark, I wish I could help on this but don't have a Mac M1 nor Rosetta so, at least for now, I'm dependent on other users to provide some assistance here.
I decided just to run it on my main mac which does not have the M1 chip. The program works fine on it.
@gtpotter Greg, this is most definitely not the first case where MS says everything's fine and yet I have to implement workarounds for Excel within PRC. Further, some macro language commands simply do not work correctly on Excel for Macs, which is why you observe flashing screens when doing PRC imports (just one example). Regardless, since MS now believes that the latest version of Excel is compatible with the Mac M1 without Rosetta, I will have to attempt to figure out where the issues are and try to develop workarounds. I plan to start addressing this issue in mid-September and will be soliciting user help. If you and/or others are interested in helping me run test versions of PRC to collect some information and then test potential workarounds as I develop them, I'd appreciate it very much. Thanks!
@holbrook304 Thanks, Mark, for that additional data point. As I said in my response to Greg's input above, I plan to dig into this issue in mid-September to see if I can figure out exactly where the problem lies and then I may be able to develop a workaround.