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

    问题

  • 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?

    2011年4月26日 6:43

全部回复

  • 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
    2011年4月29日 3:31
  • 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

    2011年5月2日 3:48
  • 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
    2011年5月3日 20:21
  • 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.

     

    2011年5月15日 1:52
  • 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.

     

     

     

    • 已建议为答案 PDT 2011年5月15日 2:03
    2011年5月15日 2:02
  •  

    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!
    2012年1月10日 20:29
  • Like you I ended up, having tried every relevant suggestion I could find without success, at my wit's end and planning a complete reinstallation of the OS on the client machine. However I did manage to find a solution just before I got to that point. To give some context: as well as the WHS Connector problem I also had a problem with Windows Update which had got stuck in a loop whereby it kept telling me I needed to reboot to install important updates but somehow these updates never got installed after a restart and I'd get the same message again. 

    It turned out that the solution to both of these problems was the same. I noticed in the error logs that there were a lot of errors showing against Windows Search and when I tried starting the Windows Search service it would start but then stop. The solution to this problem at http://support.microsoft.com/kb/2484025/en-us not only got Windows Search going again but also sorted out the Windows Update problem and then allowed me to re-install the Connector software for WHS 2011. I'm not sure why this was the solution but/ after the days I'd spent on this tearing my hair out, I didn't care too much! Anyway, I hope this helps someone. 

    2013年11月5日 11:21
  • Like you I ended up, having tried every relevant suggestion I could find without success, at my wit's end and planning a complete reinstallation of the OS on the client machine. However I did manage to find a solution just before I got to that point. To give some context: as well as the WHS Connector problem I also had a problem with Windows Update which had got stuck in a loop whereby it kept telling me I needed to reboot to install important updates but somehow these updates never got installed after a restart and I'd get the same message again. 

    It turned out that the solution to both of these problems was the same. I noticed in the error logs that there were a lot of errors showing against Windows Search and when I tried starting the Windows Search service it would start but then stop. The solution to this problem at http://support.microsoft.com/kb/2484025/en-us not only got Windows Search going again but also sorted out the Windows Update problem and then allowed me to re-install the Connector software for WHS 2011. I'm not sure why this was the solution but/ after the days I'd spent on this tearing my hair out, I didn't care too much! Anyway, I hope this helps someone. 

    2013年11月5日 11:22