Hi Skyline team,
May I please request for your help to advise as Step 17 command is returning an error for the below procedure.
https://docs.dataminer.services/user-guide/Advanced_Functionality/Security/Advanced_security_configuration/Database_security/Security_Cassandra_general/Cassandra_updating.html?tabs=tabid-1
PS C:\Program Files\Cassandra\bin> .\cassandra.ps1 -install
Get-Command : The term 'java.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling
of the name, or if a path was included, verify that the path is correct and try again.
At C:\Program Files\Cassandra\conf\cassandra-env.ps1:265 char:13
+ elseif (Get-Command "java.exe")
+ ~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (java.exe:String) [Get-Command], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException,Microsoft.PowerShell.Commands.GetCommandCommand
Regards,
Aldin
Hi,
After setting or changing environment variables (as done in step 16), you should open a new PowerShell prompt in step 17 for the changes to take effect. This was not really clear in the documentation, so changed the documentation a bit to emphasize that a new PowerShell prompt should be opened.
Kind regards,
Hi,
Probably the Java is not in the Path variables in the environment variables.
You can follow this guide to set it.
Regards,
Hi Klaas,
The link attached suggests to include in the path variable the location of JDK (e.g. C:Program FilesJavajdk1.x). This implies that JDK should be installed on the server. If I am not mistaken, Cassandra comes with a JDK available in C:Program FilescassandraJavabin
Which JDK should be included in the variable path, the one that comes from Cassandra, or the one that has been installed on the server?
Hi, I don’t think that matters, but indeed the one with Cassandra is the best option.
I would recommend to use the JDK that comes with cassandra as I have seen some issues in the past when the installed JDK versions was different from the one that comes with cassandra.
Hi All,
This is issue is fixed by closing Powershell after Step16. Kindly help to update the procedure.
Thank you.
Regards,
Aldin