none
Win 10 1903 Clients not visible in WS2012R2 Essentials RRS feed

  • Question

  • Hi,

    I updated my laptop to Win 1903 and it has become invisible to my WS2012R2 Essentials home server. The client is not on a domain.

    Since the update, it is impossible to backup the client: it fails with "cannot connect to the WS Essentials Client Computer Management Service."

    I have tried uninstalling and reinstalling the connector on the client. The reinstallation fails. I manage to log on, it complains that the client already exists on the server (which is true, is evidence that it connects to the server and is ok) and when I continue, it fails with not possible to connect to server. 

    Is anyone else seeing this?

    Monday, April 29, 2019 9:22 AM

All replies

  • Hi,

    As far as I know, Windows 10 1903 is still a inside preview version new.

    About the problem of connector installation, please check below steps to clear stable files and try to install again to check the result.

    Back up system and important data before any change first. 

    On Windows 10:
    1. Manually uninstall WSE connector via “Control Panel\All Control Panel Items\Programs and Features”.
    2. Delete “Windows Server” folder under “%ProgramData%\Microsoft\”.
    3. Delete “Windows Server Essentials” folder under “Task Scheduler – Task Scheduler Library – Microsoft – Windows”.
    4. Open TCP/IP properties, manually assign WSE’s IP address as its Preferred DNS server.
    5. Re-star the client system, log on with local admin account and try to reconnect again to check the result.

    If problem persists, please provide log files – Computerconnector.log andClientDeploy.log, which are located on “%programdata%\Microsoft\Windows Server\Logs\” on the client. You may upload the log files to OneDrive(https://onedrive.live.com/), share them and provide me the access link.

    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.

    Tuesday, April 30, 2019 8:27 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.

    • Proposed as answer by ldwhyte Friday, July 19, 2019 9:54 PM
    Monday, May 6, 2019 12:56 AM
    Moderator
  • Different person here - but exact same problem! I did the steps you said and still have the same problem. Attached is my ClientDeploy.log link:
    https://1drv.ms/u/s!AhWrgXCDAUptodYFKsGJ3wMeYZWQ_A

    Tuesday, May 7, 2019 12:44 AM
  • Hi,


    @4xMeister
    > UnKnown can't find WINHOMESERVER: Server failed
    Based on the log file, client failed to find the WSE as it failed to resolve the DNS name of server.

    On client:
    Please disable other network adapter on client system and only leave one to be active. Besides, I want to confirm with you if the “DNS Servers : 192.168.0.100” you internal DNS server or WSE? Using NSlookup to confirm that if your client system can successfully resolve the WSE.

    Try to disable IPv6 temporarily.

    @Wigster

    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.

    Friday, May 10, 2019 1:51 AM
    Moderator
  • Hi,

    192.168.0.100 is my WSE. NSLookup CAN succesfully resolve the WSE.

    I disabled IPv6 & disabled all network adapters except for one (my main Ethernet connection).

    The Connector finds the WSE almost immediately before asking for Username and Password. But, after entering username and password it can never find the WSE again.

    Here is the link to my two log files.

    https://1drv.ms/f/s!AhWrgXCDAUptoegsmgOA4oXCdClgPw

    Thank you for your help!!

    Tuesday, May 14, 2019 3:39 PM
  • To clarify NSLookup:

    When I put at the command prompt, just

    ---------------

    >NSLookup

    Default Server: UnKnown

    Address: 192.168.0.1

    -------------

    192.168.0.1 is my client computer address that I'm trying to install the client connector on.

    Wednesday, May 15, 2019 10:56 PM
  • >NSLookup 192.168.0.100

    Server: [192.168.0.100]

    Address: 192.168.0.100

    Wednesday, May 15, 2019 10:58 PM
  • Ok, multiple people are experiencing this issue*, it is a result of the feature update to Windows 10 1903 only, and it has nothing to do with the computerconnector.log and clientdeploy.log content, since those files are not updated after a successful client connector installation, e.g., mine have not been touched since November 2017.

    Symptoms are as follows:

    1.  Taskbar icon is green and shows connected to server

    2.  Launchpad shows flag in bottom left that says that the server is offline

    3.  All clients not updated to 1903 still connect and backup to the server normally

    4.  Network shares and RDP to the server work as expected

    5.  Net.tcp service is running and error occurs whether the Windows Defender firewall is active or disabled

    The relevant log that is updated during an attempted backup operation from the client Launchpad reports the following:

    =====

    [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

    =====

    The other one that updates is the Launchpad.log as follows:

    =====

    [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

    =====

    No other log updates on the client side.

    *https://homeservershow.com/forums/topic/17155-server-not-seeing-client-runnign-new-windows-1903/

    https://www.petri.com/forums/topic/ws2012r2-essentials-does-not-see-windows-1903-machine

    https://www.reddit.com/r/WindowsServer/comments/bejcom/ws2012r2_essentials_does_not_see_windows_1903/



    Friday, May 31, 2019 12:55 AM
  • For good measure here's Backuplaunchpad.log from the same machine prior to 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

    ...

    =====



    Friday, May 31, 2019 1:16 AM
  • Hi,

    [12644] 190514.083439.4658: ClientSetup: Standard Error: *** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for WINHOMESERVER
    [12644] 190514.083439.4658: ClientSetup: Standard Error: 
    [32516] 190514.083439.4658: ClientSetup: Standard Ouptput: Server:  UnKnown
    [32516] 190514.083439.4658: ClientSetup: Standard Ouptput: Address:  192.168.0.1

    I want to confirm with you if WINHOMESERVER is your WSE server name? If WSE is your DNS server which used to internal name resolution, please open DNS zone and confirm that your WSE has appropriate A record on the zone. 

    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:10 AM
    Moderator
  • Same issue here. Updated two win10 VM's to 1903 and they are now no longer visible to WSE 2016 server. I can still RDP from the web but they show up as grayed out in the device list. Also reports from WSE seem to be frozen in time for those machine "machine requires reboot from updates" though it's been rebooted and updated several times since that started. 
    Sunday, June 16, 2019 4:17 AM
  • Hi,

    WINHOMESERVER is the name of my WSE Server.

    I verified that an A record exists in the DNS Zone on the server. (in this case WINHOMESERVER A record is 192.168.0.100)

    One thing is when I run the Client Connector, it does NOT let me input the Server name at the beginning. It automatically grabs WINHOMESERVER and continues. Maybe if there was a way to have the client connector let me input the server name, I could try putting in 192.168.0.100 (the IP of the WSE) instead and see if that helps?

    Again, all of this only started once I upgraded from Win 10 1809 to 1903 on the client computer.

    Sunday, June 16, 2019 6:05 PM
  • It nukes the services off the pcs.  You have to go into the control panel, programs and features, look for Client connector for Windows Server Essentials and uninstall the connector.  Now reinstall it and it will join back up.  Ever feature release something happens to this connector software.
    Monday, June 17, 2019 11:32 PM
  • Sorry, tried that countless times. The uninstall, reinstall. That method worked in the past, but it doesn't work to fix the problem with Release 1903.
    Thursday, June 20, 2019 3:06 AM
  • It did for me.  What exact essentials version are you using?  I uninstalled the connector from the clients, and then reinstalled it.  Otherwise what's going on in the log file on the client side?
    Thursday, June 20, 2019 4:02 PM
  • Using Server Essentials 2016 with all update applied.

    [12644] 190514.083439.4658: ClientSetup: Standard Error: *** No internal type for both IPv4 and IPv6 Addresses (A+AAAA) records available for WINHOMESERVER
    [12644] 190514.083439.4658: ClientSetup: Standard Error: 
    [32516] 190514.083439.4658: ClientSetup: Standard Ouptput: Server:  UnKnown
    [32516] 190514.083439.4658: ClientSetup: Standard Ouptput: Address:  192.168.0.1

    Thursday, June 20, 2019 7:17 PM
  • What do you have set for the DNS entries on the server and client?
    Friday, June 21, 2019 9:10 PM
  • Here is the excerpt from my clientdeploy.log file showing that it appears to be an SSL Certificate Trust Error:

    [8304] 190624.181542.3013: ClientSetup: Making web request: https://192.168.0.100//connect/default.aspx?Get=Setup.cab&LanguageId=1033&64bit=1
    [8304] 190624.181542.3313: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. ---> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

    Tuesday, June 25, 2019 1:23 AM
  • Further down, it does show it downloads setup.cab succesfully via HTTP.

    But, here is the next error further down in clientdeploy.log:

    8304] 190624.181544.7586: Networking:DnsEnvironmentDetector: Dns.GetHostAddresses threw exception: System.Net.Sockets.SocketException (0x80004005): This is usually a temporary error during hostname resolution and means that the local server did not receive a response from an authoritative server
       at System.Net.Dns.GetAddrInfo(String name)
       at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
       at System.Net.Dns.GetHostAddresses(String hostNameOrAddress)
       at Microsoft.WindowsServerSolutions.Networking.ServerDiscovery.DnsEnvironmentDetector.GetAddressesFromDns(String machine)
    [8304] 190624.181544.7586: DnsEnvironmentDetector: No result from GetHostAddresses(), normal environment
    [8304] 190624.181544.7646: ClientSetup: SkipDomainJoin hook is set, skip domain join

    Tuesday, June 25, 2019 1:24 AM
  • Tuesday, June 25, 2019 5:27 PM
  • Everything came back 'OK' using the tool.
    Wednesday, June 26, 2019 12:04 AM
  • Can you attempt to install the client connector and post up the entire client deploy log as a link in here?
    Friday, June 28, 2019 4:11 AM
  • Have you already tried to disable VPN in the Dashboard-Settings?

    You can do this under settings, access anywhere, configure, uncheck VPN.

    In earlier versions this prevented the connector from installing.
    Mine just installed fine after disabling vpn (Server 2016, Windows 10 Pro 1903 as Client).

    After this you could reenable VPN in the settings.

    Friday, June 28, 2019 2:04 PM
  • VPN has always been Disabled in the Dashboard. I've never enabled it. And I verified that it is Disabled. :-(

    Friday, June 28, 2019 11:30 PM
  • Here is a link to my ClientDeploy.log & Computerconnector.log

    Logs

    https://1drv.ms/f/s!AhWrgXCDAUptoegsmgOA4oXCdClgPw

    Thank you for your help thus far!

    Friday, June 28, 2019 11:33 PM
  • Hi,

    WINHOMESERVER is the name of my WSE Server.

    I verified that an A record exists in the DNS Zone on the server. (in this case WINHOMESERVER A record is 192.168.0.100)

    One thing is when I run the Client Connector, it does NOT let me input the Server name at the beginning. It automatically grabs WINHOMESERVER and continues. Maybe if there was a way to have the client connector let me input the server name, I could try putting in 192.168.0.100 (the IP of the WSE) instead and see if that helps?

    Again, all of this only started once I upgraded from Win 10 1809 to 1903 on the client computer.

    Thursday, July 4, 2019 10:48 PM
  • But you can tell from looking at the log that it's talking to 192.168.1.100.  The fact that it's picking up the name of the home server means it's talking to it.

    http://blog.korteksolutions.com/cannot-connect-this-computer-to-the-network-windows-sbs-2011-essentials/

    See if restarting those services in that blog helps?

    Sunday, July 7, 2019 5:40 AM
  • Susan,

    Thank you for the link to the article. The thing is, those services and suggestions in that article all relate to things being done on the Server Essentials side.

    I have a number of systems - all running Windows 10 v1809 and they have no problem connecting to the server. I've also tried uninstalling and reinstalling the connector on a few of those systems and it works fine.

    It worked fine on my system until I did the update from Win10 v1809 to Win 10 v1903 - so the problem is obviously with my system, not the server.

    Sunday, July 7, 2019 6:45 AM
  • I have the same problem. I can't afford systems not to have backups. When is this going to be fixed?
    Thursday, July 11, 2019 3:19 AM
  • I have the exact same problem.  Hope MSFT has been informed of this problem in 1903 since it is being distributed widely now.

    John

    Thursday, July 11, 2019 5:57 PM
  • [Original poster here] I've finally got around to trying to fix this. I have a client with 1903 18362.239 and a fully patched WS2012R2 Essentials, in case it's a recent patch that helped. Partial Success. 

    I've applied all the suggestions mentioned here and have been successful. made the connector connect. Not sure which part was necessary and which was not, since I did everything at once.

    1. Uninstalled WSE connector via Control Panel
    2. Deleted “Windows Server” folder under “%ProgramData%\Microsoft\”.
    3. Deleted “Windows Server Essentials” folder under “Task Scheduler – Task Scheduler Library – Microsoft – Windows”.
    4. Manually assigned WSE’s IP address as the client's Preferred DNS server.
    5. Switched VPN off from Access Anywhere in the Essentials Dashboard
    6. Rebooted and installed the Connector

    This allowed the Connector to find the server and connect. However, it still complained that a client with the same name was already connected to the server and the login credentials were not appropriate. I thus archived the backup of this client through the Essentials Dashboard and completed the installation with Essential treating my client as a new machine. This is not good, but better than nothing.

    So now, I have a client which has never been backed up as far as the server is concerned. It is detected as online by the Dashboard when connected to the server's network. And I can start a backup.

    However the backup always fails eventually. It seems to happen at a random moment between 2 and 8% complete. 

    This is what BackupLaunchpad.log looks like:

    ---------------------------------------------------------
    [20448] 190714.155808.1005: BackupLaunchpad: Program.Main(): BackupLaunchpad started
    [20448] 190714.155808.1786: General: Initializing...C:\Program Files\Windows Server\Bin\BackupLaunchpad.exe
    [20448] 190714.155808.2505: General: Color branding started
    [20448] 190714.155808.2505: General: Processing Microsoft default SKU branding colors XML
    [20448] 190714.155808.2675: General: Branding colors XML parsing started
    [20448] 190714.155808.2715: General: Branding colors XML parsing ended
    [20448] 190714.155808.2715: General: Looking for OEM branding colors XML
    [20448] 190714.155808.2715: General: No OEM informations available
    [20448] 190714.155808.2715: General: Color branding complete
    [20448] 190714.155808.3655: BackupLaunchpad: BackupLaunchpadControl constructed
    [20448] 190714.155808.3705: BackupLaunchpad: BackupDisconnectedControl constructed
    [20448] 190714.155808.3715: Backup: Trying to connect to provider Async.
    [20448] 190714.155808.3725: BackupLaunchpad: BackupLaunchpadProperties: constructed form
    [15892] 190714.155808.3785: Backup: Waiting for connection with the provider.
    [13260] 190714.155813.5335: Backup: New connection detected. Try fetching all data
    [13260] 190714.155813.5685: Backup: Connected to provider Successfully
    [20448] 190714.155813.5695: BackupLaunchpad: Updated status to failed
    [20448] 190714.155813.5695: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error ConnectionLost
    [20448] 190714.155813.5705: BackupLaunchpad: Updated status to failed
    [20448] 190714.155813.5705: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error ConnectionLost
    [20448] 190714.155813.5715: BackupLaunchpad: Updated status to failed
    [20448] 190714.155813.5715: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error ConnectionLost
    [20448] 190714.155813.5715: BackupLaunchpad: Synchronized state
    [20448] 190714.155813.5895: BackupLaunchpad: Updated status to failed
    [20448] 190714.155813.5895: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error ConnectionLost
    [20448] 190714.155813.5895: BackupLaunchpad: Synchronized state
    [20448] 190714.155816.5795: BackupLaunchpad: Updated status to starting
    [20448] 190714.155828.3425: BackupLaunchpad: BackupLaunchpadControl.backupObjectModel_StartBackupAsyncCompletedEvent: StartBackupAsync ended
    [20448] 190714.155828.3466: BackupLaunchpad: Updated status to failed
    [20448] 190714.155828.3466: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error ConnectionLost
    [20448] 190714.155828.3615: BackupLaunchpad: Updated status to progress 1
    [20448] 190714.155828.3626: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.155828.3626: BackupLaunchpad: Updated status to progress 1
    [20448] 190714.155828.3626: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.155828.3691: BackupLaunchpad: Updated status to progress 1
    [20448] 190714.155828.3711: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160132.4883: BackupLaunchpad: Updated status to progress 1
    [20448] 190714.160132.4893: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160345.9867: BackupLaunchpad: Updated status to progress 2
    [20448] 190714.160345.9877: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160449.4252: BackupLaunchpad: Updated status to progress 3
    [20448] 190714.160449.4262: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160450.2494: BackupLaunchpad: Updated status to progress 4
    [20448] 190714.160450.2504: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160450.8973: BackupLaunchpad: Updated status to progress 5
    [20448] 190714.160450.8983: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160451.7983: BackupLaunchpad: Updated status to progress 6
    [20448] 190714.160451.7993: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160452.5943: BackupLaunchpad: Updated status to progress 7
    [20448] 190714.160452.5954: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.160522.6779: BackupLaunchpad: Updated status to progress 8
    [20448] 190714.160522.6789: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.161036.4249: BackupLaunchpad: Updated status to progress 9
    [20448] 190714.161036.4279: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.161409.2406: BackupLaunchpad: Updated status to progress 10
    [20448] 190714.161409.2416: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.161513.1045: BackupLaunchpad: Updated status to progress 11
    [20448] 190714.161513.1075: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.161515.7638: BackupLaunchpad: Updated status to progress 11
    [20448] 190714.161515.7678: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.161523.7599: BackupLaunchpad: Updated status to progress 11
    [20448] 190714.161523.7629: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status InProgress and error None
    [20448] 190714.161523.8029: BackupLaunchpad: Updated status to failed
    [20448] 190714.161523.8029: BackupLaunchpad: BackupLaunchpadControl.RefreshStatus(): completed and showing status Failed and error ConnectionLost
    [20448] 190714.161821.9074: BackupLaunchpad: Program.Main(): BackupLaunchpad ending

    And if I look in the EventViewer, this is the problems I seem to have having reported by VSS at 3:58 PM when the backup starts

    Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.
    . This is often caused by incorrect security settings in either the writer or requestor process. 
    
    Operation:
       Gathering Writer Data
    
    Context:
       Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
       Writer Name: System Writer
       Writer Instance ID: {49d8c06f-ee95-4c8d-a35a-8e4efdec74a9}

    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="VSS" /> 
      <EventID Qualifiers="0">8194</EventID> 
      <Level>2</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2019-07-14T13:58:32.349157700Z" /> 
      <EventRecordID>18218</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>Schizophrenic.CHAMBREDUPEINE.local</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data>0x80070005, Access is denied.</Data> 
      <Data>Operation: Gathering Writer Data Context: Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Name: System Writer Writer Instance ID: {49d8c06f-ee95-4c8d-a35a-8e4efdec74a9}</Data> 
      <Binary>2D20436F64653A20575254575254494330303030313238372D2043616C6C3A20575254575254494330303030313234312D205049443A202030303030353232342D205449443A202030303030353638382D20434D443A2020433A5C57494E444F57535C73797374656D33325C737663686F73742E657865202D6B204E6574776F726B53657276696365202D70202D732043727970745376632D20557365723A204E616D653A204E5420415554484F524954595C4E4554574F524B20534552564943452C205349443A532D312D352D3230</Binary> 
      </EventData>
      </Event>

    and at 4:18 when it fails

    The VSS service is shutting down due to idle timeout. 
    - <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
    - <System>
      <Provider Name="VSS" /> 
      <EventID Qualifiers="0">8224</EventID> 
      <Level>4</Level> 
      <Task>0</Task> 
      <Keywords>0x80000000000000</Keywords> 
      <TimeCreated SystemTime="2019-07-14T14:18:23.753405100Z" /> 
      <EventRecordID>18220</EventRecordID> 
      <Channel>Application</Channel> 
      <Computer>Schizophrenic.CHAMBREDUPEINE.local</Computer> 
      <Security /> 
      </System>
    - <EventData>
      <Data /> 
      <Binary>2D20436F64653A2020434F525356434330303030303735392D2043616C6C3A2020434F525356434330303030303734312D205049443A202030303031303439322D205449443A202030303031353931362D20434D443A2020433A5C57494E444F57535C73797374656D33325C76737376632E6578652020202D20557365723A204E616D653A204E5420415554484F524954595C53595354454D2C205349443A532D312D352D313820</Binary> 
      </EventData>
      </Event>
    Any suggestions?


    Monday, July 15, 2019 10:09 AM
  • No Success. After trying everything mentioned during different times. I did exactly as Wigster did, doing all of the recommendations at the same time and then rebooting (with 1903 v18362.239 and a fully patched Windows Server Essentials 2016) and still it could not connect to the server right after asking for login credentials during the connector setup.

    The problem is definitely with the 1903 release and needs to be fixed!

    Tuesday, July 16, 2019 3:25 AM
  • Hi, I like others am having the very same issue!  six work stations and server essentials 2016 stopper seeing the 5 I updated to 1903, the one in the garage I did not update is fine and still updates every morning at 0130!  Thank you guys for all your hard work, you've saved me alot of wasted time and effort.  I'm not very techie but willing to help anyway I can but I'm convinced it's something Microsoft will need to fix!

    Update:  https://www.technicaone.net/fix-windows-10-1903-breaks-windows-server-2016-essentials-connector/#comments 

    I tried this with one addition as without it I kept getting the Server not found error.  I had my workstations setup to skip domain so I used the router ip for my DNS, I changed it to the server lan address and it worked, only thing I did not like was it joined me to the domain but I was able to login with my original account after logging out of the domain account just setup by installing the connector.  hope this helps.  I'll try other things to see if I can get around the domain login account being added.  hope this makes sense!

    • Edited by ldwhyte Friday, July 19, 2019 9:36 PM
    Friday, July 19, 2019 6:44 PM
  • No luck for me.

    I tried setting my DNS to that of my Windows Server and it still couldn't find the server after entering the login credentials. :-(

    • Proposed as answer by 4xMeister Saturday, July 20, 2019 2:15 AM
    Friday, July 19, 2019 10:06 PM
  • did you do all the other things at the bottom of the link:

    SOLUTION

    We found that a non-destructive solution is possible.

    •  Uninstall "Client Connector for Windows Server Essentials"
    • Remove Scheduled Tasks - Path Microsoft\Windows\Windows Server Essentials (remove each task then the folder)
    • No reboot required

    Now navigate to HTTPS:\\[YourWSEServer]\connect and reinstall the connector

    Client machine may reboot (some did others did not)

    Test by performing a Manual Client Backup.

    Friday, July 19, 2019 10:08 PM
  • Yes. More times than I care to mention.

    I have also attempted the DNS to IP of the server and the Uninstall along with manual removal of folder and Scheduled Task and reinstall after each and every Windows 1903 update that has come along (about 3 or 4 now) - still no luck :-(

    Friday, July 19, 2019 11:17 PM
  • Same issue here.  Tried all the steps everyone else has.  Very frustrating.  I think MS wants Server Essentials to go away given that the 2019 version does not even support backups.
    Saturday, July 20, 2019 1:30 AM
  • **********NEW   SOLUTION***************

    Hi,

    I have posted an update on another thread, and I am trying to get its awareness raised as most advice is the same as previous releases but non worked for me.  The solution is not one I devised but is what I found on a blog post.  Linking below

    https://social.technet.microsoft.com/Forums/en-US/bdbcec29-8f0b-46ce-a2c7-13ec6cfb64e1/windows-10-feature-update-1903-disables-essentials-connector?forum=winserveressentials

    • Proposed as answer by Minimos Saturday, July 20, 2019 4:09 PM
    Saturday, July 20, 2019 4:09 PM
  • Worked with making sure all of the services were intact before seeing your post. Tried what was said in your blog post anyways - still No Luck.

    The problem is definitely with Win 10 v1903

    Saturday, July 20, 2019 5:46 PM
  • the solution I posted was a bit premature, I was about 22% thru an backup, the workstation shows in the server but after 4 attempts on two PC's a backup never completes! Very sad MS would allow this to fester so lone without a solution!  Thanks to everyone for the continued search of a fix!!

    Saturday, July 20, 2019 8:13 PM