Studio will not start with wrong Java version

Studio checks the JAVA_HOME environment variable at startup. To ensure that Studio starts
with the correct version of Java, make sure the JAVA_HOME environment variable points to the
installation directory with the supported version of Java. See Supported platforms. Note that even when the java
-version command shows a supported Java version, it is possible that JAVA_HOME
environment variable is not set to the correct Java installation directory.

NOT ENABLED error: AlwaysOn SQL cell cannot be executed

The AlwaysOn SQL cell cannot be executed when the connection is to a DSE cluster that is
not correctly configured for the AlwaysOn SQL service.

STOPPED error: AlwaysOn SQL cell cannot be executed

HTTP protocol

DataStax Studio does not run with HTTPS everywhere. Preface the URL used
to run DataStax Studio with HTTP and not HTTPS.

Studio won't accept connections from external addresses

By default, Studio binds itself to the IP address 127.0.0.1 (or
localhost). If running in the cloud, this IP address prevents Studio from
accepting connections from external addresses. If you have already installed Studio in the
cloud using localhost, change the httpBindAddress value in the
configuration.yaml Studio configuration file to the IP address of the
host it is running on.

Important: Changing the
httpBindAddress setting from the default (localhost) can pose a security risk as users on
external machines can gain access to notebooks and the DSE clusters those notebooks are
connected to. Studio is designed to be used as a desktop application. Distributed
deployment introduces potential security risks.

Unable to connect Studio to a secured DSE cluster

If you are unable to connect Studio when client-to-node encryption enabled on a DSE
cluster, the Studio log has this
entry:

Cannot support TLS_RSA_WITH_AES_256_CBC_SHA with currently installed providers

Content assist not working

On MacOS 10.12, a network configuration issue when running Studio causes content assist
functionality to become slow or unresponsive. For troubleshooting steps to resolve this
networking issue, see this Stack Overflow post.

Notebook needs troubleshooting

When you export a notebook, you can specify actions for the
notebook. As appropriate, select to include cell code and results or cell code only. For
either of these actions, you can also select to include diagnostics. Exporting a notebook
with diagnostics might include sensitive Information. Credentials are not included in the
export.

Studio UI behaves strangely after upgrade

If you leave an old Studio session open in a browser, using an older version of Studio, and
then upgrade to a new version, you can experience strange behavior. This is caused by
caching in the browser. You can solve this problem by force-loading the
index.html page. For example, if using the Chrome browser, you can
navigate to the top-level index.html page and click on the refresh
button while holding down the control key.

Starting Studio on Windows 10

While running Studio on the Microsoft Windows 10 operating system, out-of-date libraries can
prevent system-specific JNI libraries from being loaded correctly. The result is the
following stack trace:

[Studio-akka.actor.default-dispatcher-4] ERROR akka.actor.OneForOneStrategy ID: TS: - head of empty list
java.util.NoSuchElementException: head of empty list
at scala.collection.immutable.Nil$.head(List.scala:420) ~[scala-library-2.11.8.jar:?]
at scala.collection.immutable.Nil$.head(List.scala:417) ~[scala-library-2.11.8.jar:?]
at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526) ~[akka-actor_2.11-2.4.17.jar:?]
at akka.actor.ActorCell.invoke(ActorCell.scala:495) ~[akka-actor_2.11-2.4.17.jar:?]
at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257) ~[akka-actor_2.11-2.4.17.jar:?]
at akka.dispatch.Mailbox.run(Mailbox.scala:224) ~[akka-actor_2.11-2.4.17.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149

You can fix this problem by updating the Microsoft Visual C++ 2010
Redistributable Package libraries in question:

Starting Studio on Windows 7

While running Studio on the Microsoft Windows 7 operating system, out-of-date libraries can
prevent system-specific JNI libraries from being loaded correctly. The result is the
following stack trace:

leveldbjni-64-
1-6036870325998847314.8: Can't find dependent libraries]
at org.fusesource.hawtjni.runtime.Library.doLoad(Library.java:182)
at org.fusesource.hawtjni.runtime.Library.load(Library.java:140)
at org.fusesource.leveldbjni.JniDBFactory.<clinit>(JniDBFactory.java:48)
at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog.<init>(Level dbEventLog.scala:97)
at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog$$anonfun$7.apply(LeveldbEventLog.scala:358)
at com.rbmhtechnology.eventuate.log.leveldb.LeveldbEventLog$$anonfun$7.apply(LeveldbEventLog.scala:358)
at akka.actor.TypedCreatorFunctionConsumer.produce(IndirectActorProducer.scala:87)

You can fix this problem by updating the Microsoft Visual C++ 2010 Redistributable Package
libraries in question:

You can fix this problem by updating the Microsoft Visual C++ 2010
Redistributable Package libraries in question: