Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Connector install hangs at 68% RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Did manual install of Vail Refresh on new build server system. Installed network drivers as requested by Vail. Server joined LAN without problem. Started to install Connector software from the server and all appeared to go well: one restart, continued to 68% and hung. FIrst time this happened, I cancelled the install and this appeared to screw up Vail on the server (it wouldn't load). Did fresh install of Vail, then got same error with Connector install. The first time I used Firefox; the second, IE.

    Suggestions/workarounds?

    Monday, August 30, 2010 9:51 PM

Answers

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Is it perhaps due to the following issue from the initial Vail version? My server BIOS is set to GMT+1. Should I reset the BIOS as described below and do a fresh install of Vail on the server?

    Issue

    After installing and configuring Windows Server “Vail”, the server does not work properly or you cannot connect computers to the server.

    Description

    This issue occurs when the following conditions are met:

    ·      The certificate is used to authenticate between components on the server or when connecting computers to the server.

    ·      The BIOS clock on the server is wrong or the BIOS clock is right but the installation takes place in a time zone located east of Pacific Standard Time (PST), between PST and the date line.

    Solution

    Before you install Windows Server “Vail”, set your BIOS clock to match the time and date for the Pacific Time Zone (PST) regardless of where you are located in the world. After successfully installing Windows Server “Vail” and joining client computers, do not reset the time, date, and time zone on the Dashboard for another day.

    If you do not set your server time to PST, you should not use the server or connect computers to it until the number of hours pass that equals the difference between your time and PST.

    Monday, August 30, 2010 10:21 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I do not think your time zone is the issue.

    On the Vail Beta Refresh I left my clock at NZT and did not have issue's with either the install or loading the connector on the clients. The clients were connected immediately after the server install with no delay as per beta 1. The only delay was to run windows update.

    Are there any clue's in the server or client event logs as to what happened. Installing the connector should not require a reboot of either server or client. Are you certain the server install was fully completed. Could it still have been going through the multiple restarts required to complete the server install when the client install was attempted?.

    Dave

    Tuesday, August 31, 2010 12:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Could it still have been going through the multiple restarts required to complete the server install when the client install was attempted?

    Maybe this is the issue. The server install stopped with an error saying that there was no network connection. This was correct, because I do the install using the tv as monitor, and the router is downstairs. I shut down the server, took it downstairs and connected it to the router. I then logged on via a wireless laptop to begin the Connector install.

    I have now reinstalled Vail while connected to the router. I got past the step where I had to choose a server name and password, as well as applying regional settings. When I next looked, the progress bar indicating "finishing installation" was at 68% (curiously the same point as the Connector setup on my client laptop). Shortly after there was a BSOD. I restarted the server, it booted into Vail, then said something had gone wrong with the installation and I should re-do it.

    I have the error logs from this last error message, but I have no idea where to start looking in them, or what I should be looking for!

    Thanks for suggestions.

    • Edited by D0gg3d Tuesday, August 31, 2010 12:40 PM New errors
    Tuesday, August 31, 2010 6:26 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Did the BSOD give an error number and text that you can search for. Google may be your friend!.  If you post the error number and text here it may help with the diagnosis.

    Dave 

    Wednesday, September 1, 2010 12:31 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Try to install Microsoft .NET Framework 4 in de language of your clients operating system.
    After that try to install the connector software.

    This works fine for me.

    Thursday, September 2, 2010 3:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Try to install Microsoft .NET Framework 4 in de language of your clients operating system.
    After that try to install the connector software.

    This works fine for me.


    Per the quote above, I followed the procedure on the following thread and it worked for me.
    It ensured the .NET framework was functioning, I reran the connecter setup after and all was good.
    https://connect.microsoft.com/WindowsHomeServer/feedback/details/601894/whs-vail-connector-software-new-referesh-edition-fails-to-install-on-client-pc

    • Proposed as answer by rich_wa Friday, October 29, 2010 3:22 AM
    • Marked as answer by Ken WarrenModerator Saturday, October 30, 2010 12:50 PM
    Friday, October 29, 2010 3:21 AM