On my macOS Monterey (12.1) on an Intel iMac I’ve downloaded and installed Steinberg Download Assistant 1.31.1.
When I launch it it hangs up forever.
Manually launching it from console I have the following error:
192:MacOS crosati$ ./Steinberg\ Download\ Assistant
09:18:53.881 [main] DEBUG net.steinberg.elicenser.download.singleinstance.SingleInstanceLock - Lock file is: /Users/crosati/Library/Application Support/Steinberg/Download Assistant/net-steinberg-sda.4EA4CA71-30AB-4E8A-A087-757CA9B5E747.lock
09:18:53.891 [main] DEBUG net.steinberg.elicenser.download.singleinstance.SingleInstanceLock - Message file is: /Users/crosati/Library/Application Support/Steinberg/Download Assistant/net-steinberg-sda.4EA4CA71-30AB-4E8A-A087-757CA9B5E747.message
Jan 13, 2022 9:18:54 AM tornadofx.Stylesheet$Companion detectAndInstallUrlHandler
INFO: Installing CSS url handler, since it was not picked up automatically
Exception in Preloader start method
Exception in thread "main" java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Caused by: java.lang.RuntimeException: Exception in Preloader start method
Caused by: java.lang.ExceptionInInitializerError
at java.security.AccessController.doPrivileged(Native Method)
Caused by: java.lang.NullPointerException
... 22 more
However, I think we’ll need to get Steinberg Download Assistant working on your computer so that you can perform the update. It’s worth trying, though, signing in with your Steinberg ID here and clicking the Redeem Download Access Code button. If your eLicenser is registered to your account (so that we can find your existing Dorico 3.5 license to mark it as updated), I think it will work OK this way.
Thank you Daniel, the manual installation and activation worked nicely.
Being a Java software programmer myself, I can help you and your team in testing the future fix of the Download Assistant, please let me know.
Thanks for this info, Claudio. I’ve been in touch with our SDA team, and they suspect that the problem is caused by one or more fonts on your system that is causing an exception to be thrown. My colleague has put together a set of instructions for you to follow that will hopefully allow us to identify the problematic font, if you’re game to give it a try!
Navigate to the Contents/Java folder inside the application bundle folder, e.g.
cd /Applications/Steinberg\ Download\ Assistant/Steinberg\ Download\ Assistant.app/Contents/Java
Open file Steinberg Download Assistant.cfg and the property prism.debugfonts=true under the JVMOptions categrory. It looks something like this:
Thank you Daniel.
I’ve done what you wrote and I found a single entry matching “Name=null”:
Being that also “File=null” what I’ve done was removing all fonts from /Library/Fonts (but nothing changed), then from /Users/crosati/Library/Fonts, and at that point it worked. So using Newton bisection method I’ve moved back fonts until I’ve found:
MT Extra that blocked SDA from starting,
Arial, Arial Black, Arial Narrow and Arial Narrow Bold that were not loaded because of unknown format (these fonts are also in the system font as ttf extensions, so was not a problem removing them).
Now I have my SDA starting correctly. Thank you very much to you and your SDA team.
The Download Assistant has never worked for me in the years I’ve owned Dorico. Not once, not ever. Support has tried many suggestions that didn’t work but we’ve always managed to get Dorico running.
Ok, I got Dorico 4 Pro downloaded, found a place on the web site to enter my Activation Code BUT it reads Verification Pending. I open the support link and it sends me to that damned Download Assistant. Apparently, it needs to reconcile my USB eLicenser before it can generate my real license.
I tried your solution. There are no fonts produce a Null. Download Assistant still doesn’t work.
I’m trying to upload the log but it won’t accept .txt, .rtf so I hope that .pdf works.
Mike, I’ve been talking to a colleague about your case. The original log you posted a few days ago definitely suggests that the Java runtime environment is throwing an exception because of a font it doesn’t like, just like in Claudio’s case. We should try to figure this out, but in the meantime, you should be able to get up and running without needing Steinberg Download Assistant.
If you go to Login and click the Redeem Download Access Code button, then enter the Dorico 4 update DAC you received, you should be given an activation code, which you can copy to the clipboard and then enter in eLicenser Control Center. You can run eLicenser Control Center manually from the Applications folder on your Mac, then click Enter Activation Code, and paste in the activation code you were shown on the web site.
That should then mark your Dorico 3.5 license as upgraded, effectively completing the update process. Then in order to remove the “verification pending” notification in Steinberg Activation Manager (SAM), run SAM, choose to sign out using the account menu in the top right-hand corner, quit SAM, wait 20 seconds (so that the shared process used for licensing operations has time to exit), run SAM again, and sign back in. You should now see that the “verification pending” text has disappeared.
I recommend that this page be updated since that solution is not mentioned. Titling it with a reference to the Download Assistant not running would be a big help. Steinberg Licensing: “Verification Pending” support page
Had that been found on the page, I would have been up and running by now.
No argument there other than the directions you provided to Claudio did not show any such font on my system. Lord knows what old crap is sitting in my Fonts folder after 36 years. BTW, I cleaned out users/_/Library/Fonts and users/_/library/FontCollections years ago to solve other problems so I’m not unfamiliar with the havoc that they can wreak.
Fortunately, there has always been a workaround and I’m glad you found one this time. If Download Assistant is actually useful, it would be nice to experience that.
In the meantime, Apple has told me to expect an answer one way or the other by tomorrow or Monday. I’ll report back one way or the other. Who knows? They may find something useful.
A week later, I heard back from Apple Engineering (many hours over 4 days) and they told me to kick this back to you. I could not get to anyone who would run a trace in real time to see what the hang up is, however, so that they couldn’t find what is not loading is no surprise.
On a whim, I decided to do a Safe Boot with the Shift key down. The Steinberg Download Assistant eventually ran many permission screens later. Of course, I had already resolved the License per your earlier directions.
So… I don’t know what the hangup is other than Apple telling me this is a Steinberg issue. However, since I have workarounds. we can kick the can down the road till next time, I suppose.
At this point, Mike, I can’t really think of a way of resolving this aside from trying the old “binary search”, e.g. move all of the fonts out of /Library/Fonts and ~/Library/Fonts and run SDA. If it then runs, which I would expect, put all of the fonts in /Library/Fonts back and run again: does it still run? If so, put all of the fonts from ~/Library/Fonts back, and run again: presumably it doesn’t, but now we’ve narrowed it down to the fonts in your user fonts folder.
So remove half of the fonts from your user fonts folder and run again: does it run? If so, then we know the problem is in the half you removed, so swap those two halves around and run again: presumably it now doesn’t. So now remove a further half… you get the idea.
Hopefully within a few minutes you could narrow it down to a small set of fonts that cause the problem.
In the meantime, it is allegedly the case that a newer version of the JDK runtime environment has fixed this problem – the bug, by the way, is in the JDK initialisation phase, which is executed before any of our own code in SDA is able to run, so we cannot actually fix the problem. So in theory we should be able to update to a newer version of the JDK in which this problem doesn’t occur, but I don’t know what the timeline for such a move will be.
Since Download Assistant does run correctly when my Mac is booted in Safe Mode, I’ll do the font test but it’ll have to wait till I have some time between deadlines. I am curious, however. That tip might be another item to add to the support document.
I’m in the middle of Apple Support Hell. Long story short, after updating to Monterey 12.2, something has been hanging up my system, I can’t get Apple to run a start-up trace to find the culprit and they’re talking about replacing hardware…
While going through every plug, license, app etc. making sure I was up to date, I found a culprit. Antares is using a run time from WIBU Systems called CodeMeter. Apparently, the version I had from 2018 was causing too many problems to count. Anyway, I downloaded and installed version 7.40 21-12-2021 and rebooted. WiBu Support and Downlads
Most of my problems went away and Download Assistant now works.
I also found a few corrupted fonts that weren’t showing up in any reports.
I’m sorry that you’re going through support hell, Mike, but that’s interesting data, and I’m glad that at least Steinberg Download Assistant is now running on your system. Thanks for circling back to let us know.