Since upgrading to 2.2.4 I’m getting the following:
There was an error executing SysOptimizer. Not all optimizations may be done.
Error = The operation couldn’t be completed. (OSStatus error -1.)
Different OSStatus error code than before.
Any advice as this is proving to a a real problem with my headless Mac Mini system
I do get the OK button but it cannot be pressed from the Audirvana remote. I run a headless Mac MIni and so to get that OK button pressed I have to either launch a VPN viewer on my iPad; log-in to the Mac Mini using Screen Sharing from a second computer or reboot the Mac MIni with the connected TV set switched on. None of which I really think I should have to do every time I want to play music.
I don’t think this is the same fault (which threw a OSsystem error -22) that happened when folk updated to Ventura with AS version 2. There was a temporary workround and then a fix in version 2.2.3(?). Apple’s error messages are opaque but somewhere in the Apple Community there’s a suggestion that -1 means a network connection error even though your Internet is up and running.
David
Oh. Yes. I’ve had that problem in the past. I no longer use the Mac Mini… I had huge trouble getting the remote to work… Now works pretty well so I transferred my AO to my main Mac… but that’s no help to you.
…
This only happened to me (SysOptimizer issue) when AO updates. Is that the same for you. If so, you might have a screen read to use with MiniMac on those occasions.
Have you tried using disk utility and running the first aid option on your disk? OSStatus error 1 is often associated with file/disk permissions errors from past experience.
Thanks for the suggestion - I’ll give it a try and report back
[LATER]
I’ve run Disk Utility on all three partitions (Macintosh HD, Macintosh HD Data and Mac OS Base system). No errors reported all clean. Restarted the MacMini - launched AS and as yet no OSStatus error code - again I’ll se what happens when I switch the DAC back on later tonight.
I’ve updated to 2.2.5 and got the same error - so far this evening there has been no return problem but I’ll wait till I switch back to the DAC for another listening session before claiming things are fixed.
I wasn’t here for some time so couldn’t answer you (no, Audirvāna is not on strike @OffRode ).
So the ‘restart your computer’ thing worked in your case, good to know that. If you have this error again, please come back here and I will help you find what is going on