Skip to main content
M
MinNan1-Visitor
1-Visitor
July 27, 2018
Question

Selected Analytics Gateway is not connected.

  • July 27, 2018
  • 9 replies
  • 3248 views

hello

 

i work on I work on a local instance of ThingWorx 8.2 with ATE.

 

days before, i couldn't load the dataset,and i find it the reason was "Selected Analytics Gateway is not connected" in the setting.

 

i tried to reinstall ATE but it didn't work.and i have referred the article "https://community.ptc.com/t5/ThingWorx-Developers/Selected-Analytics-Gateway-is-not-connected/m-p/511980" and follow its step, but it is still not sloved.

 

what else can i do to solve the problem?

 

Thanks in advance.

Minnan

9 replies

C
cmorfin19-Tanzanite
19-Tanzanite
July 27, 2018

Hi MinNan

 

You mentioned using a local instance of ThingWorx 8.2 with ATE.
Could you please clarify how did you install this local instance of ThingWorx ?

 

Could you also send:

- the output of the command docker ps -a

- the edge.log file created after executing the command docker logs edgems > edge.log

 

Thank you

kind regards

Christophe

 

M
MinNan1-VisitorAuthor
1-Visitor
July 27, 2018

hi Christophe

 

i am working on win10, and i install the ATE with the docker running.and i use AnalyticsTrialEdition-8.2.0-r3-windows-installer.

tell me if you need more details of that.

 

here is the ouput of the command docker ps -a

 

docker ps -a.png

and the file is in the attachment

 

C
cmorfin19-Tanzanite
19-Tanzanite
July 27, 2018

Hi MinNan

 

Ok so the docker ps -a shows that most of your contianer are ina Exited states, which means they are not running.

Among them is the edgems, thereofre this is why the gateway is not connected.

You will want to:

1) Ensure you have allocated enough Memory to the docker process:

For Docker for Windows , select docker Settings > Advanced > Memory and set at least 5 or 6 Gb

2) Stop the ThingWorx Analytics Trial Edition

3) check with docker ps, that no containers are running or starting

4) start ThingWorx Analytics Trial Edition

5) check with docker ps -a that no containers are in Exited status

Then access Builder

 

Hope this helps

Christophe

 

Terms & ConditionsAccessibility statement