To investigate this further you should enable the following line in the beacon's etdp.trace:
+Scheduling/RemoteExecution
Now if you re-attempt the adoption the output from the trace file should look like the following error:
2.1146, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): error starting execution service
2.1193, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): RPC algorithm complete (intermediate error code: -1, lastError contains: "[RPCCommand]|[StartServiceFailed]|The stub received bad data.
2.1195, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): Failed to execute with RPC algorithm
2.1195, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): Set timeout to 3600 seconds
2.1196, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): Attempting execution using TCP algorithm
2.1196, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): Found winsock version: 1.1
3.1222, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): Socket error whilst connecting: 10061
3.1223, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): Failed to connect to remote server
3.1224, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): TCP algorithm complete (intermediate error code: -1, lastError contains: "[TCPCommand]|[WinsockError]|10061")
3.1224, pid 1004, thread 2632 (Scheduling/RemoteExecution/Common): Failed to execute with TCP algorithm
Other symptoms may include successful adoption from the Inventory Manager server.
Jan 30, 2019 01:27 AM