This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Warnings with errors 0x00000035(network path was not found) and Error 0x000006BA(RPC server is unavailable)

Hello Team,

Situation: I am trying to migrate the computer a/c to target domain and i was faced with the following issues when i run discovery task in RUM . The log says the discovery is successful but given warning and errors. I neglected this and proceed with processing task in RUM (as discovery is successful)  but still pops up with same warnings and errors.

Here is the log content for your reference

XYZ, Windows Server 2008 R2 Standard Edition x64, build 7601, Service Pack 1
5/9/2017 2:32:41 PM 4400 ================================================================================
5/9/2017 2:32:41 PM 4400 Dell Migration Manager RUM Controller Service version: 8.13.0.337.
5/9/2017 2:32:41 PM 4400 Starting discovery for computer: comp1.
5/9/2017 2:32:41 PM 4400 Impersonating user: admin\user.
5/9/2017 2:32:41 PM 4400 Agent already installed.
5/9/2017 2:32:41 PM 4400 Initializing connection to agent: \\comp1.
5/9/2017 2:32:41 PM 4400 Requesting remote agent version.
5/9/2017 2:32:41 PM 4400 Requesting agent to start processing.
5/9/2017 2:32:46 PM 4400 Remote computer's operating system: Windows 7 Professional x64, build 7601, Service Pack 1.
5/9/2017 2:32:46 PM 4400 Agent returned warnings during discovery.
5/9/2017 2:32:46 PM 4400 Warning: Log path \\xyz\QuestResourceUpdatingLogs$\ is not accessible. Error 0x00000035. The network path was not found. .
5/9/2017 2:32:46 PM 4400 Warning: Configuration path \\xyz\QuestResourceUpdatingConfigs$\ is not accessible. Error 0x00000035. The network path was not found. .
5/9/2017 2:32:46 PM 4400 Warning: The Dell Migration Manager RUM Controller Service is not accessible. Error 0x000006BA. The RPC server is unavailable. .
5/9/2017 2:32:46 PM 4400 Discovery completed successfully.

already verified:my environment

Remote registry is running both on migrator server and host computer in source domain

firewall is disabled on both

machine is pingable from migrator server.

 

Note: The host computer in source domain is running on different Vlan and has firewall in between my Vlan and host computer Vlan.

 

Any sort of guess/answers will be most welcome as i am struggling to resolve this.

  • If anyone of you is getting the same issues then I just find out the answer lies in fixing the DNS server
  • Can you be a little more specific? I am currently getting this error on a project I am just starting.
  • Make sure that short name and long name resolutions works within the environment. From the QMM console to all and visa versa. Make sure you have your DNS suffixes in place
  • The workstation (Comp1) is unable to connect to the console (XYZ). So assuming the console is located in the Target, it's FQDN is XYZ.Target.com. Your workstation on the other hand is located in the source, it's FQDN is Comp1.source.com. By default the domain search suffix is to append the domain naming context of the domain the computer is a member of. That means the source workstation is trying to connect to XYZ.Source.com and DNS is not answering with an IP address.

    The issue is a common one. It is common for Name Resolution to be configured to support the source in the source and the target in the target. As part of a migration you must configure Name Resolution to support both from both. A common way is to use domain search suffixes. So if the workstation had domain search suffix for Source.com and Target.com, this would be a no issue. That also assumes the DNS server in the source knows how to forward or resolve Target.com