The issue is with communication between the avagent.exe and the tray icon avscc.exe. The avagent.exe runs on a local Network Interface Controller (NIC) and listens on port 28002. The avscc.exe (tray icon) connects to 28002 to interrogate the avagent, and list the backups. Occasionally a backup administrator must use either a different NIC (when there are two) or a different port (when another program uses 28002).
This scenario has not had issues in the past. Using either to allow proper communication, --netbind==300.427.530.730 or --listenport=45015 on the avagent.cmd to customize the communication for avagent.exe. Respectively for the avscc.exe in the avscc.cmd to customize the communication using either --acaddr=300.427.530.730 or --acport=45015.
The issue occurs when we must change both simultaneously. The code in avagent.exe gets confused or is not present to properly handle the combination of both flags. The developers have adjusted and added code to allow for both the NIC and the PORT adjustments to be handled in an appropriate way.
The supplied test binary for avagent.exe has the appropriate code changes so that on the avagent.cmd, --netbind==300.427.530.730 AND --listenport=45015 together may be used.
This allows the avscc.exe to have both the respective flags in the avscc.cmd, --acaddr=300.427.530.730 AND --acport=45015 allowing for proper communication.
Resolution:
Upgrade the Avamar Server to version 19.7.100-82 or later. The fix is incorporated in Avamar 19.7 and later software releases.
Follow the below steps after upgrading to the above version.
Create or edit a file that is in c:\Program files\avs\var on the client system. Call the file:
avagent.cmd --netbind=300.427.530.730 --listenport=45015 avscc.cmd --acaddr=300.427.530.730 --acport=45015
Ensure .txt does not get automatically added by notepad, for example avagent.cmd.txt, Check this by showing extensions.
Restart the backup agent service and the tray icon.