locked
Vail RTM problem - Unable to install Connector client, fails after 95% RRS feed

  • Question

  • I'm unable to install the Windows Home Server 2011 Client Connector. After about 95% of the install it stops and starts to rollback. I've tried disabling the firewall and virus protection and still no-go:

    Here are the errors I saw from the logs (incoming wall-of-text):

    From ClientDeploy.log:

    [1812] 110410.151719.8322: ClientSetup: Install package C:\Windows\Temp\Client Deployment Files\ClientCore.msi
    [1812] 110410.151719.8622: ClientSetup: Running MSI: C:\Windows\Temp\Client Deployment Files\ClientCore.msi SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* REBOOT=ReallySuppress
    [1812] 110410.151928.2390: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
      at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
      at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
    [1812] 110410.151928.2390: ClientSetup: RunMsi returned error: RetCode=1603
    [1812] 110410.151928.2390: ClientSetup: Failed to install C:\Windows\Temp\Client Deployment Files\ClientCore.msi

    From ClientCore.msi.log:

    MSI (s) (EC:E8) [15:18:51:314]: Executing op: ServiceControl(,Name=ServiceProviderRegistry,Action=1,,)
    MSI (s) (EC:E8) [15:18:51:974]: Executing op: ActionStart(Name=SetupMcConnector,,)
    MSI (s) (EC:E8) [15:18:52:044]: Executing op: CustomActionSchedule(Action=SetupMcConnector,ActionType=9234,Source=C:\Program Files\Windows Server\Bin\esSetup.exe,Target=**********,)
    CustomAction SetupMcConnector returned actual error code -2147024891 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (EC:E8) [15:18:52:644]: Note: 1: 1722 2: SetupMcConnector 3: C:\Program Files\Windows Server\Bin\esSetup.exe 4: ********** 
    MSI (s) (EC:E8) [15:18:52:664]: Note: 1: 2205 2: 3: Error 
    MSI (s) (EC:E8) [15:18:52:684]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1722 
    MSI (s) (EC:E8) [15:18:52:694]: Note: 1: 2205 2: 3: Error 
    MSI (s) (EC:E8) [15:18:52:704]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
    MSI (s) (EC:E8) [15:18:52:714]: Product: Windows Home Server 2011 Connector -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SetupMcConnector, location: C:\Program Files\Windows Server\Bin\esSetup.exe, command: ********** 
    
    Action ended 15:18:52: InstallFinalize. Return value 3.
    MSI (s) (EC:E8) [15:18:52:784]: User policy value 'DisableRollback' is 0
    MSI (s) (EC:E8) [15:18:52:814]: Machine policy value 'DisableRollback' is 0

    From SharedServiceHost-ClientSystemServiceConfig.log:

    [2928] 110410.151841.6035: ProviderFramework: Information: [0] : Address: [net.tcp://stebbi-hs:6602/Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInMetadataProvider/Microsoft.WindowsServerSolutions.AddinInfrastructure.IAddInMetadata]
    [2928] 110410.151841.6035: ProviderFramework: Information: [0] : Binding: [net.tcp]
    [2928] 110410.151841.6045: ProviderFramework: Information: [0] : Identifier: [Microsoft.WindowsServerSolutions.AddinInfrastructure.AddInMetadataProvider]
    [2928] 110410.151841.6045: ProviderFramework: Information: [0] : ProviderEndpointBehavior.AllowedConnectionType: [AllowRemoteAccess]
    [2928] 110410.151841.6045: ProviderFramework: Information: [0] : ProviderEndpointBehavior.EndpointCredentialType: [Machine]
    [2928] 110410.151841.6045: ProviderFramework: Information: [0] : RequiredImpersonationLevel: [Identification]
    [2928] 110410.151841.6055: PfBinding: Information: [0] : Assigning certificate to X509CertificateInitiatorClientCredential.
    [2928] 110410.151841.6085: ProviderFramework: Information: [0] : factory impersonation level is: [Identification]
    [756] 110410.151841.6195: Services: Information: [0] : OnStart: service "providers_system" ProviderServiceBase.OnStart finished. (ExitCode 0)
    [756] 110410.151841.6865: ProviderFramework: Information: [0] : ProviderConnector: Received connection
    [756] 110410.151841.6865: ProviderFramework: Information: [0] : ProviderConnector: Successfully connected for Microsoft.WindowsServerSolutions.AddinInfrastructure.IAddInMetadata
    [2400] 110410.151842.5865: Services: Information: [0] : OnStart: service "initMonitor" starting up.
    [2400] 110410.151842.5865: Services: Information: [0] : OnStart: service "initMonitor" WssgServiceBase.OnStart finished. (ExitCode 0)
    [2840] 110410.151856.8266: Services: Information: [0] : OnStop: service "initMonitor" stopping. (ExitCode: 0)
    [2400] 110410.151858.0266: ProviderFramework: Information: [0] : OnStop: service "providers_system" stopping.
    [2400] 110410.151858.0466: ProviderFramework: Information: [0] : AutoReconnecter: connection closed.
    [4456] 110410.151858.0466: SharedServiceHost: Information: [0] : Exiting with code 0
    [4456] 110410.151858.0466: SharedServiceHost: Information: [0] : ==========================================================
    [756] 110410.151902.4906: ProviderFramework: Information: [0] : AutoReconnecter: m_co faulted.
    [756] 110410.151902.4906: ProviderFramework: Information: [0] : AutoReconnecter: connection closed.
    [756] 110410.151902.4906: ProviderFramework: Information: [0] : _OnDisconnected.
    [756] 110410.151902.4906: ProviderFramework: Information: [0] : _CoreDisconnected is called.
    [2764] 110410.151902.4906: ProviderFramework: Information: [0] : PfErrorHandler: IGNORING WCF internal exception: (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (IOException) The write operation failed, see inner exception. ==> (CommunicationException) The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'. ==> (SocketException) An existing connection was forcibly closed by the remote host
    [2400] 110410.151906.4326: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
    [2840] 110410.151910.4446: ProviderFramework: Information: [0] : AutoReconnecter: m_co faulted.
    [2764] 110410.151910.4446: ProviderFramework: Information: [0] : EndOpen indicated that the connection attempt failed: (EndpointNotFoundException) Could not connect to net.tcp://stebbi:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry. The connection attempt lasted for a time span of 00:00:04.0120069. TCP error code 10061: No connection could be made because the target machine actively refused it [2001:0:5ef5:79fd:3c43:1ac4:2a2a:6901]:6602. ==> (SocketException) No connection could be made because the target machine actively refused it [2001:0:5ef5:79fd:3c43:1ac4:2a2a:6901]:6602
    [2400] 110410.151910.4446: ProviderFramework: Information: [0] : ProviderRegistryProxy: connection attempt failed.
    [2840] 110410.151915.0166: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
    [756] 110410.151919.0583: ProviderFramework: Information: [0] : AutoReconnecter: m_co faulted.
    [4788] 110410.151919.0583: ProviderFramework: Information: [0] : EndOpen indicated that the connection attempt failed: (EndpointNotFoundException) Could not connect to net.tcp://stebbi:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry. The connection attempt lasted for a time span of 00:00:04.0417068. TCP error code 10061: No connection could be made because the target machine actively refused it [2001:0:5ef5:79fd:3c43:1ac4:2a2a:6901]:6602. ==> (SocketException) No connection could be made because the target machine actively refused it [2001:0:5ef5:79fd:3c43:1ac4:2a2a:6901]:6602
    [2840] 110410.151919.0583: ProviderFramework: Information: [0] : ProviderRegistryProxy: connection attempt failed.
    [2400] 110410.151922.7010: ProviderFramework: Information: [0] : ProviderRegistryProxy: Creating proxy for AutoReconnecter.
    [2928] 110410.151926.7570: ProviderFramework: Information: [0] : AutoReconnecter: m_co faulted.
    [4788] 110410.151926.7570: ProviderFramework: Information: [0] : EndOpen indicated that the connection attempt failed: (EndpointNotFoundException) Could not connect to net.tcp://stebbi:6602//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistry. The connection attempt lasted for a time span of 00:00:04.0560072. TCP error code 10061: No connection could be made because the target machine actively refused it [2001:0:5ef5:79fd:3c43:1ac4:2a2a:6901]:6602. ==> (SocketException) No connection could be made because the target machine actively refused it [2001:0:5ef5:79fd:3c43:1ac4:2a2a:6901]:6602
    [756] 110410.151926.7570: ProviderFramework: Information: [0] : ProviderRegistryProxy: connection attempt failed.
    
    Sunday, April 10, 2011 3:36 PM

Answers

  • Hello,

    Thank you for working offline with me to get you the log files for this issue.  Hopefully this thread and my answer can become the definitive thread here.  After reviewing with the developers, it seems that your password contains a set of special characters.  This is a bug (of feature if you will) that for joining clients your administration password must not contain special characters.  While it's impossible for us to see what your password is via the log files (by design), it would appear that you use a " or a \ in your password.  This is a known bug (or feature) that we'll be fixing (removing) in upcoming SE update releases.  which UR it fits into is still TBD.  As a work around, temporarily set your admin password to something else without these special characters, add the computer and then feel free to set it back after you have added the computer.

    Hope this helps with the issue,

       Sean

    Friday, April 15, 2011 8:28 PM
    Moderator

All replies

  • I have just spent the past 2 days getting my WHS 2011 up and running. On each machine, getting the connector software (now the launchpad and the dashboard) to install was a problem. On each one, the problem seemed different, and I worked my way through each client, and now have all 6 (5x Win7(4 x64, 1 x86) ,1x XP) up and connected and backing up properly.

    My Setup - WhiteBox Intel E4500, 2Gb RAM, 4 internal HD - 3x500GB, 1x1TB. Running WHS v1 flawlessly for the past 2 years since its release. Backed up all the shares and performed a clean WHS 2011 install to primary 500GB drive, then added 3 other HD for Storage and additional 1TB External drive for Server Backup.

    Before I even tried installing the Connector Software, I ensured that all basic networking was working properly. The WHS v1 Connector Software had been removed, and the users were already set up on the WHS 2011 server (matching passwords), so I verified I could access Shares directly from Server (by browsing with explorer) prior to Connector installation. The first Win7 x64 machine went smoothly, but the next gave many "Unknown" errors, and only by removing/re-installing/rebooting many times was I able to get it going. I was able to get a second Win 7 x64 connected with seeming no reason why it now worked. On the next, I tried a fix I found on this forum to add the ip address of the server (mine was set static) to the hosts file. This seemed to work on that one, but not on the next. Then, just trying different things I got another to install by downloading the connector install software to the desktop instead of running it from there instead of from IE (I closed IE after the download). That also seemed to work on the last of the Win 7, but the XP continued to give me grief. This time the problems were different, in that after I did get the software installed, the Launchpad would fail to login after reboot (tried multiple times), and no communication with the Server was possible - from a command box I could ping the router, and the printer, but not the Server - doubly strange because the server would respond to a ping from another system. I suspect a Server reboot might have fixed, but since a Server Backup was in progress, instead I opted to try using a wired connection instead of the wireless connection I had been using. Didn't even need a reboot - as soon as I plugged the wire in, the Launchpad Connected to the Server and all was good.

    So, what to try...

    Put the Server on a static IP. Make sure network connectivity is good - can you browse the shares.

    Add the Server ip to the hosts file on the client system.

    After using IE to browse to http"//server/connect, download the connector installation file to the desktop, close IE, then run the installer from there.

    Use a wired connection if possible.

    Good Luck.

    JohnBrown

    Halifax, NS

     

    Sunday, April 10, 2011 8:09 PM
  • Sorry, I forgot to mention that at one point I enabled "HomeGroup" functionality. I suspect there must have been a conflict with those access settings and the settings I set on the shares, because all the clients immediately had problems accessing shares they had previously been accessing without issue. I could access the Music and Pictures folders though, so it wasn't a Server access problem. I removed the Server and the systems from the Homegroup, and proper access was restored.

    So definitely try it without a Homegroup if it makes a difference.

    Good Luck

    jb

     

    Sunday, April 10, 2011 8:28 PM
  • Thanks for the replies. I'll try some of this and see if I can get things rolling. I'll keep this thread posted on my progress. It seems to me though that with all the posts on Connector installation problems that MS needs to deliver a fix. I had no problems at all with WHSv1 connector installation, be it an XP, Vista or Win7 machine i was instlaling it to.

    Monday, April 11, 2011 9:11 AM
  • Well I tried your suggestions and no dice :( From the logs it seems like I'm running into some sort of wcf error. The setup (SharedServiceHost log) seems to be trying to access the machine itself but it is not accepting the connections. At first I thought it was a firewall or antivirus issue but having disabled both I have eliminated that. Does anyone have any ideas? Someone from MS?

    Monday, April 11, 2011 11:52 PM
  • Hello,

    Thank you for working offline with me to get you the log files for this issue.  Hopefully this thread and my answer can become the definitive thread here.  After reviewing with the developers, it seems that your password contains a set of special characters.  This is a bug (of feature if you will) that for joining clients your administration password must not contain special characters.  While it's impossible for us to see what your password is via the log files (by design), it would appear that you use a " or a \ in your password.  This is a known bug (or feature) that we'll be fixing (removing) in upcoming SE update releases.  which UR it fits into is still TBD.  As a work around, temporarily set your admin password to something else without these special characters, add the computer and then feel free to set it back after you have added the computer.

    Hope this helps with the issue,

       Sean

    Friday, April 15, 2011 8:28 PM
    Moderator
  • Im happy to inform you that the install worked like a charm after I changed the administrator password. Thanks a lot for your help Sean!
    Friday, April 15, 2011 11:21 PM
  • I'm having the same issue, changing the admin or user password does not fix it.

    The connector installation goes to 95% and then rollbacks.

    Here is what I see in the logs :

    CustomAction RegisterEventLog returned actual error code 1603 but will be translated to success due to continue marking
    CustomAction SetupMcConnector returned actual error code -2147024809 (note this may not be 100% accurate if translation happened inside sandbox)
    Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action SetupMcConnector, location: C:\Program Files\Windows Server\Bin\esSetup.exe, command: **********
    MSI (s) (58:E0) [21:05:15:001]: Product:  Connector -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.  Action SetupMcConnector, location: C:\Program Files\Windows Server\Bin\esSetup.exe, command: **********

    Action ended 21:05:15: InstallFinalize. Return value 3.


    The connector installation works fine on another computer...
    Wednesday, April 20, 2011 1:47 AM
  • Hi,

    I created another administrator login on the computer and the installation went through successfully under this new account.

    I believe the problem was within my user profile somewhere.

    So it works now.

    Thx.

    Friday, April 22, 2011 12:05 PM
  •  

    I am also having the same issue on my WHS 2011 machine. I have confirmed that my password does not contain any special characters.

    Here is the log information showing the error.

    ClientDeploy.log

    [6096] 110425.214413.0865: ClientSetup: Install package C:\Windows\Temp\Client Deployment Files\ClientCore.msi
    [6096] 110425.214413.1021: ClientSetup: Running MSI: C:\Windows\Temp\Client Deployment Files\ClientCore.msi  SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* REBOOT=ReallySuppress
    [6096] 110425.214530.0791: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.
       at Microsoft.Deployment.WindowsInstaller.Installer.CheckInstallResult(UInt32 ret)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.Helper.RunMsi(String msiPathOrProductCode, String logFilePath, Dictionary`2 msiProperties, Boolean install, ProgressChangedEventHandler progressHandler)
    [6096] 110425.214530.0791: ClientSetup: RunMsi returned error: RetCode=1603

    LanConfigSvc

     

    Not sure if this is an issue

    (EndpointNotFoundException) Could not connect to net.tcp://127.0.0.1:65532//Microsoft.WindowsServerSolutions.Common.ProviderFramework.IProviderRegistration. The connection attempt lasted for a time span of 00:00:01.0296018. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:65532.  ==> (SocketException) No connection could be made because the target machine actively refused it 127.0.0.1:65532
    [6972] 110425.220243.5501: ProviderFramework: Information: [0] : ProviderRegistryProxy: connection attempt failed.
    [6808] 110425.220243.5501: ProviderFramework: Information: [0] : ConnectAsync was NOT able to synchronously connect to the provider registry.
    [6808] 110425.220243.5813: ProviderFramework: Information: [0] : Creating service/proxy endpoint for Contract [IServerDiscoveryProvider], binding = [CustomBinding], EndpointAddress =

     

     

    If anyone has any suggestions on a fix, please let me know.

    Thank-you,

    Sir Stox


    Sir Stox
    Tuesday, April 26, 2011 5:36 AM