locked
WHS Connector for Win7 64bit RRS feed

  • Question

  • I cannot install the connector software on my Gateway running windows 7 64bit. Keep getting error message "
    Could not open key: UNKNOWN\Components\7F0DB2FC1AA21C343B116E18F2BA4181\49794E1231C748E4689555DB7328765D. Verify that you have sufficient access to that key, or contact your support personnel." Went to regedit, cannot do anything with the 49794E1231C748E4689555DB7328765D subkey, rename, delete or open - access is denied (5). I checked permissions on the root key 7F0DB2FC1AA21C343B116E18F2BA4181 and administrator and 'user' have full control over this key and subkeys. What next? Doesn't matter if i boot to OS or in safe mode
    pdkwins
    Saturday, January 9, 2010 2:07 AM

Answers

  • You could try to download the installer file (or copy the folder \\yourservername\software\Home Server Connector Software) and run setup as Administrator (either from context menu or from a cmd prompt started As Administrator).
    Eventually delete the key (it seems to belong to backupapi.dll), before starting over. Here it is located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\7F0DB2FC1AA21C343B116E18F2BA4181\49794E1231C748E4689555DB7328765D with full control to Administrators and System.)
    Best greetings from Germany
    Olaf
    Saturday, January 9, 2010 11:44 AM
    Moderator

All replies

  • You could try to download the installer file (or copy the folder \\yourservername\software\Home Server Connector Software) and run setup as Administrator (either from context menu or from a cmd prompt started As Administrator).
    Eventually delete the key (it seems to belong to backupapi.dll), before starting over. Here it is located in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Components\7F0DB2FC1AA21C343B116E18F2BA4181\49794E1231C748E4689555DB7328765D with full control to Administrators and System.)
    Best greetings from Germany
    Olaf
    Saturday, January 9, 2010 11:44 AM
    Moderator
  • Just checking, do you have whs pp3 installed?
    Monday, January 11, 2010 9:25 AM
  • I have the exact same error message trying to update Home Server Connector.  Unfortunately I uninstalled the connector already, so I'm at a loss as to what to do from here.  Trying to install via server:55000 gives me an ACL IIS access denied error.  I have PP3 installed.
    Thursday, January 27, 2011 6:23 AM
  • Sorry for delay, the half finished answer was stuck in a hidden window on my computer since some days ;-)

    Does the Connector folder still exist in above share?
    Can you access it from Windows Explorer and run setup.exe from here?

    If both is the case, your IIS configuration is eventually messed up.

    Check the event log of the server for error messages, explaining Access denied errors (could be as well a failing disk with the share on it).

    You could try uninstalling Power Pack 3, which would rollback to the status of PP2 (unless your machine was installed natively with PP3) and apply subsequent updates again.

    Other than that the only option I would see here is a server reinstall.

    Best greetings from Germany
    Olaf

    Monday, January 31, 2011 3:28 PM
    Moderator
  • I experienced the same issue after the 1/2611 update.  My WHS would not work with all of the computers on my home network.  After applying all of the fixes found on the internet, I could not reinstall the Connector.  I disconnected my modem and successfully installed the Connector.  As soon as I reconnected the modem to the internet, the Connector could not be accessed.  That meant the problem was with the internet connection so I reconnected my modem, opened my Vipre history file,  and watched as I ran the Connector setup.  The installation proceeded to the point of discovering the WHS and the "discovery.exe" was repeatedly "blocked" before the error message appeared on the screen to try later.

    Part of the installation of the Connector is a search with a file "discovery.exe"  that was being blocked by my Vipre firewall.  Adding "discovery.exe" to my firewall Exceptions list solved the problem. 

     

    I am posting this just in case this "discovery.exe" block might help others.

    Thursday, February 3, 2011 9:32 PM
  • Yes, 3rd party firewalls often cause hard to discoverable errors.

    So disabling or better uninstalling them to sure get rid of any filter driver would be always a method to proof if this is the culprit.

    Best greetings from Germany
    Olaf

    Saturday, February 5, 2011 3:25 PM
    Moderator