Roland Cloud 2.x.x crashing on start Windows 10

31 Dec 2019, 15:20

Roland Cloud Manager crashes on me right after starting. Fresh install of RCM on a fresh install of Windows 10. (i7, 16GB). Attaching the debugger it looks like an access violation in the SSL layer. Roland hasn't responded yet to the ticket. Any ideas? This is stopping me in my tracks using the product.

Note this is the 10th Gen Core i7; I wonder if the SSL version they're using needs to be updated.


...
[Win][2019/12/31 12:13:36.871] (DBManager) Actual DB version (2.4.3)
[Win][2019/12/31 12:13:36.893] (ParentApp) Application ready.
ModLoad: 00007ffb`7a430000 00007ffb`7a6d6000   C:\Windows\SYSTEM32\iertutil.dll
ModLoad: 00007ffb`93840000 00007ffb`9386f000   C:\Windows\SYSTEM32\SspiCli.dll
ModLoad: 00007ffb`65b90000 00007ffb`65bea000   C:\Program Files\RolandCloudManager\ssleay32.dll
ModLoad: 00007ffb`65aa0000 00007ffb`65b8f000   C:\Program Files\RolandCloudManager\MSVCR120.dll
ModLoad: 00007ffb`36f40000 00007ffb`37144000   C:\Program Files\RolandCloudManager\LIBEAY32.dll
ModLoad: 00007ffb`7b9f0000 00007ffb`7ba06000   C:\Windows\SYSTEM32\ondemandconnroutehelper.dll
ModLoad: 00007ffb`86b80000 00007ffb`86c70000   C:\Windows\SYSTEM32\winhttp.dll
ModLoad: 00007ffb`81d70000 00007ffb`81d87000   C:\Windows\SYSTEM32\wkscli.dll
(2248.3d0): Access violation - code c0000005 (first chance)
First chance exceptions are reported before any exception handling.
This exception may be expected and handled.
*** WARNING: Unable to verify checksum for C:\Program Files\RolandCloudManager\LIBEAY32.dll
LIBEAY32!OPENSSL_cleanse+0x1e83:
00007ffb`36f43763 0f2870b8        movaps  xmm6,xmmword ptr [rax-48h] ds:00000193`07651b54=00000000000000000000000000000220

Re: Roland Cloud 2.x.x crashing on start Windows 10

31 Dec 2019, 23:52

More data indiciating the OpenSSL build in RCM is too old for 10th gen Core i7 hardware.

Steps:
1) remove (rename) the libeay32.dll and libssl-3.dll
2) run RolandCloudManager.exe

Now it starts in the service tray (vs crashing instantly) and attempts to connect to the cloud server.

This "works" because it finds newer vesions of libeay32 and ssl in other folders (on my machine the ones Intel installed as part of their iCLS Client.

Last edited by gregsimon on 1 Jan 2020, 21:27, edited 1 time in total.

Re: Roland Cloud 2.x.x crashing on start Windows 10

1 Jan 2020, 07:15

If true, it’s the kinda thing that puts folk off subscription services. in my experience the support team are good, so let’s hope for a quick solution.

Re: Roland Cloud 2.x.x crashing on start Windows 10

1 Jan 2020, 19:06

gregsimon wrote:
...does NOT currently work on new Intel hardware.

How new? I am running a laptop w/ 7-9750H CPU ... current build ... no problems with RCM to speak of.

Which motherboard/chipset/CPU combination are not working?

Re: Roland Cloud 2.x.x crashing on start Windows 10

1 Jan 2020, 21:27

Quad-Core 10th Gen Intel® Core™ i7-1065G7

I ran Intel's CPU tests, and MSFTs memory tests and they both check out.

...I totally agree and the last thing I think would be an issue with RCM. But everything else runs (FL Studio, Cubase Pro, Halion, Spectrasonics KS and OS, Kontakt, Spitfire, iZotope). RCM is the only one not functioning, and given manipulating the libraries makes the situation slightly improve (with 100% repeatability) leads me here.

Re: Roland Cloud 2.x.x crashing on start Windows 10

12 Jan 2020, 23:32

** VERIFIED AND A FIX **

Sure enough, the openSSL libraries the issue here. This problem can be fixed by updating the OpenSSL binaries installed by RCM 2.4.3.

1. Install RCM 2.4.3
2. Download openssl-1.0.2u-x64_86-win64.zip https://indy.fulgan.com/SSL/
3. Unzip and drag all the files from this archive into C:\Program Files\RolandCloudManager
4. Start RolandCloudManager.exe (works!)

I still haven't heard back from Roland even though I included stack dumps in the support tickets, which is disappointing. Hopefully this post helps others until Roland Updates the version of SSL they're using.

Re: Roland Cloud 2.x.x crashing on start Windows 10

15 Jan 2020, 04:42

Has the latest RCM update addressed this?.