1. Browse to the %systemroot%\system32\drivers\etc
2. Locate the sfm_resolv.conf file with a text editor (i.e. notepad)
3. Look for the cs_config_name entry. If the VOM server is not listed, this is the cause of the issue.
[domains]
sfm://Server1.Domain.local:5634/ = "";
[sfm://Server1.Domain.local:5634/]
controller = https://192.168.20.10:5634/;
ping_freq = 300;
cs_config_name =
ip = 192.168.20.10;
mh_hostname = server2.domain.local;
eat_data_dir = "C:\\ProgramData\\veritas\\VRTSsfmh\\sfm_server2.Domain.local\\sec";
families = {DB:{registered:1},HOST:{registered:1},HYPERV:{registered:1},PERF:{registered:1},VCS:{registered:1},PC:{registered:1},SF:{registered:1},NATIVE:{registered:1},NR:{registered:1},LDR:{registered:1}};
primary_broker = vxss://Server1.Domain.local:14545/sfm_agent/sfm_domain/vx;
4. Enter the Fully Qualified Domain Name (FQDN) of the VOM/CMS server for this entry
Example:
cs_config_name = Server1.Domain.local
Note: if the entire cs_config_name line is missing, manually add it above the ip value as shown above.
5. Save the file and this error should no longer be reported.