none
Essentials Connector: The server is not available after upgrade from Windows 8 Pro to Windows 8.1. Pro RRS feed

  • Question

  • Hi all

    As many others I am facing also connection problems with Windows Server 2012 Essentials R2 and a windows client pc.

    The client pc in question, with windows 8 pro, has been successfully joined through the essentials connector to the domain.
    All things went good: media streaming, shared folders, a successfull backup has been started through the essentials launchpad, the client appeared as online in the devices tab of the essentials dashboard.

    Then I upgraded the pc to windows 8.1 pro.

    Now the client can't connect to the server. Following issues appear:

    1. The client pc is showed as offline the the dashboard when it is online.
    2. Backups (from launchpad or server) aren't  possible -> no connection to the windows server essentials adminitration service.
    3. Dashboard not available from launchpad
    4. The message "the server is not available" appears, when I try to reconnect the client by the essentials connector.

    BUT:

    1. ping to the server's ip address works.
    2. media streaming is also ok
    3. shared folders are still available.

    Any ideas what changed with the upgrade to 8.1 Pro? Is the a firewall problem on the client pc?

    Many thanks for your help.

    PS. If anyone needs a specific log file from the server or the client, please let me know.

    Monday, June 2, 2014 4:43 PM

All replies

  • Hi,

    Based on your description, would you please let me confirm something more?

    1. Did you mean that you didn’t uninstall Connector software when upgrade Windows 8 Professional to Windows 8.1 Professional?
    2. The message "the server is not available" appears, when I try to reconnect the client by the essentials connector.”

    Did you mean that you can download the Connector software (type http://servername/connect), just can’t install it successfully?

    On current situation, please refer to following operations and check if can help you to solve this issue.

    1. Please check if the client computer’s date and time settings align to the settings on the server.
    2. Please logon the problematic client computer, and follow the path: Control Panel-> Programs and Features-> View installed updates. Then check if there has Windows Server Essentials Connector. If has, please uninstall it fully. And then re-install it again (type http://servername/connect) and monitor the result.

    If this issue still persists, please start BPA scan and check if you can find some more clues. Meanwhile, please navigate to %programdata%/Microsoft/Windows Server/Logs folder in the client computer and check ClientDeploy log file.

    Hope this helps.

    Best regards,

    Justin Gu

    Tuesday, June 3, 2014 12:04 PM
    Moderator
  • Hi Justin

    Thanks for your answer.

    > Did you mean that you didn’t uninstall Connector software when upgrade Windows 8 Professional to Windows 8.1 Professional

    YES, in my opinion, there is no reason to do that, but I can try this.

    > Did you mean that you can download the Connector software (type http://servername/connect), just can’t install it successfully?

    YES, i can download it. The server adds its ip-addres to the file name, such as (192.168.x.y)

    > Date and Time:
    On both machines samte time zone 
    (UTC+01:00) Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna and same time.

    > Regional Settings: Also on both machines German (Switzerland)

    Next steps:

    I will uninstall the connector and reinstall it.
    If it does not help, I will upload the ClientDeploy log file.


    Best regards,

    Hans


    Tuesday, June 3, 2014 2:37 PM
  • Hi Justin

    I executed all you instructions, but nothing helped.

    I add here the ClientDeploy.log and the ComputerConnector.log

    The ClientDeploy stopps after a registry insert error.
    The user executing the connector is member of the Administrators Group on the Client pc.
    I started the connector even with "Run as Administrator" but nothing helped.

    Any ideas why this registry insert failes?

    Thanks for you help and best regards

    Hans

    ---------------------------------------------------------
    [5692] 140604.211748.1774: ClientSetup: Start of ClientDeploy
    [5692] 140604.211748.3181: General: Initializing...C:\WINDOWS\system32\Essentials\ClientDeploy.exe
    [5692] 140604.211748.3337: ClientSetup: Create client deployment registry subkey if necessary
    [5692] 140604.211748.3493: ClientSetup: The initial launching way: -LaunchedFrom:installer
    [5692] 140604.211748.3493: ClientSetup: The initial state is set
    [5692] 140604.211748.3493: ClientSetup: The initial serverName: 192.168.3.21
    [5692] 140604.211748.3493: ClientSetup: Loading Wizard Data
    [5692] 140604.211748.3649: ClientSetup: Saving Wizard Data
    [5692] 140604.211748.3649: ClientSetup: Current DeploymentStatus=Start
    [5692] 140604.211748.7400: ClientSetup: Showing the Client Deployment Wizard
    [5692] 140604.211748.8493: ClientSetup: Machine name:PCFA, length:4
    [5692] 140604.211748.8650: ClientSetup: The input server name is 192.168.3.21
    [2156] 140604.211748.8806: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [2156] 140604.211748.8806: ClientSetup: Running Task with Id=ClientDeploy.PreConfiguration
    [5692] 140604.211748.8962: ClientSetup: InitWizard, The currrent stage is ConnectingToServer
    [5692] 140604.211748.8962: ClientSetup: Set the Deployment Sync Event
    [2156] 140604.211748.8962: ClientSetup: The configuration cab will be downloaded from 192.168.3.21
    [2156] 140604.211748.9118: ClientSetup: Download file Setup.cab from server
    [2156] 140604.211748.9275: ClientSetup: Making web request: https://192.168.3.21//connect/default.aspx?Get=Setup.cab&LanguageId=1031&64bit=1
    [2156] 140604.211748.9743: ClientSetup: Failed to download Setup.cab from server: System.Net.WebException: Die zugrunde liegende Verbindung wurde geschlossen: Für den geschützten SSL/TLS-Kanal konnte keine Vertrauensstellung hergestellt werden.. ---> System.Security.Authentication.AuthenticationException: Das Remotezertifikat ist laut Validierungsverfahren ungültig.
       bei System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       bei System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       bei System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       bei System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei System.Net.HttpWebRequest.GetResponse()
       bei Microsoft.WindowsServerSolutions.ClientSetup.CSCommon.DownloadFileFromConnectSite(String outputDirectory, Uri serverUrl, String fileName, Int32 languageId, Boolean is64bit)
    [2156] 140604.211748.9743: ClientSetup: Cannot get configuration file with https, will try http...
    [2156] 140604.211748.9743: ClientSetup: Download file Setup.cab from server
    [2156] 140604.211748.9743: ClientSetup: Making web request: http://192.168.3.21//connect/default.aspx?Get=Setup.cab&LanguageId=1031&64bit=1
    [2156] 140604.211749.0369: ClientSetup: Downloaded file C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [2156] 140604.211749.0369: ClientSetup: The configuration cab is downloaded to C:\WINDOWS\Temp\ClientDeploymentTempFiles\Setup.cab
    [2156] 140604.211749.1775: ClientSetup: Adding Server Info data in the Product Registry
    [2156] 140604.211749.1931: DnsEnvironmentDetector: GetHostAddresses() returned 192.168.3.21, normal environment
    [2156] 140604.211749.1931: ClientSetup: Exiting PreConfigTask.Run()
    [2156] 140604.211749.1931: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has TaskStatus=Success
    [2156] 140604.211749.1931: ClientSetup: Task with Id=ClientDeploy.PreConfiguration has RebootStatus=NoReboot
    [2156] 140604.211749.1931: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5792] 140604.211758.0217: ClientSetup: Running InstallRootCert Task at WizardPage DomainUserCred
    [5792] 140604.211758.0373: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5792] 140604.211758.0373: ClientSetup: Running Task with Id=ClientDeploy.InstallRootCertTask
    [5792] 140604.211758.0373: ClientSetup: Entering InstallRootCertTask.Run
    [5792] 140604.211758.0373: ClientSetup: Install root cert to local trusted store
    [5792] 140604.211758.0373: ClientSetup: Exiting InstallRootCertTask.Run
    [5792] 140604.211758.0373: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has TaskStatus=Success
    [5792] 140604.211758.0373: ClientSetup: Task with Id=ClientDeploy.InstallRootCertTask has RebootStatus=NoReboot
    [5792] 140604.211758.0373: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5792] 140604.211758.0373: ClientSetup: Running SetupVPNAndDA Task at WizardPage DomainUserCred
    [5792] 140604.211758.0373: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5792] 140604.211758.0373: ClientSetup: Running Task with Id=ClientDeploy.SetupVpnAndDATask
    [5792] 140604.211758.0529: ClientSetup: Entering SetupVpnAndDATask.Run
    [5792] 140604.211758.0685: ClientSetup: Deploy VPN profile
    [5792] 140604.211758.0998: ClientSetup: Exting SetupVpnAndDATask.Run
    [5792] 140604.211758.0998: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has TaskStatus=Success
    [5792] 140604.211758.0998: ClientSetup: Task with Id=ClientDeploy.SetupVpnAndDATask has RebootStatus=NoReboot
    [5792] 140604.211758.0998: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5792] 140604.211758.0998: ClientSetup: Running ValidateUser Tasks at WizardPage DomainUserCred
    [5792] 140604.211758.0998: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5792] 140604.211758.0998: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [5792] 140604.211758.0998: ClientSetup: Entering ValidateUserTask.Run
    [5792] 140604.211758.0998: ClientSetup: Validating User
    [5792] 140604.211758.0998: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [5792] 140604.211758.1779: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:NetworkError ErrorCode:-1
    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.Security.SecurityNegotiationException: Es konnte keine Vertrauensstellung für den sicheren SSL/TLS-Kanal mit Autorität mars01:65500 eingerichtet werden. ---> System.Net.WebException: Die zugrunde liegende Verbindung wurde geschlossen: Für den geschützten SSL/TLS-Kanal konnte keine Vertrauensstellung hergestellt werden.. ---> System.Security.Authentication.AuthenticationException: Das Remotezertifikat ist laut Validierungsverfahren ungültig.
       bei System.Net.Security.SslState.StartSendAuthResetSignal(ProtocolToken message, AsyncProtocolRequest asyncRequest, Exception exception)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessReceivedBlob(Byte[] buffer, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
       bei System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
       bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
       bei System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
       bei System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
       bei System.Net.ConnectStream.WriteHeaders(Boolean async)
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei System.Net.HttpWebRequest.GetResponse()
       bei System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       --- Ende der internen Ausnahmestapelüberwachung ---

    Server stack trace:
       bei System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
       bei System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
       bei System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
       bei System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
       bei System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
       bei System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

    Exception rethrown at [0]:
       bei System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
       bei System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
       bei Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.ICertService.GetMachineStatus(GetMachineStatusRequest request)
       bei Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.CertServiceClient.GetMachineStatus(String userName, String password, String machineName, MachineStatus& status, Boolean& isAdmin, Int32& maxClientNum, Int32& currentClientNum)
       bei Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetMachineStatus(String serverName, String userName, String password, String machineName, Boolean& isAdmin)
       bei Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.ValidateUserTask.Run(WizData data)
    [5792] 140604.211758.1779: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\ipconfig.exe"  /all
    [2156] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [2156] 140604.211758.2092: ClientSetup: Standard Ouptput: Windows-IP-Konfiguration
    [2156] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Hostname  . . . . . . . . . . . . : PCFA
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Prim„res DNS-Suffix . . . . . . . : mydomain.local
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Knotentyp . . . . . . . . . . . . : Hybrid
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    IP-Routing aktiviert  . . . . . . : Nein
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    WINS-Proxy aktiviert  . . . . . . : Nein
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DNS-Suffixsuchliste . . . . . . . : mydomain.local
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Drahtlos-LAN-Adapter LAN-Verbindung* 11:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Medienstatus. . . . . . . . . . . : Medium getrennt
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Verbindungsspezifisches DNS-Suffix:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Beschreibung. . . . . . . . . . . : Virtueller Microsoft-Adapter fr direktes WiFi
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Physische Adresse . . . . . . . . : 16-
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DHCP aktiviert. . . . . . . . . . : Ja
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Autokonfiguration aktiviert . . . : Ja
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Ethernet-Adapter LAN-Verbindung:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Verbindungsspezifisches DNS-Suffix:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Beschreibung. . . . . . . . . . . : Broadcom NetLink (TM)-Gigabit-Ethernet
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Physische Adresse . . . . . . . . : DC-
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DHCP aktiviert. . . . . . . . . . : Ja
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Autokonfiguration aktiviert . . . : Ja
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    IPv4-Adresse  . . . . . . . . . . : 192.168.2.6(Bevorzugt)
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Subnetzmaske  . . . . . . . . . . : 255.255.255.0
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Lease erhalten. . . . . . . . . . : Mittwoch, 4. Juni 2014 18:03:36
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Lease l„uft ab. . . . . . . . . . : Freitag, 6. Juni 2014 20:49:17
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Standardgateway . . . . . . . . . : 192.168.2.1
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DHCP-Server . . . . . . . . . . . : 192.168.2.1
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DNS-Server  . . . . . . . . . . . : 192.168.3.21
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:                                        192.168.1.52
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    NetBIOS ber TCP/IP . . . . . . . : Aktiviert
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Drahtlos-LAN-Adapter WiFi:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Medienstatus. . . . . . . . . . . : Medium getrennt
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Verbindungsspezifisches DNS-Suffix: Home
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Beschreibung. . . . . . . . . . . : Qualcomm Atheros AR5B97-Funknetzwerkadapter
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Physische Adresse . . . . . . . . : 94-
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DHCP aktiviert. . . . . . . . . . : Ja
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Autokonfiguration aktiviert . . . : Ja
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput: Tunneladapter isatap.{8F57A34A-FE47-429C-97D0-AA777D79C23F}:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Medienstatus. . . . . . . . . . . : Medium getrennt
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Verbindungsspezifisches DNS-Suffix:
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Beschreibung. . . . . . . . . . . : Microsoft-ISATAP-Adapter
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Physische Adresse . . . . . . . . : 00-00-00-00-00-00-00-E0
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DHCP aktiviert. . . . . . . . . . : Nein
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Autokonfiguration aktiviert . . . : Ja
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:
    [4504] 140604.211758.2092: ClientSetup: Standard Error:
    [5792] 140604.211758.2248: ClientSetup: The exit code of the process (C:\WINDOWS\system32\ipconfig.exe) is: 0
    [5792] 140604.211758.2248: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\route.exe"  print
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Schnittstellenliste
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   9...16 39 e5 4c c5 f2 ......Virtueller Microsoft-Adapter fr direktes WiFi
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   4...dc 0e a1 06 1f c9 ......Broadcom NetLink (TM)-Gigabit-Ethernet
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   3...94 39 e5 4c c5 f2 ......Qualcomm Atheros AR5B97-Funknetzwerkadapter
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   1...........................Software Loopback Interface 1
    [1344] 140604.211758.2404: ClientSetup: Standard Error:
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   5...00 00 00 00 00 00 00 e0 Microsoft-ISATAP-Adapter
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: IPv4-Routentabelle
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Aktive Routen:
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:      Netzwerkziel    Netzwerkmaske          Gateway    Schnittstelle Metrik
    [5792] 140604.211758.2404: ClientSetup: The exit code of the process (C:\WINDOWS\system32\route.exe) is: 0
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:           0.0.0.0          0.0.0.0      192.168.2.1      192.168.2.6     10
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:         127.0.0.0        255.0.0.0   Auf Verbindung         127.0.0.1    306
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:         127.0.0.1  255.255.255.255   Auf Verbindung         127.0.0.1    306
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   127.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    306
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:       192.168.2.0    255.255.255.0   Auf Verbindung       192.168.2.6    266
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:       192.168.2.6  255.255.255.255   Auf Verbindung       192.168.2.6    266
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:     192.168.2.255  255.255.255.255   Auf Verbindung       192.168.2.6    266
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:         224.0.0.0        240.0.0.0   Auf Verbindung         127.0.0.1    306
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:         224.0.0.0        240.0.0.0   Auf Verbindung       192.168.2.6    266
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   255.255.255.255  255.255.255.255   Auf Verbindung         127.0.0.1    306
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   255.255.255.255  255.255.255.255   Auf Verbindung       192.168.2.6    266
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: St„ndige Routen:
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   Keine
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:
    [5792] 140604.211758.2404: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\nslookup.exe" mars01
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: IPv6-Routentabelle
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: Aktive Routen:
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:  If Metrik Netzwerkziel             Gateway
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   1    306 ::1/128                  Auf Verbindung
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   1    306 ff00::/8                 Auf Verbindung
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: ===========================================================================
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: St„ndige Routen:
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   Keine
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Server:  UnKnown
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Address:  192.168.3.21
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Name:    mars01.mydomain.local
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Addresses:  192.168.3.21
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:    192.168.1.131
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:    192.168.4.31
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:
    [4504] 140604.211758.2560: ClientSetup: Standard Error:
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:
    [5792] 140604.211758.2560: ClientSetup: The exit code of the process (C:\WINDOWS\system32\nslookup.exe) is: 0
    [5792] 140604.211758.2717: ClientSetup: Set CD Fail reason 10 for SQM in ClientDeployment.exe
    [5792] 140604.211758.2717: ClientSetup: RecordClientDeploymentFailReason: Save registry failed in ClientDeployment.exe : System.UnauthorizedAccessException: In den Registrierungsschlüssel kann nicht geschrieben werden.
       bei Microsoft.Win32.RegistryKey.EnsureWriteable()
       bei Microsoft.Win32.RegistryKey.CreateSubKeyInternal(String subkey, RegistryKeyPermissionCheck permissionCheck, Object registrySecurityObj, RegistryOptions registryOptions)
       bei Microsoft.Win32.RegistryKey.CreateSubKey(String subkey, RegistryKeyPermissionCheck permissionCheck)
       bei Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RecordClientDeploymentFailReason(UInt32 failReason)
    [5792] 140604.211758.2717: ClientSetup: Exiting ValidateUserTask.Run
    [5792] 140604.211758.2717: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Failed
    [5792] 140604.211758.2717: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [5792] 140604.211758.2717: ClientSetup: Exting ConnectorWizardForm.RunTasks

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

    [06/04/2014 20:23:38 1730] --------------------------------------------------------------------------------------------------
    [06/04/2014 20:23:38 1730] wmain: Start of Computerconnector
    [06/04/2014 20:23:38 1730] GlobalData::Initialize (192.168.3.10, C:\Users\johndoe.mydomain\Downloads\ComputerConnector(192.168.3.10).exe)
    [06/04/2014 20:23:38 1730] =================================
    [06/04/2014 20:23:38 1730] Current Os information:
    [06/04/2014 20:23:38 1730] Suite = [256]
    [06/04/2014 20:23:38 1730] Type = [1]
    [06/04/2014 20:23:38 1730] Architecture = [9]
    [06/04/2014 20:23:38 1730] IsStarterEdition = [0]
    [06/04/2014 20:23:38 1730] IsHomeSku = [0]
    [06/04/2014 20:23:38 1730] Major = [6]
    [06/04/2014 20:23:38 1730] Minor = [3]
    [06/04/2014 20:23:38 1730] Build = [9600]
    [06/04/2014 20:23:38 1730] SPMajor = [0]
    [06/04/2014 20:23:38 1730] SPMinor = [0]
    [06/04/2014 20:23:38 1730] =================================
    [06/04/2014 20:23:38 1730] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
    [06/04/2014 20:23:38 1730] SetPackageDlcUrl: .NET url is set to http://go.microsoft.com/?linkid=9816306
    [06/04/2014 20:23:38 1730] SetPackageDlcUrl: Connector url is set to http://go.microsoft.com/fwlink/p/?LinkId=275102
    [06/04/2014 20:23:38 1730] wmain: Calling Computerconnector::ShowWizard()
    [06/04/2014 20:23:38 1730] CComputerconnector::ShowWizard: Initializing common controls
    [06/04/2014 20:23:38 1730] CComputerconnector::ShowWizard: Done initializing common controls
    [06/04/2014 20:23:38 1730] Displaying the wizard
    [06/04/2014 20:23:38 1730] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
    [06/04/2014 20:23:38 1730] Current user default UI lang setting is 1031
    [06/04/2014 20:23:38   c8] CComputerconnector::Run: Installation is ready to run
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
    [06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die aktuellen Systemanforderungen werden ermittelt... Index=  0
    [06/04/2014 20:23:42 1774] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
    [06/04/2014 20:23:42 1774] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
    [06/04/2014 20:23:42 1774] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
    [06/04/2014 20:23:42 1774] Connector installation state is 1
    [06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird heruntergeladen... Index=  1
    [06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird installiert... Index=  2
    [06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Der Connector wird heruntergeladen... Index=  3
    [06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Windows Server Essentials Connector wird installiert... Index=  4
    [06/04/2014 20:23:42 1774] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die Einrichtung von Windows Server Essentials Connector wird gestartet... Index=  5
    [06/04/2014 20:23:42 1774] RunShellExecute: ShellExecute [C:\WINDOWS\system32\Essentials\ClientDeploy.exe] with parameters [ -Server:192.168.3.10 -LaunchedFrom:installer]
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die aktuellen Systemanforderungen werden ermittelt...
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird heruntergeladen...
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird installiert...
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Der Connector wird heruntergeladen...
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Windows Server Essentials Connector wird installiert...
    [06/04/2014 20:23:42 1730] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die Einrichtung von Windows Server Essentials Connector wird gestartet...
    [06/04/2014 20:23:42 1774] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
    [06/04/2014 20:23:43 1774] CComputerconnector::Run: WaitForSingleObject RetVal = 0
    [06/04/2014 20:23:43 1730] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
    [06/04/2014 20:23:43 1730] wmain: End of Computerconnector: hr=0x0
    [06/04/2014 20:54:06 1220] --------------------------------------------------------------------------------------------------
    [06/04/2014 20:54:06 1220] wmain: Start of Computerconnector
    [06/04/2014 20:54:06 1220] GlobalData::Initialize (192.168.3.10, C:\Users\johndoe.mydomain\Downloads\ComputerConnector(192.168.3.10)(1).exe)
    [06/04/2014 20:54:06 1220] =================================
    [06/04/2014 20:54:06 1220] Current Os information:
    [06/04/2014 20:54:06 1220] Suite = [256]
    [06/04/2014 20:54:06 1220] Type = [1]
    [06/04/2014 20:54:06 1220] Architecture = [9]
    [06/04/2014 20:54:06 1220] IsStarterEdition = [0]
    [06/04/2014 20:54:06 1220] IsHomeSku = [0]
    [06/04/2014 20:54:06 1220] Major = [6]
    [06/04/2014 20:54:06 1220] Minor = [3]
    [06/04/2014 20:54:06 1220] Build = [9600]
    [06/04/2014 20:54:06 1220] SPMajor = [0]
    [06/04/2014 20:54:06 1220] SPMinor = [0]
    [06/04/2014 20:54:06 1220] =================================
    [06/04/2014 20:54:06 1220] ExpandEnvironmentStrings return (C:\WINDOWS\Temp\ClientDeploymentTempFiles\)
    [06/04/2014 20:54:06 1220] SetPackageDlcUrl: .NET url is set to http://go.microsoft.com/?linkid=9816306
    [06/04/2014 20:54:06 1220] SetPackageDlcUrl: Connector url is set to http://go.microsoft.com/fwlink/p/?LinkId=275102
    [06/04/2014 20:54:06 1220] wmain: Calling Computerconnector::ShowWizard()
    [06/04/2014 20:54:06 1220] CComputerconnector::ShowWizard: Initializing common controls
    [06/04/2014 20:54:06 1220] CComputerconnector::ShowWizard: Done initializing common controls
    [06/04/2014 20:54:06 1220] Displaying the wizard
    [06/04/2014 20:54:06 1220] CComputerconnector::WelcomeDlgProc: IDD_PROPPAGE_WELCOME Page Initialization
    [06/04/2014 20:54:06 1220] Current user default UI lang setting is 1031
    [06/04/2014 20:54:06 1404] CComputerconnector::Run: Installation is ready to run
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: IDD_PROPPAGE_TASKS Page Initialization
    [06/04/2014 20:54:09  e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die aktuellen Systemanforderungen werden ermittelt... Index=  0
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Running
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die aktuellen Systemanforderungen werden ermittelt...
    [06/04/2014 20:54:09  e90] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {21E49794-7C13-4E84-8659-55BD378267D5} returned -1
    [06/04/2014 20:54:09  e90] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {46DCED50-3A1D-4EF4-94F0-45F2681E3D70} returned -1
    [06/04/2014 20:54:09  e90] CMsi::IsMsiInstalled: MsiQueryProductState for ProductCode {C1E4D639-4A33-4314-809E-89BD0EF48522} returned -1
    [06/04/2014 20:54:09  e90] Connector installation state is 1
    [06/04/2014 20:54:09  e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird heruntergeladen... Index=  1
    [06/04/2014 20:54:09  e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=.NET Framework 4.5 wird installiert... Index=  2
    [06/04/2014 20:54:09  e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Der Connector wird heruntergeladen... Index=  3
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird heruntergeladen...
    [06/04/2014 20:54:09  e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Windows Server Essentials Connector wird installiert... Index=  4
    [06/04/2014 20:54:09  e90] CComputerconnector::RunTasks: Running Task: Id=-1 Description=Die Einrichtung von Windows Server Essentials Connector wird gestartet... Index=  5
    [06/04/2014 20:54:09  e90] RunShellExecute: ShellExecute [C:\WINDOWS\system32\Essentials\ClientDeploy.exe] with parameters [ -Server:192.168.3.10 -LaunchedFrom:installer]
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: .NET Framework 4.5 wird installiert...
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Der Connector wird heruntergeladen...
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Windows Server Essentials Connector wird installiert...
    [06/04/2014 20:54:09 1220] CComputerconnector::TaskDlgProc: DIALOG_TASK_PROGRESS: Task Description: Die Einrichtung von Windows Server Essentials Connector wird gestartet...
    [06/04/2014 20:54:09  e90] CComputerconnector::Run: Waiting upto 60secs for Sync Event to be signaled
    [06/04/2014 20:54:13  e90] CComputerconnector::Run: WaitForSingleObject RetVal = 0
    [06/04/2014 20:54:13 1220] CComputerconnector::TaskDlgProc: DIALOG_UPDATE: Success
    [06/04/2014 20:54:13 1220] wmain: End of Computerconnector: hr=0x0

    Wednesday, June 4, 2014 7:56 PM
  • Today I tried to add another Windows 8.1 client. ComputerConnector has never been run on this pc.
    The same here: Save registry failed.

    I found many other people who faces the same problem, but no solution. It seems there are special difficulties with Windows 8.l1

    Any help is appreciated.

    Thanks.

    Hans

    Monday, June 9, 2014 11:43 AM
  • Hi there,

    any solutions for that problem in meantime? HAve the same here with two 8.1 Clients one is a VM the other one normal hardware pc.

    Thanks.

    Tuesday, August 19, 2014 11:50 AM
  • Hi Ak1r4

    Unfortunately I heard nothing from Microsoft. Maybe the problem is too heavy to answer this thread.

    Tuesday, August 19, 2014 12:51 PM
  • tvddev,

    8.1 works, but I am trying to setup a clean box to retest to see if any updates may have changed something.

    But why are there so many IP ranges in your log file?  I get lost in the translation.  Can you use one nic with the same subnet and gateway as the server and manually point dns to the server

    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    Standardgateway . . . . . . . . . : 192.168.2.1
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DHCP-Server . . . . . . . . . . . : 192.168.2.1
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:    DNS-Server  . . . . . . . . . . . : 192.168.3.21
    [1344] 140604.211758.2092: ClientSetup: Standard Ouptput:                                        192.168.1.52

    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput: St„ndige Routen:
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:   Keine
    [2156] 140604.211758.2404: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Server:  UnKnown
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Address:  192.168.3.21
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Name:    mars01.mydomain.local
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput: Addresses:  192.168.3.21
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:    192.168.1.131
    [1344] 140604.211758.2560: ClientSetup: Standard Ouptput:    192.168.4.31


    Grey

    Friday, August 29, 2014 10:01 PM
    Moderator
  • Fwiw I tried to duplicate this and I could.

    I uninstalled the connector from a win 8.1 update, reboot, and ran connect again.  Lo and behold it failed like everyone else.

    I set DNS to point to the 2012R2E box and re-ran the connector and all went well. 


    Grey

    Saturday, August 30, 2014 2:21 PM
    Moderator