Skip to main content
W
Willie16-Pearl
16-Pearl
April 17, 2019
Solved

What is causing this? "Could not set properties on server. code: 500, resp:"

  • April 17, 2019
  • 2 replies
  • 1895 views

What does the following line mean?

"[INFO ] 2019-04-17 00:18:48,841 CrewRover1_wwong: Attempting to GetPropertySubscriptions from server failed. code: 500, result:"

I keep getting this line in my LSR log, but i'm not sure what it means.

 

Another line I'm not sure about is....

"[WARN ] 2019-04-17 00:19:11,60 thingworx.server: Could not set properties on server. code: 500, resp:"

What is causing these lines?  Does it mean that my EMS and LSR are not bound correctly?

 

How can I fix these?

Please see the attached LSR log file for the full log.

Best answer by Willie

Never mind.  It was a visibility permissions issue.  It's working fine now after adding the org unit with the user group to the visibility instance of the thing template.

2 replies

W
Willie16-PearlAuthorAnswer
16-Pearl
April 17, 2019

Never mind.  It was a visibility permissions issue.  It's working fine now after adding the org unit with the user group to the visibility instance of the thing template.

S
slangleyCommunity Manager
Support
April 17, 2019

Hi @Willie.

 

Since you found a solution to your issue, please mark your follow-up reply as the Accepted Solution for the benefit of users with the same issue.

 

Regards.

 

--Sharon

Terms & ConditionsAccessibility statement