Remote Access for Axeda Agent Assets through ThingWorx > Troubleshooting Remote Access > General > Symptom: Call to StartSession service fails
Symptom: Call to StartSession service fails
In general, an error like this is provider-specific, but any general causes for this failure are listed here.
Cause and Actions
CAUSE: User does not have required permissions to start a remote session.
Administrator Action
The Remote Access Extension (RAE) and Axeda Compatibility Extension (ACE) provide services that give administrators a quick way to set up permissions for specific users, as well as user groups to initiate sessions to specific Things or Things implementing a specific Thing Template. The services for the particular provider implementations (and which extension they are defined in) are:
• eMessage Connector/Axeda Global Access Server — From ThingWorx Composer, run the GrantRemoteAccessPermissionsGASFor(Thing|ThingTemplate) service of the eMessageServices Thing. For more information refer to How to Run the Services that Grant Visibility and Permissions.
• ThingWorx Internal — From ThingWorx Composer, run the GrantPermissionsThingworxInternalFor(Thing|ThingTemplate) of the RemoteAccessPermissionsService Thing.
Was this helpful?