Skip to main content
N
nadams110-Marble
10-Marble
June 30, 2016
Question

Error when logging remote property data

  • June 30, 2016
  • 3 replies
  • 5913 views

I'm implementing the SimpleThing example in the Java SDK and I'm trying to log data to a value stream for Temperature.

I'm getting the following error when the logging is enabled

Unable to Invoke Service UpdateSubscribedPropertyValues on TestThing


any help would be welcome.

    3 replies

    P
    ptc-50829061-Visitor
    1-Visitor
    June 30, 2016

    Nick, can you check the permissions for the user on which you try to call that service ?

    Also you can open Composer with this user and check if he has access to that object first and then to the service.

    Let me know if this helps.

      N
      nadams110-MarbleAuthor
      10-Marble
      July 1, 2016

      I suspect that you're right as I have removed Users from the Everybody Orginisation. but Can't use the Java SDK anyway as it doesn't support offline message store and forward so this has now become a noot point.

      Thanks anyway.

      P
      ptc-50829061-Visitor
      1-Visitor
      July 7, 2016

      Nick, regarding the "Unable to invoke Service" error, can you see the object and it's service in Composer with that particular user ? What happens when you try to log data to the Value Stream ?

      B
      BruceHulse5-Regular Member
      5-Regular Member
      July 7, 2016

      There are a lot of cases where the operation in a service is not run as the current user running the mashup. Event responses seem to be executed as System, so you need to grant the access to the operation in the error. In your case, that is the ability to execute the server UpdateSubscriptedPropertyValues on the TestThing entity. It is my experience that you'll just have to deal with these as they come up individually or grant pretty sweeping powers to the System user (which may not be a best practice).

      B
      BruceHulse5-Regular Member
      5-Regular Member
      September 15, 2016

      Looking at this again, it seems that Things/RemoteThing2 resolves to null - is that because of the run time permissions on RemoteThing2?

      W
      waynelove1-Visitor
      1-Visitor
      April 5, 2018

      Had the exact same problem myself (see my previous post) and as it always happens, after asking for help I managed to solve this myself.

       

      The issue is a visibility problem with logged properties.  You need to ensure that the user that is used to do the updates has visibility of not only the thing, but also the Value Stream and the Value Stream's persistance provider (typically ThingworxPersistenceProvider).

       

      HTH eveyone else who has this same problem.  I've wasted far to much time due to PP logging from the Thingworx platform.

        A
        Aruna1-Visitor
        1-Visitor
        June 15, 2018

        Thank you, This helped me

        Terms & ConditionsCookie settingsAccessibility statement