Symptom: Unable to retrieve endpoints via the GetRemoteAccessibleEndpoints Service of the Remote Access Subsystem
To initiate the widget's LaunchClient service, the widget needs to be provided a ThingName and RemoteEndpoint on which to start the session. For remote access types that provide multiple endpoints per device, it is usually necessary to use the GetRemoteAccessibleEndpoints service on the RemoteAccessSubsystem. In this case, calling that service may lead to a log similar to the following snippet:
2018-12-31 05:43:35.359+0000 [L: ERROR] [O: c.t.w.BaseService] [I: ]
[U: Administrator] [S: ] [T: https-jsse-nio-8443-exec-7]
[context: com.thingworx.webservices.context.HttpExecutionContext@278ff7c1]
[message: Unable to Invoke Service GetRemoteAccessibleEndpoints on RemoteAccessSubsystem : null]
2018-12-31 05:44:43.219+0000 [L: ERROR] [O: c.t.c.p.ReflectionProcessor] [I: ]
[U: Administrator] [S: ] [T: https-jsse-nio-8443-exec-3]
ErrorCode(1e6527d1-1cb0-4fbb-92d2-ff54c87d48ca),
Cause(null), Reason(Access was attempted on a null reference variable.),
Possible Resolutions(Remove the reference to the null variable within your extension code.
Cause/Action (Administrator Only)
CAUSE: The Axeda Thing does not have a providerName configured ( Thing).
ACTION: The Administrator should set the providerName property on the Thing to a valid instance of RemoteAccessProvider. For example, the GASRemoteAccessProvider Thing. This property is added to the Thing by configuring the Thing to implement the RemoteAccessible Thing Shape.