How can we improve the management tools and experience in Windows Server?

← Management Tools

[BUG] Import connections crash the WAC

Upgraded to Windows Admin Center 1910 and imported connections using the Import-Connection powershell module.

WAC will no longer load with error

500 - ArgumentException: An item with the same key has already been added.
Stack trace: at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary2.Insert(TKey key, TValue value, Boolean add)
at Microsoft.ManagementExperience.FrontEnd.Controllers.NodeController.GetConnections()
at lambda_method(Closure , Object , Object[] )
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters)
at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary2 arguments, CancellationToken cancellationToken)
--- 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.<InvokeActionAsyncCore>d0.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.<InvokeActionAsync>d1.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.<ExecuteAsync>d2.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.<SendAsync>d1.MoveNext()

Running WAC in HA on Windows Server 2019. Upgraded using the MSFT powershell script for HA installation etc.

Checked import CSV and there were no duplicate servers in the file.

9 votes
Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close

We’ll send you updates on this idea

GM shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

6 comments

Sign in
(thinking…)
Sign in with: Facebook Google
Forgot password?
Create a password
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Mark Daniel commented  ·   ·  Flag as inappropriate

    Update on that: nope, it keeps crashing the same way every day. At this point I'm about ready to toss in the towel on WAC, at least for the time being. Keeping it functional after importing a carefully groomed CSV file shouldn't be a struggle.

  • Mark Daniel commented  ·   ·  Flag as inappropriate

    OK, I've had "success" on this one, as I was plagued with it as well. It's not perfect: you lose your server list, but at least you do NOT have to re-install and re-configure the service (ports, cert, etc.). Once done, you'll need to re-attached to Azure (you can re-connect to your existing App registration), sign in to Azure, and re-import your servers.
    1. Stop the WAC service.
    2. Delete all files in C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\ServerManagementExperience *except for the JRS files*, as well as everything BUT the JRS files in TableStorage.
    3. Re-start the WAC service, log in and re-configure.

    Good luck!

  • James Iversen commented  ·   ·  Flag as inappropriate

    I was excited to "show it off" after Ignite... Now I have egg on my face. WAC failing all over the place on every machine I try to touch. From regular workstation, stuck at Initializing application screen, from red forest DA workstation WRM errors to all devices including local host... Way to make an impression guys. I know it was working before Ignite.

  • AS commented  ·   ·  Flag as inappropriate

    Same issue here. After reseting the content of the folder "C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\ServerManagementExperience" it works until we click on a server connection. After that it stays working until we relaunch the browser.

  • Ben commented  ·   ·  Flag as inappropriate

    We are also encountering this issue. Upgraded from 1904.1 (and have since done a clean install). Shortly after importing a list of connections using Import-Connections from ConnectionTools.psm1 we've found that if we fully refresh the page, we get:

    msft.sme.shell -- ConnectionManager
    message: Couldn't retrieve saved server list:An item with the same key has already been added..

    HTTP500: SERVER ERROR - The server encountered an unexpected condition that prevented it from fulfilling the request.
    (XHR)GET - https://wac.{{DOMAIN}}.com/api/connections

    The only fix that I've found is to uninstall WAC completely and then delete "C:\Windows\ServiceProfiles\NetworkService\AppData\Roaming\Microsoft\ServerManagementExperience"

    Mode: Gateway
    Gateway OS: Windows 2016
    Applied Hotfixes: KB3199986,KB4132216,KB4465659,KB4485447,KB4498947,KB4503537,KB4509091,KB4512574,KB4524152
    Browsers Used: Chrome, Firefox, Edge
    Connections list contains approximately 80 entries. Confirmed there are no duplicate entries. All connections are Windows Servers (2012R2, 2016 or 2019)

Management Tools: Windows Admin Center

Categories

Feedback and Knowledge Base

(thinking…)