Recently, one of our Attix5 Backup clients stopped backing up. Turns out the Attix5 Backup Professional SE service was stopped, and when started failed with “Error 1067: The process terminated unexpectedly”

Recently, one of our Attix5 Backup clients stopped backing up. Turns out the Attix5 Backup Professional SE service was stopped, and when started failed with “Error 1067: The process terminated unexpectedly”
We have encountered some issues with clients who already use Symantec Backup Exec and are adding additional off-site backups using Attix5. The problem is caused by both Attix5 and Symante BE using the same listening port (Port 10000) to talk to the backup agents. It seems that the Attix5 dominates the battle, and Backup Exec will then fail with the error :
Completed status: Failed
Final error: 0xe000846b – The resource could not be backed up because an error occurred while connecting to the Backup Exec for Windows Servers Remote Agent.
Make sure that the Remote Agent is installed on the target computer and is running.
??To get around this error, you can change the Attix5 listening port by following these instructions :
service.port=10001
Close the file and save the change.
netstat -anb | more
TCP � �127.0.0.1:10001 � �� 0.0.0.0:0� � � �� LISTENING � � � 160 [a5backup.exe]