Teradata Studio Express launching error

Teradata Studio
Enthusiast

Teradata Studio Express launching error

I’m trying to install Teradata Studio express on my “64-bit windows 10 home pc” and access client Teradata.

The installation looks like successful, I have installed jre-9.0.1_windows-x64_bin.exe and installed Teradata utilities then installed 

 TeradataStudioExpress__win64_x86.16.20.00.00.zip . when I launch the Teradata from desktop it gives me an errorteradata_error1.JPG

 

The error on .log file goes like following

 

!SESSION 2017-12-14 10:09:41.382 -----------------------------------------------
eclipse.buildId=unknown
java.version=9.0.1
java.vendor=Oracle Corporation
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_CA
Command-line arguments: -os win32 -ws win32 -arch x86_64

!ENTRY org.eclipse.equinox.ds 4 0 2017-12-14 10:09:43.060
!MESSAGE Exception occurred while creating new instance of component Component[
name = ConnectionService
activate = activate
deactivate = deactivate
modified =
configuration-policy = optional
factory = null
autoenable = true
immediate = false
implementation = com.teradata.datatools.connection.services.impl.ConnectionService
state = Unsatisfied
properties =
serviceFactory = false
serviceInterface = [com.teradata.datatools.connection.services.interfaces.IConnectionService]
references = null
located in bundle = com.teradata.datatools.connection.services.definition_15.11.0.201711150049 [29]
]
!STACK 0
java.lang.NoClassDefFoundError: java/sql/SQLException
at java.base/java.lang.Class.getDeclaredConstructors0(Native Method)
at java.base/java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.base/java.lang.Class.getConstructor0(Unknown Source)
at java.base/java.lang.Class.newInstance(Unknown Source)
at org.eclipse.equinox.internal.ds.model.ServiceComponent.createInstance(ServiceComponent.java:493)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.createInstance(ServiceComponentProp.java:270)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:331)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at org.eclipse.equinox.internal.ds.ServiceReg.getService(ServiceReg.java:53)
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse$1.run(ServiceFactoryUse.java:212)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.factoryGetService(ServiceFactoryUse.java:210)
at org.eclipse.osgi.internal.serviceregistry.ServiceFactoryUse.getService(ServiceFactoryUse.java:111)
at org.eclipse.osgi.internal.serviceregistry.ServiceConsumer$2.getService(ServiceConsumer.java:45)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.getService(ServiceRegistrationImpl.java:496)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.getService(ServiceRegistry.java:461)
at org.eclipse.osgi.internal.framework.BundleContextImpl.getService(BundleContextImpl.java:619)
at org.eclipse.equinox.internal.ds.InstanceProcess.getService(InstanceProcess.java:730)
at org.eclipse.equinox.internal.ds.model.ComponentReference.getMethod(ComponentReference.java:119)
at org.eclipse.equinox.internal.ds.model.ComponentReference.bind(ComponentReference.java:331)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bindReference(ServiceComponentProp.java:430)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.bind(ServiceComponentProp.java:218)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:343)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
at org.eclipse.equinox.internal.ds.InstanceProcess.registerService(InstanceProcess.java:536)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:260)
at org.eclipse.equinox.internal.ds.Resolver.buildNewlySatisfied(Resolver.java:473)
at org.eclipse.equinox.internal.ds.Resolver.enableComponents(Resolver.java:217)
at org.eclipse.equinox.internal.ds.SCRManager.performWork(SCRManager.java:816)
at org.eclipse.equinox.internal.ds.SCRManager$QueuedJob.dispatch(SCRManager.java:783)
at org.eclipse.equinox.internal.ds.WorkThread.run(WorkThread.java:89)
at java.base/java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: java.sql.SQLException
at java.base/java.lang.ClassLoader.findClass(Unknown Source)
at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:371)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
at java.base/java.lang.ClassLoader.loadClass(Unknown Source)
... 44 more

 

...goes on

 

 


Accepted Solutions
Teradata Employee

Re: Teradata Studio Express launching error

The current version of Studio/Studio Express does not support Java 9.

1 ACCEPTED SOLUTION
6 REPLIES
Teradata Employee

Re: Teradata Studio Express launching error

The current version of Studio/Studio Express does not support Java 9.

Enthusiast

Re: Teradata Studio Express launching error

Thank you!! that solves the problem.Smiley Happy

Re: Teradata Studio Express launching error

Hi, 
Cloud you please share the solution which you implemented. I am facing same kind of issue.

 

 

Enthusiast

Re: Teradata Studio Express launching error

I was using latest version of java jre-9.0.1_windows-x64_bin.exe but apparantly, it is not supported by Teradata studio.

So, i uninstalled jre-9.0.1_windows-x64_bin.exe and installed jre-1.80_151 which solved all problems.

In installation guide they didnt mension that latest version is not supported in a way its bad on their(Teradata)  part.

Hope it works for you.

Re: Teradata Studio Express launching error

Thank you,

 

Even i tried with java 8 version. it resolved my issue. But i got one more issue while creation connection.
Could you please let me know, do i need to edit any config files, before i create new connection in Teradata Studio?

 

 

Highlighted
Enthusiast

Re: Teradata Studio Express launching error

Then it may not be installation error it something to do with your connection to database. you may create a new thread for that with more information hopefully, someone will help you. good luck.