Communication Enabled option is not available on the CASO (Central Administration Server Option) for MBES (Managed Backup Exec Server)

book

Article ID: 100008908

calendar_today

Updated On:

Description

Error Message

Figure 1.

Figure 2.

It shows the following error in the normal logging for BESERVER in Sgmon.

BESERVER: Sending stream message ID 908420131 to CASO-SERVER\DjmAlrQ
BESERVER: TS Send Message
BESERVER: Unable to connect to CASO-SERVER [192.168.100.xx]:3527, error 10061 (No connection could be made because the target machine actively refused it. )
BESERVER: sendMessage unable to initialize send handler
BESERVER: Failed sending message ID 908420131 to CASO-SERVER\DjmAlrQ, status SENT_TO_TRANSPORT
BESERVER: Error sending message 908420131 to CASO-SERVER\DjmAlrQ, status UNABLE_TO_CONNECT (AL 0)

Cause

The port used for communication between CAS and MBES is 3527.  If this is blocked or changed on the CAS the issue occurs.

Resolution

On the CAS and MBES make sure the MQPortID is set to the correct port. This key should not be present in the registry by default.  If it is present, the value should be the same on all media server in the CASO environment.

Warning: Incorrect use of the Windows registry editor may prevent the operating system from functioning properly. Great care should be taken when making changes to a Windows registry. Registry modifications should only be carried-out by persons experienced in the use of the registry editor application. It is recommended that a complete backup of the registry and workstation be made prior to making any registry changes

Go to HKLM\SOFTWARE\Veritas\Backup Exec For Windows\Backup Exec\Server or HKLM\SOFTWARE\Veritas\Backup Exec For Windows\Backup Exec\Server

Create DWORD "MQPortID" and set the value to 3527 (decimal) or any other value which is not used by other application and make sure it is also created on the MBES and set to the same value.

Restart the Backup Exec services after the registry change.

 

 

Issue/Introduction

After successfully adding MBES, Communication Enabled option is not available for the MBES in the CAS Storage tab. Also while trying to share the devices (e.g., OST device or deduplication storage) between CAS and MMS it throws an error "License Information is not available for remote servers in a SSO setup" and option is grayed out as shown in Figure 1 and 2 below: