Which causes the Cubase hub to show the “Connecting…” message and never show any web content. Which results in the whole QtNetwork4.dll failing. So the loading throws an ordinal not found exception. And they don’t have the same DLL exports. Which might have been fine, but the DLLs in my system were/are newer than the version eLicenser installs. As a result Cubase was actually loading those versions, instead of the versions in the eLicensers Tools dir. In my case some application (still not sure who) had installed its versions of sslea圓2.dll and libea圓2.dll into my Windows\System32 folder. Since the eLicenser Tools directory isn’t in Cubase’s path, the actual DLLs loaded depends on the user’s path (and a lot of other things including some system settings/etc). These DLLs provide the OpenSSL support for apps that want to us encrypted HTTP. The problem is that QtNetwork4.dll imports sslea圓2.dll and libea圓2.dll DLLs. In a nutshell Cubase (via the hubsupport.dll) loads/uses DLLs from the eLicnenser tools directory (for me this was C:\Program Files\eLicenser\Tools) this includes QtNetwork4.dll. It took a bit but I’ve figured out why and can recommend some solutions. I write Windows applications for a living though and working this out is (sadly) well within my skill set. Some googleing found a bunch of people with this issue but solutions were pretty much non-existent. When I start Cubase 9.5 I was surprised to find that the Hub was always showing Connecting… and would never show any of the content. I picked up Cubase yesterday (so I’ve had it for less than 24 hours) since Cakewalk SONAR early end-of-life.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |