Installation error for v2 Beta 1
Hi
Just tried to install Musescore 2. Seemed to install correctly, but when the installation wizard tried to start the application, I get the error 'The ordinal 2578 could not be located in the dynamic link library LIBEAY32.dll'.
I'm running Win 7 Pro. Nothing unusual in the PC setup. I still have Musescore 1.3 installed.
Thanks
Comments
I should say, that Musescore then opens once I click on the error.
Does it produce the error every time you start the program, or just when starting it from the installation wizard? Could be the problem is in the wizard...
Works fine on Windows 7 for me in any case - no error on installation. It's not some sort of custom installer you are using?
The dll is part of the openssl. I think this message appears only when MuseScore connect is trying to connect to the network. AFAIK, if it does not find openssl, it just does not use this protocol to connect.
A few days ago, when testing one (self-built, debug mode) build, I found a message about missing ssleay32.dll and libeay32.dll in the debug output (coming from a Qt library), but Musescore was starting ok.
It probably needs MinGW-compiled openssl libraries (such as those found in the Qt\Tools\QtCreator\bin folder) and if openssl libraries compiled with Microsoft Visual C++, or old openssl libraries are found in the PATH it probably triggers the error seen in this report.
With recent builds I am not able to see this openssl debug message.
I believe this had been fixed in a nightly meanwhile
The error occurs every time I start Musescore (which does then start) and I don't use a custom installer.
Glad it appears to have been fixed. I don't use the nightly builds so will wait for the next full release.
Cheers
I believe the fix was to switch back from https to http for MuseScore Connect, in 39548b4a8
Hmm, maybe not, as that is in the Beta 1 already.
This bug should be solved since those dlls are now shipped with MuseScore (see for example commit 5235f81c ).
MuseScore2.0-beta2 should behave properly in this sense.
I will mark this as fixed. Please re-open if you see again this bug.
Automatically closed -- issue fixed for 2 weeks with no activity.