none
Windows 10 Feature Update 1903 disables Essentials Connector RRS feed

  • Question

  • I have begun testing the Windows 10, version 1903 Feature update.  In the three clients on which I installed the update, they were unable thereafter to connect to the Essentials Server.  The only way I was able to resolve the issue was to manually uninstall and reinstall the connector. 
    Friday, June 7, 2019 2:32 PM

All replies

  • Same issue on 3 clients (100%) so far
    Friday, June 7, 2019 5:13 PM
  • This began to be reported more than a month ago (https://social.technet.microsoft.com/Forums/windowsserver/en-US/044c29e5-7b0e-4241-803f-0cdcbe27db97/win-10-1903-clients-not-visible-in-ws2012r2-essentials?forum=winserveressentials) but follow up appears to die if the original poster does not pursue it.

    In my case, uninstalling and reinstalling the connector (Programs and Features, select, Uninstall) doesn't work, since immediately after entering login credentials into the connector during setup I get "The server is not available. Try connecting this computer again."

    BackupLaunchpad.log (affected):

    =====

    [16336] 190530.202751.5574: BackupLaunchpad: Program.Main(): BackupLaunchpad started
    [16336] 190530.202751.6194: General: Initializing...C:\Program Files\Windows Server\Bin\BackupLaunchpad.exe
    [16336] 190530.202751.6664: General: Color branding started
    [16336] 190530.202751.6664: General: Processing Microsoft default SKU branding colors XML
    [16336] 190530.202751.6784: General: Branding colors XML parsing started
    [16336] 190530.202751.6824: General: Branding colors XML parsing ended
    [16336] 190530.202751.6824: General: Looking for OEM branding colors XML
    [16336] 190530.202751.6824: General: No OEM informations available
    [16336] 190530.202751.6824: General: Color branding complete
    [16336] 190530.202751.7404: BackupLaunchpad: BackupLaunchpadControl constructed
    [16336] 190530.202751.7454: BackupLaunchpad: BackupDisconnectedControl constructed
    [16336] 190530.202751.7474: Backup: Trying to connect to provider Async.
    [16336] 190530.202751.7474: BackupLaunchpad: BackupLaunchpadProperties: constructed form
    [1676] 190530.202751.7524: Backup: Waiting for connection with the provider.
    [1676] 190530.202851.7548: Backup: Timeout waiting for connection : System.TimeoutException: Timeout occurred waiting for connection to complete.  Connection attempt is still in progress.
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.ThreadWaitHolder.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1.WaitForConnection(TimeSpan duration)
       at Microsoft.WindowsServerSolutions.DataProtection.PCBackup.ObjectModel.PCBackupClientManager.Connect()
    [16336] 190530.202917.6882: BackupLaunchpad: Program.Main(): BackupLaunchpad ending

    =====

    Launchpad.log (affected):

    =====

    [2364] 190530.205309.8116: ServerDiscoveryObjectModel:Backend: Connect: Calling Connector.Connect()
    [2364] 190530.205329.8124: ServerConnectivityStatus: Cannot connect to ServerPresenceProvider: System.TimeoutException: Timeout occurred waiting for connection to complete.  Connection attempt is still in progress.
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.ThreadWaitHolder.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.internal.ConnectorInternals.TimeoutWait`1.WaitForTimeout(TimeSpan duration, ProviderConnector`1 providerConnector)
       at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderConnector`1.WaitForConnection(TimeSpan duration)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.ProviderBackendBase`1.Connect(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.ServerDiscoveryObjectModelBase`1.Connect(TimeSpan timeout)
       at Microsoft.WindowsServerSolutions.LaunchPad.ServerConnectivityStatus.connectWorker_DoWork(Object sender, DoWorkEventArgs e)
    [2364] 190530.205329.8124: General: _isNewState changed: False

    =====

    ClientDeploy.log (affected, same machine after in-place update to 1903, during reinstallation of client connector):

    =====

    [6932] 190601.112427.8757: ClientSetup: Cannot get configuration file with https, will try http...
    [6932] 190601.112427.8767: ClientSetup: Download file Setup.cab from server
    [6932] 190601.112427.8767: ClientSetup: Making web request: http://192.168.0.2//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [6932] 190601.112427.9938: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [6932] 190601.112427.9938: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [6932] 190601.112428.0688: ClientSetup: Adding Server Info data in the Product Registry
    [6932] 190601.112428.0921: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.0.2, normal environment
    [6932] 190601.112428.0941: ClientSetup: Exiting PreConfigTask.Run()
    [6932] 190601.112428.0941: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
    [6932] 190601.112428.0941: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
    [6932] 190601.112428.0941: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3520: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [6932] 190601.112434.3520: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3520: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [6932] 190601.112434.3740: ClientSetup: Entering InstallRootCertTask.Run
    [6932] 190601.112434.3770: ClientSetup: Install root cert to local trusted store
    [6932] 190601.112434.3830: ClientSetup: Exiting InstallRootCertTask.Run
    [6932] 190601.112434.3830: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [6932] 190601.112434.3830: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [6932] 190601.112434.3830: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3830: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [6932] 190601.112434.3830: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6932] 190601.112434.3830: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [6932] 190601.112434.4190: ClientSetup: Entering SetupVpnAndDATask.Run
    [6932] 190601.112434.4260: ClientSetup: Deploy VPN profile
    [6932] 190601.112434.4480: ClientSetup: Exting SetupVpnAndDATask.Run
    [6932] 190601.112434.4490: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
    [6932] 190601.112434.4490: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [6932] 190601.112434.4490: ClientSetup: Exiting ConnectorWizardForm.RunTasks
    [6932] 190601.112434.4490: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [6932] 190601.112434.4490: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [6932] 190601.112434.4490: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [6932] 190601.112434.4750: ClientSetup: Entering ValidateUserTask.Run
    [6932] 190601.112434.4750: ClientSetup: Validating User
    [6932] 190601.112434.4760: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [6932] 190601.112434.5060: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5070: General: Failed to open IDENTITY registry key.
    [6932] 190601.112434.5251: General: Failed to open IDENTITY registry key.
    [6932] 190601.112534.9557: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1
    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus
       at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
    [6932] 190601.112534.9567: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\ipconfig.exe"  /all
    [10068] 190601.112534.9847: ClientSetup: Standard Ouptput: 

    [redacted]

    =====

    BackupLaunchpad.log (same machine, Windows 10 1809 prior to in-place update to 1903):

    =====

    [2264] 190427.110129.7687: BackupLaunchpad: Program.Main(): BackupLaunchpad started
    [2264] 190427.110129.8357: General: Initializing...C:\Program Files\Windows Server\Bin\BackupLaunchpad.exe
    [2264] 190427.110129.9207: General: Color branding started
    [2264] 190427.110129.9207: General: Processing Microsoft default SKU branding colors XML
    [2264] 190427.110129.9317: General: Branding colors XML parsing started
    [2264] 190427.110129.9367: General: Branding colors XML parsing ended
    [2264] 190427.110129.9367: General: Looking for OEM branding colors XML
    [2264] 190427.110129.9367: General: No OEM informations available
    [2264] 190427.110129.9367: General: Color branding complete
    [2264] 190427.110130.1077: BackupLaunchpad: BackupLaunchpadControl constructed
    [2264] 190427.110130.1128: BackupLaunchpad: BackupDisconnectedControl constructed
    [2264] 190427.110130.1137: Backup: Trying to connect to provider Async.
    [2264] 190427.110130.1147: BackupLaunchpad: BackupLaunchpadProperties: constructed form
    [8] 190427.110130.1187: Backup: Waiting for connection with the provider.
    [1344] 190427.110135.2064: Backup: New connection detected. Try fetching all data
    [1344] 190427.110135.2304: Backup: Connected to provider Successfully
    [2264] 190427.110135.2304: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2314: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2314: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2314: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2314: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2324: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2324: BackupLaunchpad: Synchronized state
    [2264] 190427.110135.2394: BackupLaunchpad: Updated status to success
    [2264] 190427.110135.2394: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110135.2394: BackupLaunchpad: Synchronized state
    [2264] 190427.110143.6196: BackupLaunchpad: Updated status to starting
    [2264] 190427.110143.8923: BackupLaunchpad: BackupLaunchpadControl.backupObjectModel_StartBackupAsyncCompletedEvent: StartBackupAsync ended
    [2264] 190427.110143.8933: BackupLaunchpad: Updated status to success
    [2264] 190427.110143.8933: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Success and error None
    [2264] 190427.110143.9043: BackupLaunchpad: Updated status to progress 1

    ...

    =====



    Sunday, June 9, 2019 12:17 PM
  • Hi,

    In general, for system upgrade, it is recommended to un-install connector before upgrading and re-install connector to connect to WSE later.

    As you had mentioned that, system feature upgrade causing connection problem and re-install connector resolves the problem. If possible, please provide more detail information and I will test on my VM.
    1. Windows Server Essentials and client system before upgrade:
    Run “winver” on Windows Server Essentilas, provide me the detail OS version and build number.
    2. Detail error message or phenomenon about the failure connection from client to WSE.

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 10, 2019 8:06 AM
    Moderator
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang     

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 12, 2019 2:30 AM
    Moderator
  • The issue is unchanged.  There are numerous posts on this site describing Windows 10 feature upgrades disabling the Essentials Connector.  Apparently, the connector will have to be uninstalled and reinstalled on each client.  Sad, but true...
    Wednesday, June 12, 2019 2:24 PM
  • Hi,

    Thank you for taking the time to share the details, I will try to reproduce it on my test environment.

    Also, as you mentioned that multi users and devices meet such problem, I will post such feedback to product team. Also, in general, as customer you can post such feedback via Windows Server General Feedback Forum:
    https://windowsserver.uservoice.com/forums/295047-general-feedback

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, June 13, 2019 3:26 AM
    Moderator
  • I'm experiencing this issue with all my customers as well. The previous trick to flush DNS or restarting the PC a few times for connector to come alive again in the dashboard no longer works. As mentioned in this string, completely uninstalling the reinstalling the connector is the only solution at this time.

    Pete


    • Edited by pperry803 Saturday, June 15, 2019 8:20 PM
    Thursday, June 13, 2019 4:05 AM
  • Damn, I wish I had seen this BEFORE upgrading my clients to WIN10 v 1903.  I also installed KB4103712 to the server.  I am running WHS2011. Each major WIN10 client update has messed up the client connector.  This time, neither my server nor my clients can use the connector system to link--all report the others appear to be offline.
    Wednesday, June 19, 2019 12:31 PM
  • You have to go into the programs and features on each client/uninstall the connector and reinstall it.
    Thursday, June 20, 2019 3:49 PM
  • Eve,

    Come on now.  The Windows Server Essentials Connector for Windows Server 2012 R2 has been a problem for a long time and MSFT needs to upgrade the priority on an appropriate fix.  In my system I have one client on which I always have to re-install the connector using xxserver/Connect every time I install updates on the offending client.  After a major feature update ControlPanel/Programs and Features does not show Windows Essential installed, so I do it manually.  That has worked in the past, but with upgrade to Windows 10 1903 it does not work.  When executing Connect, all goes well until the end.  Then the program stops after the last step and I never get to Finish.  The Server has all of the current updates.

    On this offending client almost every update causes the Essentials application to be deleted.  Other clients do not have this problem.

    John

    Wednesday, July 10, 2019 9:22 PM
  • I'm having the same problem. WSE 2012 R2 on the server, Windows 10 build 1903 on three clients.

    But I can't even reinstall the Connector--when I get to the WSE Connector Configuration Wizard, it says "This server is not available. Try connecting this computer again."

    I've also tried downloading Connector from the Microsoft Download Center, but that install quits before it gets to the configuration wizard.

    I'm open to suggestions.

    Saturday, July 13, 2019 11:31 PM
  • Not sure your problem is the same as mine, but I have solved mine.  My solution was to uninstall the Connector first.  Earlier I had gone into Control Panel/Programs and Features and looked for something that began with Windows Server Essentials...  I knew it should be uninstalled first, but there was nothing there.  Then I found the name of the Connector application is “Client Connector for Windows Server Essentials”.  That seems a poor choice for the name.  Anyway I uninstalled that and then the new Connect feature worked.  It is very annoying that MSFT Windows 10 updates screws this up to begin with.  This ought to be a solvable problem and MSFT needs to fix it in the future.  It appears the Windows 10 people are not talking with the Server people.
    Saturday, July 13, 2019 11:58 PM