Sign in
Microsoft.com
 
Microsoft
 
 
 
Microsoft >
> 
> 
> 
Unable to install Home Server Connection CD

Unanswered Unable to install Home Server Connection CD

  • Tuesday, March 06, 2007 10:04 PM
     
     
    Sign In to Vote
    0

    I have used this WS Connector CD to setup one laptop w/o any issues. On the 2nd laptop, configured exactly the same hardware and software, I had a connection failure originally, (the laptop could see the SERVER but could not authenticate) I attributed this to having Windows OneCare and Defender also running on this laptop. In troubleshooting this issue, I have uninstalled all three products, 1. Windows OneCare 2. Windows Defender 3. Home Server Connector. Now I can not reinstall. I am recieving a fatal install error after starting the setup.exe icon. A window pops up:

    SETUP.EXE Fatal Application Exit

    CopyFile

    the only option is "OK" to exit.

    Any clues.

     This laptop is a Compaq M300 w/PII333 cpu w/ 256mb ram a 30gb harddrive running Windows XP Pro w/ SP2 and all updates.

     

     

All Replies

  • Wednesday, March 07, 2007 4:02 AM
    Moderator
     
     
    Sign In to Vote
    0
    Try running it from the \\SERVER\Software\ share.
     
  • Wednesday, March 07, 2007 7:01 AM
     
     
    Sign In to Vote
    0

    1. Check your %TEMP% directory - can you copy files into this directory (being logged on as the same user as tries to install the client). Maybe permissions are wrong, or something of this kind.

    2. Look for the file "whssetup.msi" or .dat in %TEMP% directory on your client. If you see one, look whether it is R/O. If it is, that's your problem - delete this file and repeat client install.

    3. Make sure that you can copy whssetup.dat from your CD to %TEMP%

    4. If it still does not work, look into the log %TEMP%\homeserverclientsetup.log - in the end of the file - and see what was the failure code at copy. Maybe this error code makes it clear what happens.

     
  • Saturday, March 10, 2007 6:56 PM
     
     
    Sign In to Vote
    0

    Hi Tom,

    Thanks for the reply. Although these shares \\SERVER\Software were visible, the "failed" install laptop could not authenticate. I even tried to create multiple user accounts with administrator rights that were also present on the WHS bos. I have eventually utilized and reinstalled XP Pro on a "spare" 30gb laptop drive and rebuilt a Vanilla Virgin XP Pro laptop which connected. I also needed to change the Windows Onecare firewall settings to allow a few programs/ports to be open. Both laptops are connecting ang backing up without issue.

    If only I could get the Recovery CD to recognize either laptop's NIC. A network driver discovery tool would be useful to backup the required network drivers to work with this CD. The ability to create a floppy/usb key for each system would be nice. I couldn't determine if it "the recovery CD" was trying to use Windows 2003 server NIC drivers or XP Pro. But this issue is for another THREAD or FORUM.

    Now to get the remote access for outside the Router setup

    Thank you again,

    Jim

     

     
  • Saturday, March 10, 2007 7:11 PM
     
     
    Sign In to Vote
    0

    Hi Sasha,

     Thank you for the reply. Although, I did not think to look in the %TEMP% directory for the install files, I did try to and did succeed to copy the Recovery CD contents to the "failed" laptop's hard drive. I also verified that the registry was free and clear of WHS console entries.

    As I have mentioned in another Reply, I attempted to utilize the WHS Recovery CD to restore this laptop as a "clone" of the laptop that is connecting without issue, but the Network drivers failed to load and the XP Pro drivers that I copied to floppy and the USB key also failed to be recognized by this Recovery CD (I wonder if they were supposed to be Windows 2003 drivers)

    but alas to continue with "Good Faith Testing" I have uninstalled Windows Defender and Windows OneCare products as well from this laptop; also to no avail. Everything else appears to work and function correctly, except the WHS Recovery CD loading.

    I have subsequently, "installed a spare" 30gb hard drive a rebuilt a Vanilla XP Pro install. Again after 1 day of updates, patches, service packs and the like from Microsoft. I again attempted the install. As it went before, the install worked correctly and was able to connect to the WHS system without issue.

    Remote access from outside the firewall and back to Recovery CD connection are left to be overcome....or at least researched in the FORUMS.

    Thank you

     
  • Saturday, May 19, 2007 3:22 AM
     
     
    Sign In to Vote
    0

     

     

    I have problems installing the connector to a "sick" desktop.

    It would be a excellent canditate for a restore test

    The HD is failing, and needs to be replaced.

    I have tried to install from the \\server\software share

    I get all of the way to the configuring back up part when it fails

     

    I have tried to install from a user account with no password and it fails

    I created a user name with the correct network password and still fails

     

    Any ideas?

     

     
  • Saturday, May 19, 2007 12:14 PM
     
     
    Sign In to Vote
    0
    Have you tried directly connecting to your router using a network cable?  This helped me out restoring a backup to my Dell D800 laptop.  It wouldn't restore wirelessly.


     
  • Saturday, May 19, 2007 1:20 PM
     
     
    Sign In to Vote
    0

    I am connected by network cable directly to the router. I saw other posts that said make sure the computer that I am trying to install the connector on is in the same workgroup. I have checked and it already was.

     

    Still trying

     

    I looked in the log and found this

     

    14.20.45 5/20/2007 Looking for product {21e49794-7c13-4e84-8659-55bd378267d5}:  --> state=-1
    14.20.45 5/20/2007 LOCATION_MSIEXEC: C:\WINDOWS\system32\msiexec.exe
    14.20.45 5/20/2007 LOCATION_WHSCLIENT_LOCAL_COPY: C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\WHSConnector.msi
    14.20.45 5/20/2007 LOCATION_LOG: C:\DOCUME~1\TPuckett\LOCALS~1\Temp\HomeServerClientMsi.log
    14.20.45 5/20/2007 LOCATION_MSIEXEC: C:\WINDOWS\system32\msiexec.exe
    14.23.52 5/20/2007 MSI returned 1602
    14.23.52 5/20/2007 MSI installer returned 1602
    14.23.52 5/20/2007 MSI returned cancellation code 1602 - rolling back via uninstall
    14.23.52 5/20/2007 Uninstalling old Q client
    14.23.52 5/20/2007 LOCATION_LOG: C:\DOCUME~1\TPuckett\LOCALS~1\Temp\HomeServerClientMsi.log
    14.23.52 5/20/2007 LOCATION_MSIEXEC: C:\WINDOWS\system32\msiexec.exe
    14.25.10 5/20/2007 MSI returned 0 for uninstallation
    14.25.10 5/20/2007 MSI un-installer returned 0
    14.25.10 5/20/2007 END: got to the end

     

     
  • Sunday, May 20, 2007 11:36 PM
     
     
    Sign In to Vote
    0
    Also make sure that the network segment is the same as the server - everything has to match, including the subnet mask.  i.e., 255.255.255.0 for everyone (or 255.255.0.0, etc).  I lost connectivity (and ability to backup using connector) because my subnet didn't match.  I could RDP and logon to the server, but couldn't get connector to bring up the WHS console.  Took me a while to remember I had changed the subnet so I could talk to a network appliance on a different subnet...
     
  • Monday, May 21, 2007 4:18 AM
     
     
    Sign In to Vote
    0

    That was not the problem, all of the machines are on the same subnet, becuase they are served by the same DHCP server ( The router)

     

    I finall had to give up and replace the HD on that machine, shortly I will try to install the connector software on the fresh install of XP.

    It will be interesting, if it works then.

     

    I replaced the HD, did my reinstall of XP, and then it installed easily.

     

     

     

     

     
  • Sunday, June 17, 2007 7:28 PM
     
     
    Sign In to Vote
    0

    I receive  the same error. Here is what the log file says when it fails. Does this mean anything?

     

    Thanks, Kevin

    --------

    Copying MSI from server to the local client temp location...
    13.42.19 6/17/2007 Failure 5 while copying MSI from S:\Home Server Connector Software\WHSConnector.msi to C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Home Server\WHSConnector.msi
    !!! Line 787 in file d:\qhsv1_rc\qhs\src\client\setup\setup.cpp :
    Fatal failure: CopyFile