'Failed getting progress' notices during upgrade
Affected versions
From DataMiner 10.4.0 [CU0]/10.3.7 onwards.
Cause
When you connect to a DataMiner Agent via localhost or 127.0.0.1, a special local connection called slnetIPC is used, which utilizes IPC (Inter-process communication). An edge case in the upgrade logic causes the monitor to incorrectly parse slnetIPC as a hostname, causing the upgrade events to not come through.
Note
The upgrade that was launched will still be progressing in the background. It is only the monitoring of the event that is affected.
Workaround
To keep this issue from happening, connect to the system using the local IP or hostname instead of localhost or 127.0.0.1.
If you have already started an upgrade and encounter this issue, you can take the following steps:
Close DataMiner Cube.
Reconnect using the local IP or hostname (avoid using localhost or 127.0.0.1).
If you are unable to connect but you see the message DataMiner is busy upgrading. The connection will be established when finished. Please wait..., click Monitor.
If you are able to connect to the DataMiner Agent:
Go to System Center > Agents.
Right-click the Agent you launched the upgrade from, and select Upgrades.
In the pop-up window, right-click the package you used to launch the upgrade and select Attach.
The monitor should now show all the events.
Fix
No fix is available yet.
Description
During a DataMiner upgrade, no progress events are shown, but instead the following message is repeatedly shown:
Failed getting progress from http://slnetipc:8004//UpgradeService: The remote name could not be resolved: 'slnetipc'
This happens when the upgrade is launched in a DataMiner Cube session connected via localhost. You can verify this in Cube by clicking the user icon in the top-right corner and selecting About. In the connection tab of the About window, look for Connection String or Connection String (NR). If either or both says ipc://slnetipc/SLNetService, this issue will occur.
