Hi ,
i have tried deploying the probe on that robot again and got these logs recorded in distrv :
Feb 21 10:47:33:658 [29140] distsrv: license_check from hubip/55905
Feb 21 10:47:40:832 [29140] distsrv: archive_list from hubip/56122
Feb 21 10:47:40:862 [29140] distsrv: job_add from hubip/56126
Feb 21 10:47:40:872 [29140] distsrv: unzip successful for: E:\Program Files (x86)\Nimsoft/archive/robot_update.zip
Feb 21 10:47:44:927 [31132] distsrv: unzip successful for: E:\Program Files (x86)\Nimsoft/archive/robot_update.zip
Feb 21 10:47:44:941 [31132] distsrv: start_install starting
Feb 21 10:47:44:941 [31132] distsrv: Installation of robot_update on /NPCI_Domain/CHECAUIMHUB01_Pri_hub/hyclpcbivrdb01 started
Feb 21 10:47:44:942 [23692] distsrv: checking ACLs
Feb 21 10:47:44:945 [23692] distsrv: unzip - no files found for E:\Program Files (x86)\Nimsoft/archive/robot_update.zip
Feb 21 10:47:44:970 [23692] distsrv: unzip successful for: E:\Program Files (x86)\Nimsoft/archive/robot_update.zip
Feb 21 10:48:03:879 [23692] distsrv: nimSessionWaitMsg: got error on client session: 10054
Feb 21 10:48:22:792 [23692] distsrv: nimSessionWaitMsg: got error on client session: 10054
Feb 21 10:48:22:792 [23692] distsrv: inst_pkg failed: communication error
Feb 21 10:48:23:146 [29140] distsrv: license_check from hubip/56708
Feb 21 10:48:23:147 [20776] distsrv: Installation of robot_update on /Domain/Primaryhub/robotname finished
Feb 21 10:48:23:147 [20776] distsrv: Recording finishing status of installation of robot_update on /Domain/Primaryhub/robot
Regards
AMar
Original Message:
Sent: 02-20-2020 01:31 PM
From: David MICHEL
Subject: inst_pkg failed: communication error
if the target system is Windows 80040402 could be an error passed back from the OS.
perhaps this will help:
https://answers.microsoft.com/en-us/windows/forum/all/error-code-80040402-while-fix-troubleshooting/22c50f22-0af9-4204-bb53-8360560e7581
------------------------------
Support Engineer
Broadcom
Original Message:
Sent: 02-20-2020 08:31 AM
From: Gene HOWARD
Subject: inst_pkg failed: communication error
so this is going to be a network /firewall issue.
Most likely you have a robot attached to a secondary hub that you are trying to work with.
The secondary hub has both a direct connection to the primary on port 48002 as well as a tunnel setup.
we do not support this.
Either you use tunnels and ONLY connect on the tunnel port 48003 OR you have everything open from 48002-48050 between ALL machines.
The other possibility is that you have a NAT setup between your robot and your hub rather than having the hub on the same network as the hub.
Again not a supported configuration.
Without more details of IP address for the robot hub, hub tier structure, IE how the hub communicates with the primary etc this will be hard to help with
You can use the probe utility PU call back from the primary to do a name to IP call back to find out the IP and port you are trying to connect on that use telnet to test and repeat the process on each hub until you find the problem communication link so that you can correct it.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
Original Message:
Sent: 02-20-2020 06:12 AM
From: Sushant Paluskar
Subject: inst_pkg failed: communication error
The same issue faced for me as well.
Any suggestion?
Original Message:
Sent: 02-20-2020 05:18 AM
From: amar kondraju
Subject: inst_pkg failed: communication error
Hi ,
Original Message:
Sent: 02-20-2020 05:11 AM
From: amar kondraju
Subject: inst_pkg failed: communication error
Hi ,
I have followed the communities already for the same error but firewall is already turned off in our case and still we are facing the below error while trying to deploy probes on robot .
inst_pkg failed: communication error
Regards
Amar