pu.exe return error "can't determine source encoding"
Article ID: 235429
Updated On:
Products
Issue/Introduction
While trying to run probe commands from CMD on primary hub using PU Utility it can't connect with the probe controller or any other probe.
The message is as follow:
C:\Program Files (x86)\Nimsoft\bin>pu -u administrator -p ************* controller
Feb 24 09:35:33:516 2 pu: _nimInit
Feb 24 09:35:33:532 2 pu: nimCharsetSet() - charset=
Feb 24 09:35:34:563 0 pu: nimCharsetAutoConvert() -- can't determine source encoding
Feb 24 09:35:34:563 0 pu: nimSessionNew - _probeCheckin failed - communication error
Feb 24 09:35:35:579 0 pu: Failed attempt to log in to local controller at 127.0.0.1
Feb 24 09:35:36:595 0 pu: nimCharsetAutoConvert() -- can't determine source encoding
Feb 24 09:35:36:595 0 pu: nimSessionNew - _probeCheckin failed - communication error
Feb 24 09:35:37:626 0 pu: nimCharsetAutoConvert() -- can't determine source encoding
Feb 24 09:35:37:626 0 pu: nimSessionNew - _probeCheckin failed - communication error
_command failed: communication error
However if the PU utility is executed from a remote robot, it connects to the primary hub probes.
Environment
DX UIM 20.4.* / 23.4
Cause
pu utility will try to connect to the local controller, usually on port 48000 (127.0.0.1:48000)
The message above indicates the connection failed, due the controller is not running, or due something is actively blocking the connection.
Resolution
1. Check the AV, if any installed, make sure is not scanning the folders and process from UIM
2. the pu.exe will try to connect to the controller on 127.0.0.1:48000. You can use Powershell, and run next to test the connection locally: Test-NetConnection 127.0.0.1 -Port 48000
If it is blocked the output will look as follow. While the connection is being actively blocked the pu will not be able to connect.
If is not blocked the output will look as follow:
Feedback
