How to do i fix Error ID 960 of dependency varification failed in azure migrate

Ashish kumar Sharma 1

Error ID

960

Error message

Invalid or null result.

Possible causes

The operation failed due to an internal error.: user1, user2, user3

1 answer

Pavan Minukuri 280 Reputation points Microsoft Vendor

2024-10-09T19:34:19.8933333+00:00
Hi Ashish kumar Sharma
Welcome to the Microsoft Q&A Platform! Thank you for asking your question here.

To create a project and register the Azure Migrate appliance, you must have an Azure account that has these permissions:

-Contributor or Owner permissions in the Azure subscription.

-Permissions to register Microsoft Entra apps.

-Owner or Contributor and User Access Administrator permissions at subscription level to create an instance of Azure Key Vault, which is used during agentless server migration.

Check Permissions and Access Rights

Ensure the service accounts or users (user1, user2, user3) performing the migration have sufficient permissions:

RBAC permissions for the Azure subscription and resource group. Ensure the service principal/User used for the migration has proper roles such as "Contributor" or "Owner" on the target resources.

Inspect Migration Project and Components

Review the specific components in your Azure Migrate project (e.g., Discovery, Assessment, or Migration Tools):

3.Ensure that Discovery is working properly, and all source machines are listed.

If the issue arises during migration, check that you have the correct target resources set up in Azure (VMs, storage, network).

Verify that the Azure Migrate appliance is healthy and properly connected to both the on-premises environment and Azure.

4.Review the logs for more detailed error messages. Logs are typically located in C:\ProgramData\Azure\AzureMigrate\Logs

Reference Link: https://learn.microsoft.com/en-us/azure/key-vault/general/rbac-migration

If you are not satisfied with the above answer, please let us know where exactly you are encountering the error during the discovery or assessment process.

If you have any further queries, do let us know.

If the answer is helpful, please click "Accept answer" and "Upvote it".
Please sign in to rate this answer.
Ashish kumar Sharma 1 Reputation point

2024-10-09T19:45:37.26+00:00

Hi Thanks for replying.

My azure migrate appliance and user permission is working fine.

i am able to discovered servers, software inventory, Web inventory and SQL inventory.

My issue is discovered server not verified for Dependencies (Agentless).

getting error id 960. verification failing.

Pavan Minukuri 280 Reputation points Microsoft Vendor

2024-10-09T20:25:41.39+00:00

Hi Ashish kumar Sharma,
Thanks for replying.!
Ensure that the account you're using for discovery has administrator permissions on the source machines. For Windows VMs, the account needs to have local admin rights. For Linux VMs, the account must have root or sudo privileges. WMI or PowerShell Access Issues (for Windows VMs):

Azure Migrate uses WMI (Windows Management Instrumentation) to query installed software. If WMI is disabled or corrupted, the software inventory collection might fail. Fix: Ensure that the WMI service is running and that there are no issues with WMI on the target machine. Make sure that PowerShell Remoting is enabled and functional. SSH Configuration Issues (for Linux VMs):

For Linux machines, Azure Migrate uses SSH to collect software inventory. If the SSH service is not running or is misconfigured, software data collection will fail. Fix: Ensure that SSH is enabled and accessible from the Azure Migrate appliance. Firewall or Network Restrictions:

Possible Causes and Fixes:

Network Traffic Blocked:

The appliance needs to collect information about TCP traffic between machines. If network traffic is being blocked (e.g., by firewalls, security groups, or network policies), the appliance won't be able to collect this data. Fix: Ensure that network traffic between VMs, and between the VMs and the appliance, is not restricted. This is especially important for dependencies like port scanning and packet inspection. Agentless Limitations:

If the source machine's OS is unsupported or not configured properly for dependency collection, the agentless method may fail. Fix: Ensure the OS is supported for agentless dependency mapping, and if it's not, consider using the agent-based method.

Ensure the Azure Migrate appliance can communicate with the machines on required ports (e.g., TCP 135 for Windows WMI, TCP 22 for Linux SSH, and others depending on the setup). Check Permissions:

Ensure the user accounts have sufficient permissions: Windows: The account should have local admin rights. Linux: The account should have root/sudo access. Enable and Verify WMI or SSH:

For Windows machines, ensure that WMI is enabled and accessible.
For Linux machines, ensure SSH is running and properly configured.

If you have any further queries, do let us know.

If the answer is helpful, please click "Accept answer" and "Upvote it".

Ashish kumar Sharma 1 Reputation point

2024-10-10T10:09:52.2+00:00

Hi

my account has domain admin rights and added into local administrators group.

able to telnet and communicate over 135 Port, windows firewall and antivirus allow traffic from appliance and vice verca, some server able verify (like sql and web) but my 80% server has the verification failed on dependency data

Pavan Minukuri 280 Reputation points Microsoft Vendor

2024-10-10T19:30:43.35+00:00

Hi
I’ll walk you through the steps
You are working with an appliance or system that verifies servers using port 135 for RPC, but many servers are failing verification.

Here are some things to check:

RPC Dynamic Ports: Besides port 135, RPC uses a range of ports (49152–65535). Ensure this range is allowed in the firewall or restrict it in the registry under HKEY_LOCAL_MACHINE\Software\Microsoft\Rpc\Internet.

DCOM Permissions: Check that DCOM is enabled and your account has access permissions in Component Services (dcomcnfg).

WMI: Test WMI with wbemtest by connecting to \localhost\root\cimv2 and running queries like SELECT * FROM Win32_OperatingSystem.

Firewall Rules: Ensure firewall rules allow RPC and WMI traffic on failing servers.

Antivirus: Check if antivirus or security software is blocking RPC or DCOM connections.

Required Services: Make sure services like RPC, WMI, and DCOM Server Process Launcher are running.

Network Segmentation: Confirm network paths, firewalls, and VLANs don’t block communication for the failing servers.

If the answer helpful, please click "Accept Answer" and "Upvote it"

Pavan Minukuri 280 Reputation points Microsoft Vendor

2024-10-11T16:40:09.25+00:00

Hi Ashish kumar Sharma,
If you had a chance to see my comment to your question.
If it was helpful, please click "Upvote" on my post let us know.
Thank you...!

Pavan Minukuri 280 Reputation points Microsoft Vendor

2024-10-14T13:36:57.5133333+00:00

Hi Ashish kumar Sharma,
If you had a chance to see my comment to your question.
If it was helpful, please click "Upvote" on my post let us know.
Thank you...!

Ashish kumar Sharma 1 Reputation point

2024-10-14T14:04:11.5266667+00:00

do i need test mentioned service and dcom thing on appliance serve or source server?

Pavan Minukuri 280 Reputation points Microsoft Vendor

2024-10-14T17:13:27.6766667+00:00

Hi Ashish kumar Sharma,
You can test in Source Server.
If you facing any challenges let me know.
Thank you...!
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

How to do i fix Error ID 960 of dependency varification failed in azure migrate

1 answer

Your answer