locked
Connector Issues RRS feed

  • Question

  • I just purchased windows home server that includes power pack 1 (which as a result can't be uninstalled). the setup of the server side was basically fine. I'm able to remote into the server through one of my machines. now the issue is when i try to install the connector i get an error message after it downloads the content from the server (through http://server:55000/saying that there could be a potential virus. given the machine was just build that's virtually impossible. i try to proceed and it errors out by saying that the "sample.cab" file is corrupt. as of right now i can remote into the computer and access file share, but can't install the connector software and can't uninstall power pack 1 (which for many seems to be the issue). any ideas?
    Monday, July 6, 2009 9:07 AM

Answers

  • Do you mean i should move the entire Home Server Connector Software folder?  i tried that and then when i go to my home computers it can't find any of the software.  The contents of that folder are as follows:

    Folder: DOTNETFX20
    Folder: WindowsInstaller31
    setup.exe
    whs_connectorhelp.chm
    whsconnector.msi
    whsconnector_x64.msi
    whsconnectorinstall.exe
    whsversionupgrade.dll
    whsversionupgrade_x64.dll


    No not the entire folder, only the OEM folder (if one exists, since I have seen this message only in context with OEM add-ins, I thought this as a potential reason).
    If you don't have an OEM folder, was there a connector software installed on that client originating from an OEM device? If so, uninstall and remove the remains first.

    What happens, if you attempt to run setup.exe directly from the mentioned shared folder?
    Best greetings from Germany
    Olaf
    • Marked as answer by dtrip35 Monday, July 6, 2009 7:49 PM
    Monday, July 6, 2009 1:17 PM
    Moderator

All replies

  • This message comes, if the OEM puts in unsigned own packages.
    These can be found in the OEM folder below \\server\software\Home Server Connector Software.
    If you move that folder to somewhere else, the installation should work (also from that share).
    Best greetings from Germany
    Olaf
    Monday, July 6, 2009 9:25 AM
    Moderator
  • Olaf,
    Do you mean i should move the entire Home Server Connector Software folder?  i tried that and then when i go to my home computers it can't find any of the software.  The contents of that folder are as follows:

    Folder: DOTNETFX20
    Folder: WindowsInstaller31
    setup.exe
    whs_connectorhelp.chm
    whsconnector.msi
    whsconnector_x64.msi
    whsconnectorinstall.exe
    whsversionupgrade.dll
    whsversionupgrade_x64.dll


    Thanks

    Don

    Monday, July 6, 2009 9:38 AM
  • Do you mean i should move the entire Home Server Connector Software folder?  i tried that and then when i go to my home computers it can't find any of the software.  The contents of that folder are as follows:

    Folder: DOTNETFX20
    Folder: WindowsInstaller31
    setup.exe
    whs_connectorhelp.chm
    whsconnector.msi
    whsconnector_x64.msi
    whsconnectorinstall.exe
    whsversionupgrade.dll
    whsversionupgrade_x64.dll


    No not the entire folder, only the OEM folder (if one exists, since I have seen this message only in context with OEM add-ins, I thought this as a potential reason).
    If you don't have an OEM folder, was there a connector software installed on that client originating from an OEM device? If so, uninstall and remove the remains first.

    What happens, if you attempt to run setup.exe directly from the mentioned shared folder?
    Best greetings from Germany
    Olaf
    • Marked as answer by dtrip35 Monday, July 6, 2009 7:49 PM
    Monday, July 6, 2009 1:17 PM
    Moderator
  • No OEM folder, however i installed directly from setup.exe and that worked!  seems almost simple now, not sure what the intial problem was, but the workaround does the trick, thanks Olaf!
    Monday, July 6, 2009 7:49 PM
  • I also have this problem. I built the machine myself and used an OEM version of WHS from the same retailer. The WHS connector was working great on 10 machines, all 64 bit including SBS 2008, all have One Care running and are fully patched. Within week or two after the install, the connector stated that a new version was available and needed to be installed, when attempting to run this, the failure above is encountered first the warning that a virus might be in the file, then a failure that sample.cab cannot be found. Uninstalling the connector and rerunning it directly from the server\software\setup.exe using run-as administrator also does not work. Problem still exists, no known solution at this time.
    Tuesday, September 1, 2009 7:51 PM