Home / server / Questions / 1018893
In Process
prd
Asked: 2020-05-28 02:08:30 +0800 CST

Windows Admin Center cannot connect to destination

  • 772

I am pulling my hair on this.. Can't seem to point a finger at where it went wrong. All error messages are cryptic, and leads to wrong problem.

I have just installed Windows admin Center to one of my server. I already have PS Remoting working for sometimes, and I can enter my servers using enter-pssession.

After installation, I tried to connect to the computer where I installed the Windows Admin Center and greeted with this screen.

Wrong Password

Then I scoured Event Viewer, and found this one

400 - CimException: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". Stack trace:
at Microsoft.Management.Infrastructure.Internal.Operations.CimAsyncObserverProxyBase1.ProcessNativeCallback(OperationCallbackProcessingContext callbackProcessingContext, T currentItem, Boolean moreResults, MiResult operationResult, String errorMessage, InstanceHandle errorDetailsHandle) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.Cim.CimProxy.<>c__DisplayClass7_0.<<Query>b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.Cim.CimProxy.<>c__DisplayClass22_01.<b__0>d.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.Security.ImpersonationManager.d__01.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.Cim.CimProxy.<RunInCimSession>d__221.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.Cim.CimProxy.d__7.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.FrontEnd.Controllers.FeatureController.d__14.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Threading.Tasks.TaskHelpersExtensions.d__3`1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Microsoft.ManagementExperience.FrontEnd.Handlers.ImpersonationActionInvoker.d__1.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Dispatcher.HttpControllerDispatcher.d__1.MoveNext()

So I checked my WinRM service, and found out it is indeed, running WinRM Check

and accepting conneections. Invoke commands is also working properly

Powershell Connection

The rdp server that I was trying to connect, is the one hosting Windows Admin Center. So it is basically logging in into localhost. The system is freshly installed, and is connected to active directory.

Any idea on where it went wrong? Thank you

windows-admin-center windows-server-2019

2 Answers

  1. Ok.. It is solved.

    Remove the Windows Admin Center, and reinstall it. This time, remove the checkmark from WinRM https.

    • 2

  2. Apart from the other answer, try running this commands in Administrator PowerShell window in your server, to get sure everything is well setup:

    winrm qc Enable-psremoting

    And there is another reason that can be tricky: get sure that both the server and the WAC machine have the correct date and time. If there is a mismatch, it can avoid the connection.

    NOTE: the firewall, by default, allows connections only from the same subnet.

    • 0