Skip to main content
1-Visitor
August 4, 2016
Question

Installing Thingworx 6.6 : Error relation "root_entity_collection" does not exist

  • August 4, 2016
  • 3 replies
  • 5253 views

Hello,

I'm getting ERROR: relation "root_entity_collection" does not exist, while installing Thingworx 6.6.

I've added 'SEARCH_PATH' item as mentioned in this blog

Frequently Seen Errors upon launching the ThingWorx application:

error_1.pngerror_2.png

I've attached application logs along with the post.

Aanjan Ravi

3 replies

5-Regular Member
August 4, 2016

You should not have the words mySchema in your SEARCH_PATH. Instead, modify that to say only "$user",public instead.

*EDIT* You can have mySchema in there if you have created such a thing for the ThingWorx tables to reside in, but I'm assuming you did not and you should just use ​public ​instead. I would restart your database service after you do this, just to ensure the changes take effect.

Meghan

spatel-211-VisitorAuthor
1-Visitor
August 4, 2016

Getting the same error after that modification. Yes I did restart the service

5-Regular Member
August 4, 2016

If you have your schema named ​mySchema​, then adding that to the SEARCH_PATH was correct, and probably should have worked. I'm assuming you changed this when you ran the setup script for the schema? If you don't need to rename your schema and just want to get ThingWorx up and running I would recommend wiping out the schema and re-running that batch files.

I'll keep looking if there is another fix for this that we aren't seeing.

Meg

spatel-211-VisitorAuthor
1-Visitor
August 6, 2016

Hi Meghan,

I did re installation, but this time kept public as schema and it worked.

As of now Thingworx is running fine.

Thanks for your help.

-Siddharth

5-Regular Member
August 4, 2016

Postgres Error: root entity collection does not exist 

The above link may be helpful as well.

**EDIT** Alright, one more thing, set the path to "$user",mySchema,public

The order matters, and it reads left to right. Since the $user schema most likely doesn't exist it'll ignore that and move on. I'm not sure if the public one exists by default but that may be why ThingWorx was confused because, it was looking there first because it exists and then doesn't find anything. Give it a shot and let me know if that still doesn't work.

Meg