none
Connect wizard fails - the server is not available

    Question

  • The connect wizard fails from all client PC's. All the usual issues that I know of have been addressed - DNS points to the server, IPv6 disabled, firewalls, security software, etc. Cleanly installed Windows 10 Pro, new out of box PC, reconnecting an existing client - all have the same error - After supplying the user name and password to the wizard, "Cannot connect this computer to the network. The Server is not available. Try connecting this computer again... Something is clearly amiss on the server.

    Here is the contents of the ClientDeploy.log. The ComputerConnector.log and the CSetup.log have no errors. I don't have the knowledge to understand exactly what these errors are telling me. Can some please direct me to documentation or give me help with what to look at next? Thank-you!

    ---------------------------------------------------------
    [2844] 171221.114453.2200: ClientSetup: Start of ClientDeploy
    [2844] 171221.114453.2982: General: Initializing...C:\Windows\Temp\Client Deployment Files\ClientDeploy.exe
    [2844] 171221.114453.3138: ClientSetup: Loading Wizard Data
    [2844] 171221.114453.5482: ClientSetup: Current DeploymentStatus=Running
    [2844] 171221.114454.2071: ClientSetup: Showing the Client Deployment Wizard
    [2844] 171221.114454.4267: ClientSetup: Adding Server Info data in the Product Registry
    [2844] 171221.114454.4579: ClientSetup: Set the Deployment Sync Event
    [7060] 171221.114504.2457: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [7060] 171221.114504.2457: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7060] 171221.114504.2457: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [7060] 171221.114504.2457: ClientSetup: Entering InstallRootCertTask.Run
    [7060] 171221.114504.2457: ClientSetup: Install root cert to local trusted store
    [7060] 171221.114504.2613: ClientSetup: Exiting InstallRootCertTask.Run
    [7060] 171221.114504.2613: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [7060] 171221.114504.2613: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [7060] 171221.114504.2613: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [7060] 171221.114504.2613: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [7060] 171221.114504.2613: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7060] 171221.114504.2613: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [7060] 171221.114504.2613: ClientSetup: Entering SetupVpnAndDATask.Run
    [7060] 171221.114504.2925: ClientSetup: Exting SetupVpnAndDATask.Run
    [7060] 171221.114504.2925: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
    [7060] 171221.114504.2925: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [7060] 171221.114504.2925: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [7060] 171221.114504.2925: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [7060] 171221.114504.2925: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [7060] 171221.114504.2925: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [7060] 171221.114504.2925: ClientSetup: Entering ValidateUserTask.Run
    [7060] 171221.114504.2925: ClientSetup: Validating User
    [7060] 171221.114504.2925: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [7060] 171221.114506.3207: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1
    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.FaultException: The server was unable to process the request due to an internal error.  For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.

    Server stack trace: 
       at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
       at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
       at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]: 
       at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       at Microsoft.WindowsServerSolutions.Devices.Identity.ICertService.GetMachineStatus(MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum, String userName, String password, String machineName)
       at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
       --- End of inner exception stack trace ---
       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)
    [7060] 171221.114506.3207: ClientSetup: Exiting ValidateUserTask.Run
    [7060] 171221.114506.3207: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
    [7060] 171221.114506.3207: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [7060] 171221.114506.3207: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [2844] 171221.114506.3207: ClientSetup: JoinNetwork Tasks returned TaskStatus=Failed
    [2844] 171221.114509.8125: ClientSetup: Back from the Client Deployment Wizard
    [2844] 171221.114509.8281: ClientSetup: Saving Wizard Data
    [2844] 171221.114509.8281: ClientSetup: End of ClientDeploy: ErrorCode=1603

    Thursday, December 21, 2017 6:40 PM

All replies

  • Hi,

    Please try below steps:
    1. Open Run, type “dcomcnfg” and end with enter to open Component Services.
    2. Double-click Component Services - Computers.
    3. Right-click My Computer, and then click Properties - COM Security tab.
    4. In the Launch and Activation Permissions area, click Edit Default.
    5. Click Add, type Network Service, and then click OK.
    6. While Network Service is selected, click to select the Allow check boxes for the following items:
    Local Launch
    Remote Launch
    Local Activation
    Remote Activation

    Save the change and try to re-connect client to Essentials Server and check the result.

    If problem persists, please provide more information:
    1. Your Essentials Server’s OS name and version.
    2. Whether this problem happens recently? And it had worked before? Any change before problem happens?
    3. Please check Event Viewer and confirm that if any relate event has been logged?

    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, December 22, 2017 6:16 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.

    Tuesday, December 26, 2017 2:58 AM
    Moderator
  • Hi,

    Is there any update?

    Please click “Mark as answer” if the reply is helpful. It would make this reply to the top and easier to be found for other people who has the similar problem.

    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, December 28, 2017 2:11 AM
    Moderator
  • Eve, thank you so much for your response. I haven't been back to the client site yet to try this. I'll keep you posted. 

    Bob

    Friday, December 29, 2017 2:37 PM
  • Hi,

    If there is anything update, please feel free to let us know.

    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, January 01, 2018 6:14 AM
    Moderator
  • Good Morning Eve,

    I am having this same issue.

    I have already tried running through the steps you have outlined with no success.

    To answer your questions:

    1. Windows Server 2016 Essentials 64-bit (10.0, Build 14393)

    2. This problem has only started this morning (1/2/18). I had no issues with any computers I connected last night (1/1/18). I made two changes between last night and this morning. The first is that I started an off site cloud backup for the server, which ran until I arrived this morning. The second is I am using both ethernet ports this morning as opposed to just using one last night.

    3. I'm not quite sure which events I'm looking for. There are several that seem like they could be the issue.

    EventID: 144 - (one instance)

    EventID: 10016 - (multiple instances)

    EventID: 4319 - (multiple instances)

    Tuesday, January 02, 2018 3:52 PM
  • I have resolved my issue.

    I unplugged the second ethernet cable and then pointed the connectors to the first ethernet port's ip address. Every computer was able to connect after. 

    Tuesday, January 02, 2018 5:07 PM
  • Hi,

    Thank you for taking the time to update the result. Your detail sharing might be helpful for other people who has the similar problem.

    If there is anything else we can do for you, please feel free to post in the forum.

    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, January 03, 2018 1:35 AM
    Moderator
  • Hello Eve, I'm the original poster of this question. 

    I tried your suggested steps, without success. (performed on the Server)

    No events recorded in Event viewer on PC at the same time as the failure.

    Server OS is Windows Server 2012 Essentials.

    All LAN adapters on the server are joined in a team with a single static IP.

    This started months ago, but at the time I thought it was a problem with the PC I was trying to add. (PC's are not added often.) Since then, I have been unable to add any PC's, and have realized the problem is most likely with the server. Every PC I try to add gives the same result, even brand new out of the box, or reformatted and reinstalled Windows 10.

    It may have started after removing WSUS from the server.

    There are 2 recurring DCOM errors on the PC, but seemingly at random times. Event ID 10016

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {6B3B8D23-FA8D-40B9-8DBD-B950333E2C52}
     and APPID 
    {4839DDB7-58C2-48F5-8283-E1D1807D0D7D}
     to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID 
    {D63B10C5-BB46-4990-A94F-E40B9D520160}
     and APPID 
    {9CA88EE3-ACB7-47C8-AFC4-AB702511C276}
     to the user NT AUTHORITY\LOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

    Thank you for looking at this.



    Wednesday, January 03, 2018 9:57 PM
  • Hi,

    >All LAN adapters on the server are joined in a team with a single static IP.
    As far as I know, NIC teaming is not supported on Windows Server Essentials.

    If possible, I would recommend you to remove NIC teaming and enable only one NIC on your server, assign a static IP address and check the result.

    If problem persists, please provide me the complete ClientDeploy.log file.

    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, January 04, 2018 9:44 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.

    Monday, January 08, 2018 8:19 AM
    Moderator
  • Hi,

    Is there any update?

    Please click “Mark as answer” if the reply is helpful. It would make this reply to the top and easier to be found for other people who has the similar problem.

    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, January 10, 2018 6:39 AM
    Moderator