Bad Password: Kerberos Error: WinRM cannot process the request

  • 7019407
  • 04-Jun-2015
  • 01-Sep-2017


Migration Toolkit 2.1


A customer with this error found that the error came up because the password they were using had a '$' in it. Using  '-' and '_' appear to work.

Using User Migrator, the migration fails with the error:
WinRM cannot process the request. The following error with errorcode 0x80090311 occurred while using Kerberos authentication: There are currently no logon servers available to service the logon request.
 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.


The User Migrator uses PowerShell to connect with Exchange, and Powershell has certain reserved characters including:

     $     ()     *     +     .     []     ?     \     /     ^     {}     |

It is recommended that you use an alphanumeric password that avoids those characters.

See Also:
Hey, Scripting Guy! How Can I Use Windows PowerShell to Replace Characters in a Text File?

Additional Information

This article was originally published in the GWAVA knowledgebase as article ID 2559.