locked
Cannot install WHS 2011 Connector Software on any 64-Bit Win 7 Ultimate Machine

    Question

  • Hello

    I recently downloaded and installed the latest version of Vail.

    I am unable to join any Windows 7 (64-bit edition) Ultimate machines to the Vail server. Installations fail with the error message "unexpected error". A bit of searching seemed to suggest that this is because the PC names used non-ASCII characters, which doesn't apply to me because they are simply named "PC1" and "LAPTOP2", etc.

    If I have missed something somewhere that says 64-bit editions of Windows are unsupported, then I'm sorry for wasting anyone's time...

    Thanks for your help.

    Rik.


    Richard Parker http://richard.parker.name
    Thursday, February 17, 2011 7:53 PM

Answers

  • I just wanted to provide a further update.

    It seems that Bullguard anti-virus & firewall isn't happy to work with the WHS Vail Launchpad/connector.

    Even with Bullguard firewall & antivirus disabled, the computer will always report that the Vail server is offline. Something about the product seems to interfere with Vail.

    If I uninstall Bullguard, reboot and login, the client is able to connect to the Vail server without any issue at all.


    Richard Parker http://richard.parker.name
    Tuesday, February 22, 2011 12:19 PM

All replies

  • No, 64 bit is supported.  I have 4 64-bit machines connected to my server.  The first step I would take is to make sure that there are no other versions of connector software from either WHS v1, or any past beta's running on the machines.  If thats not an issue, maybe provide a little more info about your network.  Your computers are able to find the server?
    D.W.
    Thursday, February 17, 2011 8:41 PM
  • Hi D.W.

    Thanks for your reply. I thought that may not be the case; I had presumed (hoped!) 64-bit was supported for this release.

    Both of these machines can "see" the Vail server on the network, no problems there. The connector software can be downloaded from the http://server/connector site and the set up itself contacts the server, asks for password, verifies, and gets to about 95%+ then starts to roll back.

    Both computers have also previously had WHS v1 connector software on them, but both have since had this uninstalled.

    In addition, I have reinstalled .NET FX 4 on both machines.

    It would be useful if the "unexpected error" message would at least tell me a little more about what the error was so that I might try investigating myself :)

    Any other ideas?

    Thanks,

    Rik.


    Richard Parker http://richard.parker.name
    Thursday, February 17, 2011 11:27 PM
  • It could be a network issue.  Does the server and your client both have valid IPv4 addresses?
    D.W.
    Friday, February 18, 2011 12:20 AM
  • The fact that it gets that close, and then backs off points me in that direction.
    D.W.
    Friday, February 18, 2011 12:21 AM
  • It could be a network issue.  Does the server and your client both have valid IPv4 addresses?
    D.W.

    Both have valid IPv4 addresses... 

    To test further any potential for network issues, I created static entries in both machines' hosts file to point to the server (they both pinged fine before this, anyway). I also disabled any firewall software on the client machines. Still no luck...

    Rik


    Richard Parker http://richard.parker.name
    Friday, February 18, 2011 8:22 AM
  • I think you're on to something there with the network issue.

    Even after disabling the firewall completely on the WHS box, the connector software fails at about 95% of the "Connecting your computer to the network...." stage.

    Here's a list of the stages the installer goes through with success:

    Please wait while your server is found... WORKS
    Verifying components ... WORKS
    Log on to your WHS Server 2011 [ServerName] ... WORKS
    Downloading the connector software ... WORKS

    And the failure occurs at the next step, "Connecting your computer to the network".

    I have verified that both the server and the client have valid IPv4 addresses. I have also tried again by disabling IPv6 on both machines and giving installation another shot. No joy.

    /Rik


    Richard Parker http://richard.parker.name
    Friday, February 18, 2011 8:41 AM
  • I think you're on to something there with the network issue.

    Even after disabling the firewall completely on the WHS box, the connector software fails at about 95% of the "Connecting your computer to the network...." stage.

    Here's a list of the stages the installer goes through with success:

     

    Please wait while your server is found... WORKS
    Verifying components ... WORKS
    Log on to your WHS Server 2011 [ServerName] ... WORKS
    Downloading the connector software ... WORKS

    And the failure occurs at the next step, "Connecting your computer to the network".

    I have verified that both the server and the client have valid IPv4 addresses. I have also tried again by disabling IPv6 on both machines and giving installation another shot. No joy.

    /Rik

     


    Richard Parker http://richard.parker.name


    Are there any manually set rules or exceptions in your Router?

    I'm asking because I'd made some changes to my WHS v1 network configs in the router, which I forgot about.
    So when backup restores failed at later parts of the cycle (unknown or unexpected error) and I couldn't figure it out why this was happening I became quite frustrated.

    By chance I looked through settings in the Router, I removed all manual settings and returned to automatic setups.
    Backup restores as intended!

    Any of this apply to your network?


    One WHS v1 machine in the basement with a mixed setup of harddrives in and outside the storage pool.
    Friday, February 18, 2011 9:40 AM
  • And the failure occurs at the next step, "Connecting your computer to the network".


    It could be DNS, or DHCP.  Are you using your router for DHCP?  Are all computers on your network pointed to the same source for DNS?

    D.W.
    Friday, February 18, 2011 1:59 PM
  • Yes, all using the same router for DHCP and no other clients on the network configured as DHCP servers. DNS addresses confirmed as being the same (the router address) on client and servers...


    Richard Parker http://richard.parker.name
    Friday, February 18, 2011 2:03 PM
  • Well, i'm pretty much out of ideas.  Your DNS should be an address from your ISP though.  Not the address of the gateway.  I've seen several threads with this same problem though, so maybe you should submit a bug report.

    Sorry I couldn't be of more help.


    D.W.
    Friday, February 18, 2011 4:50 PM
  • Well, i'm pretty much out of ideas.  Your DNS should be an address from your ISP though.  Not the address of the gateway.  I've seen several threads with this same problem though, so maybe you should submit a bug report.

    Sorry I couldn't be of more help.


    D.W.

    Thanks for your input, it is appreciated. 

    The router itself forwards DNS requests it receives through to the ISP's DNS servers, so that shouldn't really be the problem...

    Rik


    Richard Parker http://richard.parker.name
    Friday, February 18, 2011 5:13 PM
  • I don't think so; this is a new router and there have been no custom exceptions/routing rules configured.

    It might help if I knew exactly what part of the 'connecting' process it was failing on, because clearly it does start out with a connection because it retrieves the server settings and validates the password etc.

    Not sure what else to try, besides giving up on the RC and moving back to WHS v1.


    Richard Parker http://richard.parker.name
    Friday, February 18, 2011 5:14 PM
  • Well the client sees the server, and is even able to download the connector software from it.  And then if you get past the part where it asks for the server password, they are for sure talking to each other.  It's gotta be something with the final address resolution.  I had the same problem in a virtual environment before I put the beta on a machine.  The problem there was the client and server were both configured with the same IP address (since it was a virtual internal network).  So I just had to assign one a unique IP address.  Not sure if that could be the case here or not.  I don't see a router letting that happen.
    D.W.
    Friday, February 18, 2011 6:13 PM
  • I was browsing through and found your entry with problems related to installing the connector software on any windows 7 64 bit machine. I can report that, I am also finding issue with a similiar setup. I am running 2 virtual machines, one for the server and the other running an evaluation edition of windows 7. The connector software fails to install on the windows 7 VM in exactly the same way you have described on your Windows 7 Client PC's. I am using the latest Windows Home Server 2011 version of the server software. There are no network or password issues, get to 95%, rolls back and displays an error message. I'm sorry that I can't post any resolution to this problem though, I was hoping somebody else might be able to help with that.

    Best Regards

    Brian

    Tuesday, February 22, 2011 12:30 AM
  • If your working with VM's, make sure that your IP addresses are not shared on the virtual machines.  That was the issue I was having.
    D.W.
    Tuesday, February 22, 2011 1:24 AM
  • I was wondering if you might be able to expand on the issue you were having please? I'm using Hyper-V to do the virtualization btw, I'm not very sure what you may mean by shared IP Addresses, the addresses on each of the VM's is different if that's what you mean, still having problems.

    Best Regards

    Brian

    Tuesday, February 22, 2011 1:41 AM
  • So how is your network set up with the VM's?  Are you running a virtual internal network?  Or are the computers all on the same network?
    D.W.
    Tuesday, February 22, 2011 1:53 AM
  • This is the same problem I am having with the wife's laptop.  She has Windows 7 Pro 32-bit and she was previously connected to my WHS v.1 machine.  I uninstalled the connector, restarted, installed the new v.2 connector and ran in to the error.  After checking some of the settings, I found that her computer wasn't on the proper workgroup.  I changed that, rebooted and still nothing.

    I would love to find a solution for this issue.

    Tuesday, February 22, 2011 4:14 AM
  • Hi all

    Just wanted to post an update to this issue. As I still haven't found a resolution, and it seems at least two other folks have experienced the same/similar issue, I decided to start looking through the (rather large!) log files that have been generated.

    Mostly the log is all 'successes', however I did find:

    MSI (s) (4C:BC) [08:39:11:800]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1603 
    Info 1603.The file C:\Program Files\Windows Server\Bin\CertManaged.dll is being held in use.  Close that application and retry.
    MSI (s) (4C:BC) [08:39:11:809]: Product: Windows Home Server 2011 Connector. The file C:\Program Files\Windows Server\Bin\CertManaged.dll is being used by the following process: Name: ClientDeploy , Id 2920.
    MSI (s) (4C:BC) [08:39:11:813]: Product: Windows Home Server 2011 Connector. The file C:\Program Files\Windows Server\Bin\CertManaged.dll is being used by the following process: Name: SharedServiceHost , Id 7704.
    MSI (s) (4C:BC) [08:39:11:818]: Note: 1: 1321 2: C:\Program Files\Windows Server\Bin\CertManaged.dll 3: 5 
    MSI (s) (4C:BC) [08:39:11:822]: Verifying accessibility of file: CertManaged.dll
    MSI (s) (4C:BC) [08:39:11:828]: Note: 1: 2205 2:  3: Error 

    I also found:

    [7728] 110218.083440.5848: ProviderFramework: Information: [0] : EndOpen indicated that the connection attempt failed: (EndpointNotFoundException) Could not connect to net.tcp://127.0.0.1:65532//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistration. The connection attempt lasted for a time span of 00:00:01.0020573. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:65532. ==> (SocketException) No connection could be made because the target machine actively refused it 127.0.0.1:65532

    ... Which indicates a socket connection failure on the local machine.

    This morning I attempted a re-install, this time I disabled anti-virus (Bullguard) and Bullguard's firewall. In addition, I disabled Windows Firewall on both the client and the server, and the installation succeeded.

    In hind sight I should have tested the install by disabling one feature at a time, however as I was in a rush I decided to give this a go. I wondered if the cause of the "CertManaged.dll is being used by another process" could possibly be related to the anti-virus program, which led me on a crusade of disabling everything, everywhere :)

    #Hope this helps,

     

     

    Rik.


    Richard Parker http://richard.parker.name
    Tuesday, February 22, 2011 10:04 AM
  • I just wanted to provide a further update.

    It seems that Bullguard anti-virus & firewall isn't happy to work with the WHS Vail Launchpad/connector.

    Even with Bullguard firewall & antivirus disabled, the computer will always report that the Vail server is offline. Something about the product seems to interfere with Vail.

    If I uninstall Bullguard, reboot and login, the client is able to connect to the Vail server without any issue at all.


    Richard Parker http://richard.parker.name
    Tuesday, February 22, 2011 12:19 PM
  • I am having a similar issue except when the laptop reboots after installing the connector it says it needs a specific version of .net 4.  This is on a Windows 7 Home Premium laptop.  When it comes back to the desktop after reboot the user now has no user account and just an admin account with the .net 4 error.
    When in doubt empty the magazine...
    Tuesday, February 22, 2011 2:18 PM
  • I have a simular issue. I have 3 machines with same error. "An unexpected error has occurred", when I try to load WHS 2011 connector software. When I run the program on either of these 3 machines, it fails at same place, after you enter the server password. All 3 of these units are running Win 7 Ultimate 64 bit. 1 is a laptop, {dell} and 2 are PC's, 1 Intel system and other Gigabyte system. All 3 are running Avast Free edition. I have removed all other connector software, cleared registry of any entries, removed Program Files and directories and have tried all 3 in safe mode as well. I have a 4th unit, laptop, [HP] that also has Win 7 Ultimate 64, and Avast Free and it loaded fine, no issues. At wits end here...WHS wont work if you can't connect!

     

    Ricky

    Saturday, February 26, 2011 3:57 AM
  • My network setup is a very straight forward setup in Hyper-V. I have no problems whatso ever "seeing" the network between the 2 VM's and "seeing" the host network as well.

    I also checked the event log on the client after receiving the error from the failed connector install. I get event ID 11712 and the error shown is:

    Product: Windows Home Server 2011 Connector -- Error 1722. There is a problem with this Windows Installer package. A Program run as part of setup did not finish as expected. Contact your support personnel or package vendor. Action SetupMcConnector, location: C:\Program Files\Windows Server\Bin\seSetup.exe, command: *********?

    I would have thought that this error should be fairly conclusive. Also see my previous posts...

    Best Regards

    Brian

    Saturday, February 26, 2011 9:12 PM
  • I found the following details in the Microsoft Connect website if it is likely to be of any use to you you could try:

    "Please ensure the following services are running on your client: "Windows Media Center Receiver Service" and "Windows Media Center Scheduler Service". If not please start them manually (using the steps below) then retry installing the client connector software."

    Best Regards

    Brian

    • Proposed as answer by Rudeboouuy Monday, April 18, 2011 4:45 PM
    Tuesday, March 01, 2011 8:50 AM
  • I found the following details in the Microsoft Connect website if it is likely to be of any use to you you could try:

    "Please ensure the following services are running on your client: "Windows Media Center Receiver Service" and "Windows Media Center Scheduler Service". If not please start them manually (using the steps below) then retry installing the client connector software."

    Best Regards

    Brian


    This worked for me!!!! Thanks Brain, I was about to start pulling my hair out! I had disabled both those services to slim down the resources on my media center and because I don't have cable TV anymore, just the media center. After I enabled both those services the install completed successfully.

     

    Thanks again!!


    PS I don't think this is a network issue. I read about other people changing their workgroup names and DNS settings, yes for some people this may be a DNS issue but as previously stated, if you're getting to the point of entering the home server password your connection is fine. Also I have a very complicated home network, the majority of my computers are using a DHCP server and belong to a domain, and of course the home server is in a workgroup. Both the computers in my workgroup and in my domain have been able to install the connector software without issue, except for this.....
    Monday, April 18, 2011 4:48 PM
  • I've been having this issue since installing whs 2011 last night and finally decided to try re-setting the router and it worked. It gave both the whs and the administrating computer a different IPv4 address. Thanks for all the input from everyone.
    • Proposed as answer by Nate1148 Wednesday, April 20, 2011 12:58 AM
    • Unproposed as answer by Nate1148 Wednesday, April 20, 2011 12:59 AM
    Tuesday, April 19, 2011 1:45 PM
  • Hello.

    I was having the exact same issues and the work arounds did not work.

    I am subscribing to opendns through my router (dlink 655) and I am having local dns issues becuase of opendns ie. rdp no longer works with the computer name and I must use the local ip address, etc.

    So, i disabled opendns and left the primary and secondary ip address blank so they re-route back to my isp and the connector - connected first time.

    Hope this helps someone.

    Nate


    WHS Intel Dual Core 2.8 Gig, 2 Gig Ram. 1x500Gig Sata Drive 2 x 2 TB EARS Drive - Working Great!
    • Proposed as answer by Nate1148 Wednesday, April 20, 2011 1:06 AM
    Wednesday, April 20, 2011 1:06 AM
  • I found the following details in the Microsoft Connect website if it is likely to be of any use to you you could try:

    "Please ensure the following services are running on your client: "Windows Media Center Receiver Service" and "Windows Media Center Scheduler Service". If not please start them manually (using the steps below) then retry installing the client connector software."

    Best Regards

    Brian

    This one worked for me. I was having the issue on 2 PC's and manually starting these services allowed the installer to complete. Thankyou
    Sunday, May 15, 2011 12:21 AM
  • Hi
    I found another possible problem with the d#$%$d WHS 2011 connecter installation

    I also wasn't able to sucessfully install the connector (same error as mentioned above)
    but all suggested solution didn't helped

    Only after going through the Logfile manually I found this in the file ClientDeploy.log

    [5332] 110530.213853.7274: ClientSetup: Could not ensure NetTcpPortSharing service is Running: System.InvalidOperationException: Cannot start service NetTcpPortSharing on computer '.'. ---> System.ComponentModel.Win32Exception: The system cannot find the file specified
      --- End of inner exception stack trace ---
      at System.ServiceProcess.ServiceController.Start(String[] args)
      at Microsoft.WindowsServerSolutions.Common.ServiceUtility.ChangeObjectState(Methods method, ServiceController svc, DateTime deadline)
      at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(String serviceName, Int32 timeout)
      at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.PrepareClientTask.Run(WizData data)
    


    somehow the .newt 4.0 installation was broken but nobody seemed it necassery to inform the User!

    Reinstalling the Framework helped!!

    <sarc>

    Thanks Microsoft for showing the user the Information he needs to solve his problem!!
    The next "improvement" would be to ship it with the sourcecode so my Grandma can debug the software by herself

    </sarc>

    Monday, May 30, 2011 8:10 PM