Unable to access Sisense web application from browser (http://localhost:8081/app/main#/home/newdashboard?ds=Demo2)

Answered

September 07, 2018 13:43

After clicking on dashboard option Sisense Elasticube manager i am getting this error. I was able to open it earlier but now it doesn't seen to work. Can you please help on how to resolve this?

Comments

11 comments

Shawn Springstead September 07, 2018 19:13 (Edited September 07, 2018 19:30)

Did you upgrade to 7.2 recently? Sisense is no longer reachable on port 8081.
Try https://localhost

0

Permalink
Prithvi Pandey September 10, 2018 10:52

The current Sisense is at version 7.2. But when trying to connect to dashboard, it is redirecting me to 8081. We also tried with https://localhost, but no improvement. Please help

0

Permalink
Katie Garrison October 16, 2018 20:52

Hi Prithvi,

Please open a support ticket about this issue if you have not already so our support team can assist.

A configuration change new in Version 7.2 is how the ports are set up. If you are logged onto on the Sisense web server you can check to see which port your Sisense website is running on by navigating to the Configuration Manager page (http://localhost:3030)

Also check to see if SSL is enabled

If SSL is not enabled, you should try this URL:

https://localhost:<port> where <port> is the port number from the Configuration Manager

If SSL is enabled, you should try this URL:

http://localhost:<port> where <port> is the port number from the Configuration Manager

0

Permalink
Prithvi Pandey October 17, 2018 06:45

Ok thanks, i will raise a ticket. The port is 8081 and SSL was disabled. I tried opening https://localhost:8081 only.

0

Permalink
Michael Becker October 17, 2018 09:30

Hi Prithvi,

start with restarting all Sisense services. 7.2 moved to nodejs and sometimes after upgrade not all of them start properly and restart should help.

Regards,

Michał

0

Permalink
Noramaya M Zakri October 29, 2018 15:14

hi all,

I have the same issue.

It was ok after upgrade (7.2)

But suddenly after a week it went down with that error.

Resrat services and reboot doesnt solve this.

0

Permalink
Sisense License November 05, 2018 12:54

I am experiencing the same issue quite frequently. Any solution?

0

Permalink
Prithvi Pandey November 06, 2018 06:41

Hi, I was facing the same issue and trying below steps resolved it:

1) Open the Control Panel
2) Administrative tools
3) Services
4) For each of the services, please find them in the list and repeat steps 5&6, in the following order:

"Sisense.ECMS"
"Sisense.ECMServer"
"Sisense.Repository"
"Sisense.Oxygen"
"Sisense.Broker"
"Sisense.Galaxy"
"Sisense.Gateway"
"Sisense.Jobs"
"Sisense.Identity"
"Sisense.SPE"
"Sisense.CLRConnectorsContainer"
"Sisense.JVMConnectorsContainer"
"Sisense.Configuration"
"Sisense.Plugins"

5) Right-click on it and select Stop (make sure its status field becomes blank)
6) Right-click on it and select Start (make sure its status field changes to "Running")

Restart the IIS web server:

In your start menu type 'cmd'.
Right click the shortcut and choose "Run as Administrator"
In the command line, type: "iisreset" hit Enter and wait for the IIS server to restart.
close the command prompt window.

Refresh your Web Browser page.

If this also doesn't work you might have to reinstall Sisense. I am new to Sisense, would love to hear more suggestions.

0

Permalink
Noramaya M Zakri November 16, 2018 02:12

Hi Prithvi Pandey

Did your problem resolved? Would you share on the steps>

So far I have 3 Windows 10 Pro, failed with Sisense 7.2 installation.

It's either the Web cannot be up at all or, it will have issues connecting to the elasticube server with error

"Unable to reach the Sisense server......." on the datasource Admin page

0

Permalink
Christian Lira February 14, 2019 06:50

Very helpful posting and thank you.

0

Permalink
Ahuva Shabtai May 17, 2019 20:58

I am having the same issue, on a Server. No luck when navigating to localhost:8081, nor :3030. One point to note is that when I restarted (stopped & started) the services, the are in status 'started' - not 'running'... maybe that is a clue?

0

Permalink

Please sign in to leave a comment.

Comments

Didn't find what you were looking for?