none
WHS 2011 Connector Install Issues RRS feed

  • Question

  • I have replaced my exisiting WHS v3  (HP Media Center WHS Box) with self made WHS 2011 sever and  I am migrating my 5 home pcs/laptops  to the new server.   So far, I have succesully installed connector on two computers running Win 7 Home Premium.  These two computers seem to be working perfectly with the new server.  Backups are running and folder shares are working.

    Sadly, WHS Connector fails to complete installation on the other three computers (win7 home premium laptop, win7 home premium desktop, and win 7 ultimate desktop).  I do see the server in the workgroup and in network connections and can share files...

    When installing connector, I get past looking for home server... enter Server Password....  Then it stops... with the error  ..to the effect of ..."This system has an install in process or this system has a reboot scheduled"...  Of course I have rebooted all computers, and the server, as well as attempted to reinstall with firewall (mcaffee)turned off.  

    Any suggestions ..

     

    Monday, September 19, 2011 7:04 PM

All replies

  • Rainer,

    Can you check this key in the registry?

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

    if it is possible back up the key and then delete it.  Perhaps there is an operation orphaned in that key.  The setup likely is checking to see if its populated or not before continuing.


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Monday, September 19, 2011 7:23 PM
  • Thanks,

    This folder path does not exist in my registry

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations


    Rainer
    Tuesday, September 20, 2011 12:25 AM
  • Rainer,

    Can you take one more look? To be clear, the last value I believe is a dword not a folder.  So navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager and then on the right see if there is a value called "PendingFileRenameOperations". Delete it.

    You receive a "Setup has detected that another program requires the computer to reboot" error message when you try to install Visual Studio .NET or Visual Studio 2005
    http://support.microsoft.com/kb/830608


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Tuesday, September 20, 2011 10:31 AM
  • Dave, thanks for your help.  I will look again.   Im not at home now, I may have missed the entry value to the right that you described.  

    I did make some progress on 2 of the 3 computers based upon information posted by (eltoro1) on July 8 2011. After clearing registry of all traces of WHS, (removed .net4 which was already gone on one computer), ran a program called CCleaner which seems to have found and deleted dozens of orphaned .net4 references then rebooted and re-installed Connector from //server/connect.   This worked perfectly on two computers.  one computer was win 7 ultimate, the other win 7 home premium.  

    However this did not seem to work on a mini-laptop running win7 starter. 

    will look again at your suggestion to  navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager and then on the right see if there is a value called "PendingFileRenameOperations"

    Getting closer though.


    Rainer
    Tuesday, September 20, 2011 3:33 PM
  • Sounds good.  I am 99% sure clearing that value will resolve it for you.

     


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Tuesday, September 20, 2011 4:48 PM
  • Still do not see "pendingfilerrenameoperations" anywhere near the path you mentioned...

    still cannot connect on win7 starter

     

     

     


    Rainer
    Wednesday, September 21, 2011 12:40 AM
  • Rainer,

    I was mistaken in that the value is a multi-string value but the location and name in the registry is correct.  Two ways we can check:

    1. Copy this script into notepad and save as check.vbs, save to desktop.  From elevated command prompt on the starter machine run c:\users\yourdesktop>cscript.exe check.vbs

    http://blogs.msdn.com/b/tommills/archive/2008/08/15/a-handy-wmi-script-for-checking-for-pending-file-rename-operations.aspx

    What are the results?

    2. From the starter machine export the regeistry key from Session Manager. Trim out the first pragraph which should only the top level from session manager folder and paste in here.

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager]

     


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Wednesday, September 21, 2011 10:46 AM
  • Rainer,

    Any update on issue?

     


    Dave Guenthner [MSFT] This posting is provided "AS IS" with no warranties, and confers no rights. http://blogs.technet.com/b/davguents_blog
    Thursday, September 22, 2011 10:08 PM
  • All,

    My issue was similar ... but my installation would get as far as saying it could take "30 minutes to install" ... and that's "all she wrote" ...

    I tried a lot of stuff to fix the problem. But i won't bore you with the 2 hours of debug. :-( 

    Anyway, the upshot is that the Connector install log kept indicating that a .Net 4.0 registry read failed.

    I checked the installed software and I only had the .Net 4.0 client.

    So I decided to manually install the full .Net 4.0 from the Microsoft site. Ran all the updates for .net 4.0. Restarted thae computer ... and ...

    The connector blew thru the install and I am online with my (home built) WHS 2001.

    The system with the problem was a home built HTPC, Windows 7 Pro 32-b.

    I hope this helps someone :-)

     



    • Edited by Aussie_1 Monday, October 31, 2011 12:32 AM
    Saturday, October 15, 2011 8:54 PM
  • This solution worked great.

    I used Registry first aid 8.2 to find and edit the substrings.

    Thanks Dave and Ken

    Saturday, June 30, 2012 6:11 PM
  • This worked like a charm for me.  Thanks!  On my machine though (Windows 7 Home Premium) I also had to delete the keys from [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager] and [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\Control\Session Manager].  It didn't work until I also deleted the values out of those two folders before it'd work, so I'd suggest also taking a look in there (if you have them) and deleting them too.
    Wednesday, April 30, 2014 1:10 PM