You can translate the question and the replies:

Installing Denodo Express

I am attempting to install Denodo Express 8.0 on a Linux CentOS VM in Azure but get the following message when attempting to start the installation process using install.sh. Can anyone advise please? Exception in thread "main" java.awt.AWTError: Can't connect to X11 window server using 'localhost:1.0' as the value of the DISPLAY variable. at java.desktop/sun.awt.X11GraphicsEnvironment.initDisplay(Native Method) at java.desktop/sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:102) at java.base/java.security.AccessController.doPrivileged(Native Method) at java.desktop/sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:61) at java.base/java.lang.Class.forName0(Native Method) at java.base/java.lang.Class.forName(Class.java:315) at java.desktop/java.awt.GraphicsEnvironment$LocalGE.createGE(GraphicsEnvironment.java:101) at java.desktop/java.awt.GraphicsEnvironment$LocalGE.<clinit>(GraphicsEnvironment.java:83) at java.desktop/java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:129) at java.desktop/java.awt.Window.initGC(Window.java:487) at java.desktop/java.awt.Window.init(Window.java:507) at java.desktop/java.awt.Window.<init>(Window.java:549) at java.desktop/java.awt.Frame.<init>(Frame.java:423) at java.desktop/java.awt.Frame.<init>(Frame.java:388) at java.desktop/javax.swing.SwingUtilities$SharedOwnerFrame.<init>(SwingUtilities.java:1919) at java.desktop/javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1995) at java.desktop/javax.swing.JWindow.<init>(JWindow.java:183) at java.desktop/javax.swing.JWindow.<init>(JWindow.java:135) at com.izforge.izpack.installer.SplashScreen.<init>(Unknown Source) at com.izforge.izpack.installer.Installer.main(Unknown Source)
Denodo Express
user
19-04-2023 05:51:36 -0400
code

4 Answers

Hi, I’ve found a similar question about that error linked [here](https://community.denodo.com/answers/question/details?questionId=9060g0000004FTeAAM&title=Getting+Can%27t+connect+to+X11+window+server+using+%27%3A0.0%27+as+the+value+of+the+DISPLAY+variable+error). According to that answer, you have to remove the DISPLAY variable by executing the below command and run the script. `unset DISPLAY` Hope this helps!
Denodo Team
20-04-2023 06:53:59 -0400
code
Hi, Thanks, I tried above but then get the below error: java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. java.awt.HeadlessException: No X11 DISPLAY variable was set, but this program performed an operation which requires it. at java.desktop/java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:208) at java.desktop/java.awt.Window.<init>(Window.java:548) at java.desktop/java.awt.Frame.<init>(Frame.java:423) at java.desktop/java.awt.Frame.<init>(Frame.java:388) at java.desktop/javax.swing.SwingUtilities$SharedOwnerFrame.<init>(SwingUtilities.java:1919) at java.desktop/javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:1995) at java.desktop/javax.swing.JWindow.<init>(JWindow.java:183) at java.desktop/javax.swing.JWindow.<init>(JWindow.java:135) at com.izforge.izpack.installer.SplashScreen.<init>(Unknown Source) at com.izforge.izpack.installer.Installer.main(Unknown Source)
user
21-04-2023 05:17:50 -0400
Hi, To overcome this error, you could use a server that has graphical support to launch the install.sh or if you are accessing from a command line interface like Putty or Winscp, you need to have X display like Xming or Xlaunch in the machine from where you are accessing your Virtual DataPort Administration Tool. Once you have an X display installed on your machine, you’d have to export the X display using the following command (if you are on the main display): `export DISPLAY=<host>:0.0` Hope this helps!
Denodo Team
21-04-2023 07:49:11 -0400
code
Hi, Using export display caused the same error and also stops the xclock showing up. xclock shows up fine without using export display. I manged to get past this by using a GUI file manager but later discovered that the permissions on the install.sh weren't at the corrrect level. Anyway, this has been resolved now, thanks.
user
27-04-2023 10:09:36 -0400
You must sign in to add an answer. If you do not have an account, you can register here