Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Cannot Install Connector on WHS 2011 on one Windosw 7 64 bit computer RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Countless atempts at installing the WHS Connector on my Windows 7 64 bit desktop have all failed.  It has installed on my laptop, also running Window7 Professional 64 bit, so the problem would appear to be with my desktop.  I have read the posts by other people, and no-one seems to be having the problem I am experiencing.  The ClientCore.msi.log consistently shows the problem is the Backup Driver.  I have removed Rapport Trusteer as well as all the other possible things I can find, all to no effect.  Any help would be appreciated.

    The key part of the log appears below

    MSI (s) (D8:90) [16:06:33:430]: Created Custom Action Server with PID 1296 (0x510).
    MSI (s) (D8:78) [16:06:33:477]: Running as a service.
    MSI (s) (D8:78) [16:06:33:493]: Hello, I'm your 32bit Elevated custom action server.
    MSI (s) (D8:90) [16:06:34:179]: Executing op: ActionStart(Name=RollbackBackupDriver,,)
    MSI (s) (D8:90) [16:06:34:226]: Executing op: CustomActionSchedule(Action=RollbackBackupDriver,ActionType=1298,Source=C:\Program Files\Windows Server\Bin\BackupDriverInstaller.exe,Target=-u,)
    MSI (s) (D8:90) [16:06:34:241]: Executing op: ActionStart(Name=InstallBackupDriver,,)
    MSI (s) (D8:90) [16:06:34:257]: Executing op: CustomActionSchedule(Action=InstallBackupDriver,ActionType=1042,Source=C:\Program Files\Windows Server\Bin\BackupDriverInstaller.exe,Target=-i,)
    CustomAction InstallBackupDriver returned actual error code -536870397 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (D8:90) [16:06:36:160]: Note: 1: 1722 2: InstallBackupDriver 3: C:\Program Files\Windows Server\Bin\BackupDriverInstaller.exe 4: -i
    MSI (s) (D8:90) [16:06:36:191]: Note: 1: 2205 2:  3: Error
    MSI (s) (D8:90) [16:06:36:207]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722
    MSI (s) (D8:90) [16:06:36:223]: Note: 1: 2205 2:  3: Error
    MSI (s) (D8:90) [16:06:36:254]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
    MSI (s) (D8:90) [16:06:36:269]: Product: Windows Home Server 2011 Connector -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action InstallBackupDriver, location: C:\Program Files\Windows Server\Bin\BackupDriverInstaller.exe, command: -i

     

    Sunday, February 12, 2012 4:19 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    I'm glad I'm not the only one with this issue.  This has occurred since the Windows 2011 rollup update happened on the server around Feb 17 2012, and my Win7 x64 Ultimate client now just continues to pop up with a notification about the fact that it 'Cannot install the Connector updates' and then suggests you reboot.  I too found the same log you have found, and I believe the program its referring to which has not finished is the file c:\program files\windows server\bin\esSetup.exe.  I also looked in Device manager to find System Devices\Windows Server Solutions Computer Restore Driver which was missing due to me getting half way round to reinstalling the connector for it only to fail with that error.  I could still launch the Dashboard from the client, and even browse the backups, but when I selected to restore a file it would come up with a driver error.  I have since restored my client back to before the WHS update happened, so I do now have the entry in Device manager, but am still being prompted with the notification about it not being able to update the connector software.  From the server the client appears to be offline, so they're not communicating at all now.   Am guessing it was the rollup pack which has caused this, or .NET 4 which seems to also be a possibility, though I tried manually reinstalling this in all of my troubleshooting which didn't help.

    • Proposed as answer by Matthers Wednesday, February 22, 2012 4:49 AM
    • Unproposed as answer by Matthers Wednesday, February 22, 2012 4:49 AM
    Wednesday, February 22, 2012 3:16 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I think I have just fixed it, although was presented with a window after reboot which confused me.  Here's what i did:

    0. Disabled auto logon for my mediacenter user.  Had initially seen an error about this being able which prevented the update from taking place.  After disabling, it still couldn't perform the update, but thought I'd mention this as a step 0 of what i did.

    1. Deleted all temp files in %temp%.  Don't think this was necessary

    2. Deleted all temp files in c:\windows\temp.  Don't think this was necessary

    3. Stopped all services which began with Windows Server... on the client (Win7 Ultimate x64)

    4. Connected to WHS2011 http://servername/connect and downloaded the Connector exe file and ran it

    5. Half way through I noticed that the TSR was still in the taskbar alerting me about the connector having trouble so I killed this in task manager.  I think it was called ConnectorAlert.exe - sorry can't remember exactly what it was.

    When I did this, almost immediately the window got past the 80% section where it would always sit at before rolling itself back, and prompted me for a reboot.  Not sure if this was coincidence, and if the only thing required was to get rid of that notifier, but this is a blow by blow account of how it worked for me :)
    After rebooting, it auto logged itself in and then told me that the client already belonged to a different home server and I should uninstall the connector! 
    (How you are meant to uninstall the connector on 2011 is quite beyond me.  I never had anything in Add/Remove about it, couldn't find anything in the Uninstall registry key in HKLM\Software\Microsoft\Windows\Uninstall nor in the Syswow64 uninstall area either, and the Windows 7 cleanup utility didn't show anything either)

    It then logged me out.  So i logged in and all appears happy now, fingers crossed.  Really wouldn't have thought it would be too hard for MS to simply stop services before performing the update, but this, along with the killing of the connector notification appears to have done the trick.

    Hope others find this useful
    Matthers

    • Proposed as answer by Matthers Wednesday, February 22, 2012 5:04 AM
    Wednesday, February 22, 2012 5:03 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can you explain this part a bit more "After rebooting, it auto logged itself in and then told me that the client already belonged to a different home server and I should uninstall the connector! " Thanks Matthers.

    I'm not sure if its viable to apply the fix offered without knowing the actual cause for this issue.

    May be, a Microsoft Engineer can reply to this post and let us know, what exactly needs to be done and whatever caused it.

    Thanks.

    Friday, February 24, 2012 3:44 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    At last I have a working Home Server 2011 and a Windows 7 64 -bit computer, but to disappoint all who have read this thread it was only achieved by a new install of Windows 7, taking the opportunity to install the OS on an SSD.

    One potential solution I can offer is that I had exactly the same problem when I then went to connect my Windows 7 64-bit laptop to WHS.  I solved the problem in this case by deleting the laptop computer from WHS and then reran the connector and all was well.  I realise this will only work for situations where there has been a successful connection in the past.

    Thanks for the interest in my problem.

    lgcboy

    MichaelJ aka lgcboy

    Saturday, April 28, 2012 7:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    howdy Folks, I have also been having this issue since June when I built my home server and I found a very  unethical way around this. First backup you computer. I opened up the home server dashboard on my 32 bit windows 7 desktop and clicked on the "computers and backups" tab so that I could watch as the server connector made progress. then I initiated the installation of the home server connector on my laptop ( I was using a wired connection) however I don't think it will make a difference. I noticed that every other time that the connector had failed it showed on the server dashboard at about 90% that it was online and I could even see the properties of the laptop from the server dashboard. So I figured I would interrupt the installation as soon as the server connector installation got to about 90% and the computer properties were showing on the server dashboard. So at 90% I forced the computer to shutdown by holding the power button and guess what when I restarted my laptop the installation was complete and I was even able to backup the Asus laptop (64bit OS win 8 with media center pro). I hope this works for your guys.
    Saturday, December 8, 2012 5:11 AM