locked
WHS Connector Fails to install: HS Discovery has problem RRS feed

  • Question

  • I installed an EX490 about a week ago and have been working through getting things set up. Overall, things have gone well.
    I installed an EX490 about a week ago and have been working through getting things set up. Overall, things have gone well.
    I installed an EX490 about a week ago and have been working through getting things set up. Overall, things have gone well.
    I recently installed a new HP EX490 and have succeeded (I think) in getting file sharing and system back-ups to work properly.  When I went to change the setup of my XP client so that it would wake up for back-ups I received an error message the "Home Server Discovery has encountered a problem and needs to close."  The next pop-up informs that installation could not be completed.

    (Client back-ups and file sharing seem to work properly.  The XP system wakes up for backups too.)

    I installed an EX490 about a week ago and have been working through getting things set up. Overall, things have gone well.
    In sequence, here's what the event viewer shows:

    MSInstaller Event 11728 HP MediaSmart Server 3.0 Update 1 Config Completed successfully
    HomeServer Warning Event 1794 Server ID is not set yet
    HomeServer Event 1817 WHS Connector started successfully
    HomeServer Event 1818 WHS Connector stopped successfully
    HomeServer Event 1817 WHS Connector started successfully
    Application Error Event 1000 Faulting application discovery.exe
    Application Error Event 1001 Fault bucket 1575794575

    The HS client setup log shows this:

    14.12.23 1/29/2010 Copying MSI from server to the local client temp location...
    14.12.23 1/29/2010 Verified: not 64-bit OS
    14.12.23 1/29/2010 Failure 2 while copying MSI from C:\DOCUME~1\Encoreps\LOCALS~1\Temp\~WindowsHomeServerConnector~\WHSConnector_x86.msi to C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\WHSConnector.msi
    14.12.23 1/29/2010 Using MSI from C:\DOCUME~1\Encoreps\LOCALS~1\Temp\~WindowsHomeServerConnector~\WHSConnector.msi
    14.12.23 1/29/2010 Major=5, minor=1, suite=256
    14.12.23 1/29/2010 Uninstalling old client...
    14.12.23 1/29/2010 Requested rerun setup after reboot: C:\DOCUME~1\Encoreps\LOCALS~1\Temp\~WindowsHomeServerConnector~\Setup.exe
    14.12.23 1/29/2010 Looking for product {21e49794-7c13-4e84-8659-55bd378267d5}: --> state=5
    14.12.23 1/29/2010 Discovered Windows Home Server Connector
    14.12.23 1/29/2010 Found incompatible Q client Windows Home Server Connector. Uninstalling {21e49794-7c13-4e84-8659-55bd378267d5}
    14.12.29 1/29/2010 Stopping tray.

    This continues until the bitter end where MSI installer returns error code 1603

    I don't know how to determine what went wrong and how to fix this.  Can I ignore the error if things appear to work properly?

    I noticed another post in this forum where files couldn't be copied from the server to the client during installation.  I checked for the presence of the files that are supposed to be in the WHS Connector folder on the server.  All are present.

    I haven't set up remote access yet, since I thought I should nail this down before opening up another battle front.

    Thanks and regards,

    Bob

    I installed an EX490 about a week ago and have been working through getting things set up. Overall, things have gone well.
    Monday, February 1, 2010 3:22 AM

All replies

  •   I installed an EX490 about a week ago and have been working through getting things set up. Overall, things have gone well.

    I recently installed a new HP EX490 and have succeeded (I think) in getting file sharing and system back-ups to work properly.  When I went to change the setup of my XP client so that it would wake up for back-ups I received an error message the "Home Server Discovery has encountered a problem and needs to close."  The next pop-up informs that installation could not be completed.

    (Client back-ups and file sharing seem to work properly.  The XP system wakes up for backups too.)

    In sequence, here's what the event viewer shows:

    MSInstaller Event 11728 HP MediaSmart Server 3.0 Update 1 Config Completed successfully
    HomeServer Warning Event 1794 Server ID is not set yet
    HomeServer Event 1817 WHS Connector started successfully
    HomeServer Event 1818 WHS Connector stopped successfully
    HomeServer Event 1817 WHS Connector started successfully
    Application Error Event 1000 Faulting application discovery.exe
    Application Error Event 1001 Fault bucket 1575794575

    The HS client setup log shows this:

    14.12.23 1/29/2010 Copying MSI from server to the local client temp location...
    14.12.23 1/29/2010 Verified: not 64-bit OS
    14.12.23 1/29/2010 Failure 2 while copying MSI from C:\DOCUME~1\Encoreps\LOCALS~1\Temp\~WindowsHomeServerConnector~\WHSConnector_x86.msi to C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\WHSConnector.msi
    14.12.23 1/29/2010 Using MSI from C:\DOCUME~1\Encoreps\LOCALS~1\Temp\~WindowsHomeServerConnector~\WHSConnector.msi
    14.12.23 1/29/2010 Major=5, minor=1, suite=256
    14.12.23 1/29/2010 Uninstalling old client...
    14.12.23 1/29/2010 Requested rerun setup after reboot: C:\DOCUME~1\Encoreps\LOCALS~1\Temp\~WindowsHomeServerConnector~\Setup.exe
    14.12.23 1/29/2010 Looking for product {21e49794-7c13-4e84-8659-55bd378267d5}: --> state=5
    14.12.23 1/29/2010 Discovered Windows Home Server Connector
    14.12.23 1/29/2010 Found incompatible Q client Windows Home Server Connector. Uninstalling {21e49794-7c13-4e84-8659-55bd378267d5}
    14.12.29 1/29/2010 Stopping tray.

    This continues until the bitter end where MSI installer returns error code 1603

    I don't know how to determine what went wrong and how to fix this.  Can I ignore the error if things appear to work properly?

    I noticed another post in this forum where files couldn't be copied from the server to the client during installation.  I checked for the presence of the files that are supposed to be in the WHS Connector folder on the server.  All are present.

    I haven't set up remote access yet, since I thought I should nail this down before opening up another battle front.

    Thanks and regards,

    Bob      

    You could try uninstalling the Connector software on that client, rebooting the client, then installing the newest version of the Console from the server (\\server\software\home server connector software).
    Monday, February 1, 2010 3:49 AM
    Moderator