Entrar
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
The windows home server 2011 connector has encountered an unexpected error on Windows 7 Ultimate x86

Proposed Answer The windows home server 2011 connector has encountered an unexpected error on Windows 7 Ultimate x86

  • terça-feira, 26 de abril de 2011 06:43
     
     
    Entrar para Votar
    0

    Ok, i'm at my wits end almost with this problem. Just upgraded my HP EX495 to WHS2011 and I was able to connect my HTPC Win7 x64 to it, and my Mac OSX to it as well. However, my laptop I am typing on (which is the most important) is Win7 Ultimate x86 and for the life of me i can't get it to connect.

    Here's what I've tried:

    • I can ping and find the server just fine
    • I have enabled Windows Media Center Services (both)
    • I have disabled AV & Firewall

    No luck, every single time it goes through like it's installing, and then rolls back and then says the unexpected error.

    I checked Event Viewer and this was the only thing I found:

    Windows Installer installed the product. Product Name: Windows Home Server 2011 Connector. Product Version: 6.1.8800.16385. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.

     

    Any ideas?

     

Todas as Respostas

  • sexta-feira, 29 de abril de 2011 03:31
     
     
    Entrar para Votar
    0

    Hi Shadymg,

     

    I am having the same issue, here is my link to our troubleshooting attempts.

    http://social.microsoft.com/Forums/en-US/whsvailbeta/thread/039b38bd-7700-4d85-827c-38929f7d3806

     

    Thanks,

    SirStox

    Sir Stox
     
  • segunda-feira, 2 de maio de 2011 03:48
     
     
    Entrar para Votar
    0

    Same problem here.  I get an "Unexpected error has occurred" trying to install Connector for WHS 2011 on a new Dell PC, 64 bit, Windows Home Premium. The error comes after prompted for the server password.  I have tried multiple times with the same result.  Alternating between reboots, disabled virus software (MSE) etc.  Nothing noted in the event log. Are there logs I can check for some clues about what might be wrong?

     

    Thanks!

    Paul

     
  • terça-feira, 3 de maio de 2011 20:21
     
     
    Entrar para Votar
    0

    See if this helps http://www.dotnetindia.com/2011/05/home-server-2011-connector-and-problems-with-net-framework.html...

    Regards, Anand Mukundan http://www.dotnetindia.com
     
  • domingo, 15 de maio de 2011 01:52
     
     
    Entrar para Votar
    0

    Anand, I finally got a change to try your suggestion. Alas, it was not the issue.  However, I did find the issue!

    Reading the help associated with this error message, I found the path to where the installer puts the trace files:

    C:\ProgramData\Microsoft\Windows Server\Logs

    I looked for errors in the logs and found this gem:

    [3196] 110514.175538.2950: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1

    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://server:65500/CertWebservice.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 82.98.86.171:65500

    The interesting part is that the IP address is incorrect.  My internal IP addresses all start with 192.168.1.xxx.  I opened a command line and pinged 'SERVER'.  Sure enough it mapped to the IP 82.98.86.171. Somehow the hostname SERVER is being resolved to the wrong IP address.

    I entered http://82.98.86.171 and was diverted to sedoparking.com.  Reverse DNS reveals the same.  What I am not clear about is how a DNS lookup for 'SERVER' endedup with sedoparking's IP address.

    To get around this problem, I updated the hosts file on the computer to map the name server to the correct address.  Everything works correctly now!

    Modifying the hosts file is obviously a temporary workaround.  I will post more when I figure out why server is resolving to the wrong IP address.

     

     
  • domingo, 15 de maio de 2011 02:02
     
     Resposta Proposta
    Entrar para Votar
    1

    Understanding the nature of my problem helped me find this excellent article.

    http://social.microsoft.com/Forums/en-US/whsfaq/thread/15a9e657-54a3-453f-b0e7-1efa59b7feea

     

    It turns out I had configured my router to have 'tidwell.net' in the 'Domain Name' field.  This is not a domain I own, and I am not sure why I put it there. I assumed it was harmless.

    All of the computers in my home network were trying 'server.tidwell.net' in the process of resolving the host name and getting an answer!  The company 'sedoparking.com' has reserved tidwell.net (and will happily sell it to me I am sure).  Reconfiguring my router (removing the bogus domain name) took care of the problem.

     

     

     

    • Sugerido como Resposta PDT domingo, 15 de maio de 2011 02:03
    •  
     
  • terça-feira, 10 de janeiro de 2012 20:29
     
     
    Entrar para Votar
    0
     

    Anand, I finally got a change to try your suggestion. Alas, it was not the issue.  However, I did find the issue!

    Reading the help associated with this error message, I found the path to where the installer puts the trace files:

    C:\ProgramData\Microsoft\Windows Server\Logs

    I looked for errors in the logs and found this gem:

    [3196] 110514.175538.2950: ClientSetup: MachineIdentityManager.GetMachineStatus had errors: ErrorCatalog:ProviderNotAvailable ErrorCode:-1

    BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetMachineStatus ---> System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at https://server:65500/CertWebservice.svc that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 82.98.86.171:65500

    The interesting part is that the IP address is incorrect.  My internal IP addresses all start with 192.168.1.xxx.  I opened a command line and pinged 'SERVER'.  Sure enough it mapped to the IP 82.98.86.171. Somehow the hostname SERVER is being resolved to the wrong IP address.

    I entered http://82.98.86.171 and was diverted to sedoparking.com.  Reverse DNS reveals the same.  What I am not clear about is how a DNS lookup for 'SERVER' endedup with sedoparking's IP address.

    To get around this problem, I updated the hosts file on the computer to map the name server to the correct address.  Everything works correctly now!

    Modifying the hosts file is obviously a temporary workaround.  I will post more when I figure out why server is resolving to the wrong IP address.

     

     


    Thanks for this - added the Server IP address to each client PC's Hosts file fixed it - brilliant, thanks!