SOTI Pulse Logo

Legacy Remote Control not working

SD
Stefan Devernon
BMW AG

Hi Guys,

I encountered a problem with the Legacy Remote Control.
It's just one user who has this problem and the Web-based Remote Control is working fine for him.
If he used the Legacy mode, it takes 2-3 minutes, then the Legacy Remote Control is opening, but shows no data or device. After some time, it closed automatically.
 In the log of the deployment server there is a message. Error message is:

"Remote Control token has expired for device" and

"Comm.Client.9: System.UnauthorizedAccessException was captured when processing message: StartRemoteControlMsg:{}" and

"Comm.Client.9: System.UnauthorizedAccessException: Invalid RC token.".
We already uninstalled and installed the plugin again but doesn't work ether.
Do you have any suggestions?

Thanks for your help.

remote-control legacy-rc invalid-rc-token
6 years ago
Android
ANSWERS
A
AKMOD@SOTI
6 years ago

Hi Stefan Devernon

Thanks for your query. Could you please share the following details:
1. Device Manufacturer:
2. Device Model:
3. Operating System of the device and its version:
4. The Profile used: Android Plus/Android Enterprise
5. The network being used to access remote control?

Regards

SD
Stefan Devernon
6 years ago

Hi,

we use Zebra devices. We tried it with TC56 and MC33.

Every time the same problem. On my hand I have no problems to get a remote session to the devices.

Information about the devices:

Android 7.1.2 with Update 19 installed. Profile is Android Plus.

What do you exactly mean with "network"?

There is one server in Germany and all devices are connected to this server. It takes quite some time to establish a connection to the devices in USA but it's working for me and other colleagues stationed in USA. 

Only one person has this kind of problems with the Legacy mode. Web-Version is working fine.

RC
Raymond Chan Diamond Contributor
6 years ago

Is that person having problem locating in a different site from those with no problem?

It's quite abnormal that a RC session needs 2-3 minutes to start.

Maybe he/she should check if the latest OS and .NET patches have been installed and there are sufficient memory resources on the machine running the RC session.

Similar Discussions