Hi,
I'm using the Standalone Cassandra Cluster Installer tool to install a remote Cassandra node.
The installation itself goes well, but during startup of the Cassandra service, following error is shown, which causes the service to stop again:
Some remarks:
- The C:\Windows\Temp\jna--280475957 folder is present on the system, but empty.
- The installation is done through a user account with administrative rights, not the built-in Windows Administrator account.
- Using the DataMiner Installer does allow the Cassandra node to run fine
Any idea what goes wrong here, and if a workaround is available?
Thanks!
From searching around, this issue tends to be related to jna-4.2.2.jar (used by Cassandra) depending on msvcr100.dll (https://github.com/java-native-access/jna/issues/636). The fix for this was included in jna 4.3.0
I believe this basically means that following file should exist when using jna-4.2.2: C:\Windows\System32\msvcr100.dll
On another system we managed to resolve this issue by installing VC++ 2010 Service Pack 1.
From our direct messages, you've already tried to install Service Pack 1.
Perhaps the problem was that the installer page currently links to the security update for Service Pack 1 instead of Service Pack 1 itself? (I'll look into updating this).
We could try to install VC++ 2010 Service Pack 1 itself once more. Instructions for this can be found at https://support.microsoft.com/en-us/topic/description-of-visual-studio-2010-service-pack-1-1f12811e-3826-6728-9f40-b11ee9ae2a0e.
A completely different approach is to look into manually upgrading jna-4.2.2.jar to 4.3+. This approach might require additional testing to verify that this does not result in other problems.
(as far as I know jna 4.3 should be backwards compatible with 4.2.2, I also quickly tested this on my own system and Cassandra did launch).
Thanks Frederic.
Tried your first suggestion – installing VC++ 2010 Service Pack – and the node is starting up fine.
You were right. Only the security patch was installed before, as I followed the download link from the Installer page.
Let’s indeed get that updated with the correct one.