Azure Migration Appliance error during discovery on hyper-v.

Ralda, Jason 1 Reputation point
2022-03-15T16:51:56.07+00:00

I am not sure where to look or what is causing the issue, have verified all user names and passwords.

Error ID
60001
Error message
Unable to connect to server 'Xxxxxx' due to an error. Error code: '' Error details: 'Unable to connect to this machine. The error per IP is: [IP: xxx.xxx.xxx.20, Error:Unable to connect to server 'xxx.xxx.xxx.20' due to an error. Error code: '-2146233087' Error details: 'Connecting to remote server xxx.xxx.xxx.20 failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030d occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated.
Possible causes are:
-The user name or password specified are invalid.
-Kerberos is used when no authentication method and no user name are specified.
-Kerberos accepts domain user names, but not local user names.
-The Service Principal Name (SPN) for the remote computer name and port does not exist.
-The client and remote computers are in different domains and there is no trust between the two domains.
After checking for the above issues, try the following:
-Check the Event Viewer for events related to authentication.
-Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.
Note that computers in the TrustedHosts list might not be authenticated.
-For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.'.] [IP: fe80::1db:d801:xxxx:xxxx, Error:Unable to connect to server 'fe80::1db:d801:xxxx:xxxx' due to an error. Error code: '-2146233087' Error details: 'Connecting to remote server [fe80::1db:d801:6a97:xxxx] failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030d occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated.
Possible causes are:
-The user name or password specified are invalid.
-Kerberos is used when no authentication method and no user name are specified.
-Kerberos accepts domain user names, but not local user names.
-The Service Principal Name (SPN) for the remote computer name and port does not exist.
-The client and remote computers are in different domains and there is no trust between the two domains.
After checking for the above issues, try the following:
-Check the Event Viewer for events related to authentication.
-Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport.
Note that computers in the TrustedHosts list might not be authenticated.
-For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic.'.] '.

Azure Migrate
Azure Migrate
A central hub of Azure cloud migration services and tools to discover, assess, and migrate workloads to the cloud.
928 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Manu Philip 20,206 Reputation points MVP Volunteer Moderator
    2022-03-15T18:39:21.327+00:00

    I have seen that the error include the following message
    The following error with errorcode 0x8009030d occurred while using Negotiate authentication

    This error basically shows that, 'TrustedHost' parameter is not configured for authenticating the computer. Try to set it on the computer shows the error message as below

    Set-Item -Path WSMan:\localhost\Client\TrustedHosts -Value 'ComputerName1,ComputerName2'
    

    You may use wildcard character (*) to specify multiple computers also


    --please don't forget to upvote and Accept as answer if the reply is helpful--

    1 person found this answer helpful.

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.