Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Windows Home server Connector Fails to install on WinXP SP3 RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    The Connector installed without problems on three computers (win7 Home premium, Win7 Professional and win7 ultimate) but failed on two computers with With WinXP SP3 (32 bit). The installation proceeds through the initial steps and through the server password request. Then it gets to Configuring the computer. It stays there for awhile after whicvh the following messeage appears:

    The Windows Home server 2011 Connector has encountered an unepxected error. Click close to undo most of the changes that are made to the computer.

    I have tried several times but the results reamians the same. The connector for the origanl version of Windows home server had no problems installing.  I did reinstall it without problem.

    Any ideas of how to get the connector for WHS 2011 To install on the WinXP machines ???   

    • Moved by Ken Warren Friday, June 24, 2011 12:26 AM Vail question (From:Windows Home Server Hardware and Installation)
    Thursday, June 2, 2011 6:13 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I got a clue from the internet. In the folder  C:\Windows\Microsoft.NET\Framework\v4.0.30319 I renamed the file SMSvchost.exe.config and copied the SMSvchost.exe.config from C:\Windows\Microsoft.NET\Framework\V3.0\windows Communication foundation. Rebooted the machine and checked local services. The NetTcpPortSharing showed started. I uninstalled the connector for windows home server and rebooted. I then tried to install the connector for windows home server 2011. It installed without any problem. Backed up the client -no problem. It looks like replacing the SMCcvHost.exe.config file with the configuration file from an earlier version fixed my problem.
    After having success on my first winxp SP3 (32bit) machine. I tried on my second XP machine. Again everything went as described above. It is presently being backed up by Windows home server 2011.
    So far I have not seen any negative effects from using an earlier version of the configuration file

    It looks like my problem installing the windows home server 2011 connector on my 2 winxP SP3 (32bit) machines is fixed. I'll watch for a few days and see if using the older version of the configuration file has any negative side effects.


    It was just in time since it is starting to bug me to activate again . I have already used slmgr -rearm twice. I'm not sure it would have worked a third time.  
    • Marked as answer by Jon_Hildrum Tuesday, August 16, 2011 2:25 AM
    Saturday, August 13, 2011 9:50 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    please check the event logs on client and server for more detailed related errors and/or warnings. ("Unexpected" is just that - unexpected, I also would wish, that Microsoft would find better worded error messages pointing to the issue instead of showing surprise, something which helps actually in diagnostics.)

    Other than that - which security suite is installed on the client? If it contains also Firewall functionality, try to uninstall it temporary.

    Do time, time zone and date (including year) match on both client and server?

    Best greetings from Germany
    Olaf

    Friday, June 3, 2011 12:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I did check the event viewer but didn't see anything at the time. Furthermore, I searched on google and found someone having a similar problem where a beta version of .net framework 4 had been installed. Another person had just clicked the X in the corner rather than close and everything worked. Neither approach worked for me.

    I also went through and tried to make sure that all software and registry entries from the old Home server was removed. (It is possible that I might have missed something)

    The Client computer actually appears in the list of computers on the server but is shown as offline. Furthermore, the connector software is not being installed on the client. Both Client computers use Microsoft Security Essentials. The Date, Time Zone and year match within a few seconds and the time zone is US Pacific  same as Microsoft default.    I'm using the windows firewall (Microsoft).  

    Friday, June 3, 2011 1:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    One of the WinXP SP3 computers I tried to install the connector on has a dual boot with win7 Home premium. I tried the following:

    In WinXP, I disabled all startup items and all services not required in MSconfig. Rebooted and tried installing the connector. Same result. I then tried installing in the alternate boot (win7). It installed with no problems.

    The connector for the old version of WHS are now installed in both WinXP machines. (It was uninstalled and computer rebooted before trying WHS 2011 connector installation)  

    Saturday, June 4, 2011 2:12 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, it is getting close to the day when I have to activate Windows Home Server 2011. Having searched using Google, Bing and forums for potential solutions, I have found nothing that works. I did find a few suggestions but they didn't work for me. I think the solution is to go back to the old Version of WHS which worked fine for all my computers.

    I can post the logs from my last try if that would be of any help

    Wednesday, June 15, 2011 2:54 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I am having the same problem. I am trying to deploy microsoft small business server essentials in what was formerly a workgroup network. Most of the machines are XPPROSP3. The lone win7 pro machine (my laptop) went in flawlessly, but two XPPRO machines both errored out in the same fashion as described here. I have tried many of the suggestions offered but to no success. Obviously, this problem is common to WHS and SBS and really needs some attention from Microsoft. Still looking for the answer...

     

     

    Wednesday, June 15, 2011 7:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well, tomorrow is the day when I have to activate. After having spent lots of hours doing research on the net and trying every potential suggestion, I have not been able to resolve the problem.  The Home server 2011 connector does not install on my XP SP3 machines. It stops where normally the connector software is to be downloaded.

    I'm wondering if there are some remenants of the old WHS connector remaining on the machines which prevents it from downloading and installing the software. However, after using the add/remove programs in control panel to delete the old connector, I also searched the harddrive and the register for any items related to WHS, Windows Server and windows home server  and removed anything I could fine. Didn't help.

    Now I have two options:

    1. Activate windows Home server 2011 and using it for the win7 machines. Leave my old whs running for XP machines and hope there is a potential resolution for my problem in the not to distant future.  ( I do like some of the features added in WHS 2011 and loss of drive extender is not a significant problem for me ) 

    2. Delete the Windows Home server 2011 altogether and install the original WHS on my newer hardware -( It is faster, has more memory and more disk space). There are no problems with either my win7 machines or the XP SP3 machines on the old WHS.

    I'll Sleep on it.  


    Thursday, June 23, 2011 8:27 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    3. Start again with a new installation of WHS2011 and try a new 30 days to solve the problem.

     

    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
    Thursday, June 23, 2011 8:34 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Actually I decided to try a reinstall to see if I would be able to resolve the issue in the next 30 days. However, befoere starting the reinstall I decided to try the

     slmgr -rearm  which if it worked,  would give me another 30 days to activate and not delete some of the data already on the WHS 2011. It worked - I now have another 30 days to activate.

    Friday, June 24, 2011 4:35 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I've tried everything I can find about potential solutions on the net. Nothing has worked so far.  My next step is to try reinstalling WinXP SP3 on one of the two where the connector fails. If that does not resolve the problem, I will try to reinstall Windows Home server 2011.

    If neither works then it is time to ditch Windows Home server 2011 and return to the original version where I had no problems with any of my machines.

     


    Sunday, July 3, 2011 4:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I have a triboot PC with XPPro x32, Vista-Ult X32 and W7 Pro x32 and had lots of problems with XPPPro until I found the problem was in the registry and discussed in other parts of the forum when getting errors saying "a connect installation can't proceed because there is a insatallation already in process and the system needs to be rebooted". However, I think that the "rename" registry key should be cleared after every connect load failure and then reboot the system and try again. It was mentioned that Widows Security Essentials was not compatible with WHS 2011 and thus deleting it befor another attempt to connect might be another step toward the solution.
    Frank Stankis Sys Mngr
    Monday, July 4, 2011 8:47 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Opps , I made an error about the Microsoft security essentials. It can't be used on the server, but can on the clients. I am just starting to learn the details of WHS 2011 and sometimes make a wrong assumption. I still think the problem is related to the registry and I am going to see if I can duplicate it on my computer.  I had a similar problem but not identical and making a registry change and getting rid of the Logitec Web Cam software allowed me to load the connector successfully.

    Nothing like problems to help learn the system, like on-the -job traing which is more difficult but but rewarding when a problem is resolved.

    Frank Stankis Sys Mngr
    Monday, July 4, 2011 10:27 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Well I got a little further along:

    1.  I tried removing Logitech Web Cam software, removed .net 4, removed the old WHS connector, Searched computer and registry for anything with "windows home server" and removed anything I found. I cleaned out tmp files. (PS I rebooted after each item).  Tried installing windows Home server 2011 connector.  The same results as original - The installation installs .net 4 and proceeds to where the connector software is supposed to download and install and quits with the unexpected error message. The computer appears in the Windows Home server 2011 as off line just after the connector software gets the Home server password and connects.

    This attempt was a failure

    2. Next I tried an almost clean install. I had an acronis image from mid 2008 which was clean install with the applications used in mid 2008. I restored this image and tried installing the Windows 2011 Connector. The installation went through and installed .net 4 and proceded to install the connector software without any problems. Thus this installation was a success.

    However, the problem now is that this image is from 2008 and includes the applications and configurations from that time. Some of these applications has been deleted since then, several have been updated and additional application has been installed as well as a bundle of windows XP updates.  It would take quite awhile to determine what has changed between 2008 and today -and then upgrade the 2008 installation without losing anything - a dilemma !!! (Specially since this is my wifes computer and I'd be in trouble if I mess it up) 

    This attempt was a success!!!!

    Next: Maybe next I'll try a repair install of my exisitng windowsXP installation and see what happens. However, the indications seems to be that it is an application that might be causing the problem.

    Question which Microsoft should answer: Why all the problems with installing the connector software on Windows Home server 2011. Never had any problems with the original windows Home server.

     

     



    Tuesday, July 5, 2011 5:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    No good solution yet. I'll try rearming once more for another 30 days.

    What did work:

    1. Reinstalling an old Image of my wife's computer from 2008 with minimal applications. This is a problem on my wife's computer since it has changed quite a bit over the last 3 years. It would take quite a bit of time to start from scratch even though probably less than I have already spent on this issue.

     

    What has not workes:

    1. Removing Logitech Web Cam and software

     2. removing .net 4 and letting the connector installation install it

    3. After removing WHS Old version connector search computer and registry for anything related to Windows Home Server, WHS, Windows Server and removing it prior to trying to install Windows Home server 2011 connector.

    4. Using MSconfig and diabling any startup items. Furthermore disabling processes not required

    5. Comparing the two XP SP3 machines (which has the same problem). Then removing all applications common to the two machines ( Since it worked on a pretty clean old image and the indication is that an application may be part of the problem) 

    6. Reviewed event viewer after failed installation for clues. Nothing there which is of significance to me. Reviewed the logs after the tries. It doesn't mean much to me except something appears to time out. I did try to increase the time out period by making a registry change. Made no difference.

    7. I did try a repair install of windows XP SP3 without success but I need to try it again since I forgot to prepare the machine properly for the repair install. Thus this  try was not a valid try.

    Where to go from here:

    I'll retry the repiar install - hope it works. If not my choice is to start from a clean install (No problem on one of the XP machines since it is a test machine anyway -but I major headache on my wife's computer), or ditch Windows Server 2011 and go back to the original WHS which worked without problems on all my machines.     

    Friday, July 22, 2011 5:38 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jon,

    sometimes starting from the scratch would be really the best way - and why not with Windows 7 instead of XP then?

    Best greetings from Germany
    Olaf

    Friday, July 22, 2011 11:49 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It goes without saying, but if you have 3rd-party anti-virus software installed on your Windows XP machines, have you tried disabling it prior to the install?   (In general, I recommend MS Security Essentials--it's unobstrusive, fast, free, and most importantly, likely to have been tested by MSFT product teams.)
    Saturday, July 23, 2011 3:19 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have suggested windows 7 to my wife several times. I actually have an unused Windows 7 Ultimate which was planned for her computer. She is used to her machine which she has had for years. Furthermore, She likes outlook express. Her machine has Office with outlook but that was a no go. She also looked at Windows Live mail - IHer friends use it on Windows 7 and she does not like it. Thus, for the time being I'm kind of stuck with WinXP on her machine.

    My test machine which has a dual boot of XP and Win7 is not an issue. I keep XP on it since I have a game that does not work well on Windows 7. I tried it using the XP mode but the video was very slow.

    I use MS security essentials on both of the XP machines. No 3rd party anti-virus software installed.

    I have a couple of items to try but want be able to do it before next weekend. It ties up the machine for most of the day and my wife want need it next weekend.    

    Saturday, July 23, 2011 3:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I have suggested windows 7 to my wife several times. I actually have an unused Windows 7 Ultimate which was planned for her computer. She is used to her machine which she has had for years. Furthermore, She likes outlook express.


    Understand. 

    If you really want to help her migrate, it is possible to configure Windows 7 Ultimate so that she could run Outlook Express "seamlessly" in Windows XP Mode.  The app could even be pinned to the Windows 7 Task Bar or Start Menu.  In time, she may grow to prefer some of the more modern Windows 7 apps and features. And of course, she could simply run the Windows XP environment full screen.

    Virtualization is more complex to setup than I would suggest for casual users, but if you know your way around PCs (which you seem to), its a potential solution. You do have to do make a registry change on the virtual XP system to surface some of the built-in apps (such as IE or OE) on the Windows 7 Start menu, but a Bing search should give you what you need.

    Saturday, July 23, 2011 4:38 PM
  • Question
    Sign in to vote
    3
    Sign in to vote

    I had the same problem..

    I came across a solution that has worked for both of my XPSP3 boxes which is to rename the MachineKeys directory under:

    Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA

    I just renamed it with a _old and both machines were able to install the connector.

    Hope that helps.

    • Proposed as answer by jimerich Sunday, May 6, 2012 7:39 PM
    Friday, July 29, 2011 6:18 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I had this problem too.. but it's with sbs essentials 2011.

    It's basically the same as whs 2011, it just has active directory. Do you thing this solution will work on my pain in the neck installation? And do you just rename the folder _old or all the files in it?

    salt4502
    Saturday, July 30, 2011 3:17 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I tried renaming the Machinekeys directory under Documents and Settings\All Users\Application Data\Microsoft\Crypto\RSA. The connector would not install - same problem.

     

    PS: I was looking at using outlook express in windows 7 ( I know it will not work in 64 bit but it might in 32 bit). I have searched and not found a good solution. I see solution that uses windows mail but she didn't like it either. The fact that some people suggest it is similar and really outlook express 7 does not get me far. She uses outlook express 6, is familiar with it, both mail and newsgroups  and does not want to change.

     

    Virtualization may be an idea

     

     

    Sunday, July 31, 2011 8:53 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Jon

    From your posts, I feel that your are interested in solveing problems and I will try to help you solve this one. ^_^

    There are some product logs of WHS 2011 under %programdata%\Microsoft\Windows Server\Logs. You can delete these logs and try to install again. After fail to install , you can get some useful information from the log to help you solve the problem. You can paste the log here , or email to me. (Please delete any of your personal information from the log)  

    Saturday, August 6, 2011 5:30 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi sbs

    I'm having the exact same problems as Jon. I have a post on here titled "Trouble Installing Launchpad: Logs Included" Could you possibly help me to?

    If you can, Thanks

    salt4502
    Saturday, August 6, 2011 6:28 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I can paste the log files here. There are 3 of them and they take quite a bit of space. Maybe it would be easier to email them to you if you provided an email address.

    Mine is Jon_Hildrum@msn.com

    For your info I did a little bit more research and found the following:

    net tcp port sharing services is not started. It is set to automatic but instead of saying started like some of the other, it just says starting. All the boxes for start, stop etc are greyed out. I tried changing to manual to see if I could get it to say Started but no luck. I tried repairing the .Net 4 installation but still no luck. I tried using start run and type in sc start nettcpportsharing but it made no difference either.

    Maybe that is my problem that NetTCPportsharing is not started.

    PS: The other XP computer that fails installing the Home server 2011 Connector has the same situation with Nettcpportsharing.

    PS: I also tried deleting .net 4 and have the connector installation install it. Made no difference.



    Tuesday, August 9, 2011 5:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Dear Jon

    For a possible fix to your problem check out my post  "Trouble Installing Launchpad, Logs Included, Update: Solved!!!" Your problem is the same one I had.

    salt
    Tuesday, August 9, 2011 9:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    here is a copy of my clientdeploy log. It appears that nettcpportsharing may be the problem

    ---------------------------------------------------------
    [4972] 110809.095514.9375: ClientSetup: Start of ClientDeploy
    [4972] 110809.095515.0937: General: Initializing...C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe
    [4972] 110809.095515.0937: ClientSetup: Loading Wizard Data
    [4972] 110809.095515.9375: ClientSetup: Current DeploymentStatus=Failed
    [4972] 110809.095521.6250: ClientSetup: Showing the Client Deployment Wizard
    [4972] 110809.095521.7500: ClientSetup: Adding Server Info data in the Product Registry
    [4972] 110809.095521.8437: ClientSetup: Set the Deployment Sync Event
    [5336] 110809.095532.4687: ClientSetup: Running ValidateUser Tasks at WizardPage HomeServerCred
    [5336] 110809.095532.4843: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5336] 110809.095532.4843: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser
    [5336] 110809.095532.5625: ClientSetup: Entering ValidateUserTask.Run
    [5336] 110809.095532.5781: ClientSetup: Install root cert to local trusted store
    [5336] 110809.095532.9843: ClientSetup: Validating User
    [5336] 110809.095532.9843: ClientSetup: Call MachineIdentityManager.GetMachineStatus
    [5336] 110809.095543.9687: ClientSetup: Current Machine Join Status: NotExists
    [5336] 110809.095543.9687: ClientSetup: Exiting ValidateUserTask.Run
    [5336] 110809.095543.9687: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Warning
    [5336] 110809.095543.9687: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot
    [5336] 110809.095543.9687: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5336] 110809.095543.9687: ClientSetup: Running JoinNetwork Tasks at WizardPage HomeServerCred
    [5336] 110809.095543.9687: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5336] 110809.095543.9843: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork
    [5336] 110809.095543.9843: ClientSetup: Entering JoinNetworkTask.Run
    [5336] 110809.095543.9843: ClientSetup: Network Join Client to Server: ClientComputerName=xxxxxxx ServerName=yyyyyyyy
    [5336] 110809.095543.9843: ClientSetup: Maximum amount of joined machines: 15
    [5336] 110809.095543.9843: ClientSetup: Current amount of joined machines: 5
    [5336] 110809.095543.9843: ClientSetup: Running Network Join
    [5336] 110809.095543.9843: ClientSetup: Call MachineIdentity.GetCert
    [5336] 110809.095550.1406: ClientSetup: Exiting JoinNetworkTask.Run
    [5336] 110809.095550.1406: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success
    [5336] 110809.095550.1406: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
    [5336] 110809.095550.1406: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [4972] 110809.095550.1406: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success
    [5336] 110809.095601.2031: ClientSetup: Running Tasks for Wizard Page ConfiguringComputer
    [5336] 110809.095601.2031: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5336] 110809.095601.2031: ClientSetup: Running Task with Id=ClientDeploy.PrepareClient
    [5336] 110809.095601.2187: ClientSetup: Entering PrepareClientTask.Run
    [5336] 110809.095601.2187: ClientSetup: Ensuring that ServiceName=NetTcpPortSharing is Running
    [5336] 110809.095801.2812: ClientSetup: Could not ensure NetTcpPortSharing service is Running: System.ServiceProcess.TimeoutException: The timeout provided has expired and the 'NetTcpPortSharing' service has not reached any of the desired states. Desired states are 'Running', 'Paused', 'Stopped', and the current state is 'StartPending').
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility._ThrowTimeout(ServiceController objSvc, ServiceControllerStatus[] statusArray)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility._PollForStatusChange(ServiceController objSvc, DateTime deadline, ServiceControllerStatus[] statusArray)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForMultipleStatus(ServiceController objSvc, DateTime deadline, ServiceControllerStatus[] statusArray)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.ChangeObjectState(Methods method, ServiceController svc, DateTime deadline)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(ServiceController svc, Int32 timeout)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(String serviceName, Int32 timeout)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.PrepareClientTask.Run(WizData data)
    [5336] 110809.095801.2812: ClientSetup: Exiting PrepareClientTask.Run
    [5336] 110809.095801.2812: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Failed
    [5336] 110809.095801.2812: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot
    [5336] 110809.095801.2812: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5336] 110809.100351.6406: ClientSetup: Running Tasks for Wizard Page InstallationError
    [5336] 110809.100351.6406: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5336] 110809.100351.6406: ClientSetup: Running Task with Id=ClientDeploy.UninstallSoftware
    [5336] 110809.100351.6406: ClientSetup: Entering UninstallSoftwareTask.Run
    [5336] 110809.100351.6406: ClientSetup: Client MSI is not installed
    [5336] 110809.100351.6406: ClientSetup: Exiting UninstallSoftwareTask.Run
    [5336] 110809.100351.6406: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has TaskStatus=Success
    [5336] 110809.100351.6406: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has RebootStatus=NoReboot
    [5336] 110809.100351.6406: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [4972] 110809.100351.6406: ClientSetup: Back from the Client Deployment Wizard
    [4972] 110809.100351.6406: ClientSetup: Saving Wizard Data
    [4972] 110809.100351.6562: ClientSetup: End of ClientDeploy: ErrorCode=1603
    336] 110809.095543.9843: ClientSetup: Maximum amount of joined machines: 15
    [5336] 110809.095543.9843: ClientSetup: Current amount of joined machines: 5
    [5336] 110809.095543.9843: ClientSetup: Running Network Join
    [5336] 110809.095543.9843: ClientSetup: Call MachineIdentity.GetCert
    [5336] 110809.095550.1406: ClientSetup: Exiting JoinNetworkTask.Run
    [5336] 110809.095550.1406: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success
    [5336] 110809.095550.1406: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot
    [5336] 110809.095550.1406: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [4972] 110809.095550.1406: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success
    [5336] 110809.095601.2031: ClientSetup: Running Tasks for Wizard Page ConfiguringComputer
    [5336] 110809.095601.2031: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5336] 110809.095601.2031: ClientSetup: Running Task with Id=ClientDeploy.PrepareClient
    [5336] 110809.095601.2187: ClientSetup: Entering PrepareClientTask.Run
    [5336] 110809.095601.2187: ClientSetup: Ensuring that ServiceName=NetTcpPortSharing is Running
    [5336] 110809.095801.2812: ClientSetup: Could not ensure NetTcpPortSharing service is Running: System.ServiceProcess.TimeoutException: The timeout provided has expired and the 'NetTcpPortSharing' service has not reached any of the desired states. Desired states are 'Running', 'Paused', 'Stopped', and the current state is 'StartPending').
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility._ThrowTimeout(ServiceController objSvc, ServiceControllerStatus[] statusArray)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility._PollForStatusChange(ServiceController objSvc, DateTime deadline, ServiceControllerStatus[] statusArray)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.WaitForMultipleStatus(ServiceController objSvc, DateTime deadline, ServiceControllerStatus[] statusArray)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.ChangeObjectState(Methods method, ServiceController svc, DateTime deadline)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(ServiceController svc, Int32 timeout)
       at Microsoft.WindowsServerSolutions.Common.ServiceUtility.EnsureStarted(String serviceName, Int32 timeout)
       at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.PrepareClientTask.Run(WizData data)
    [5336] 110809.095801.2812: ClientSetup: Exiting PrepareClientTask.Run
    [5336] 110809.095801.2812: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Failed
    [5336] 110809.095801.2812: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot
    [5336] 110809.095801.2812: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [5336] 110809.100351.6406: ClientSetup: Running Tasks for Wizard Page InstallationError
    [5336] 110809.100351.6406: ClientSetup: Entering ConnectorWizardForm.RunTasks
    [5336] 110809.100351.6406: ClientSetup: Running Task with Id=ClientDeploy.UninstallSoftware
    [5336] 110809.100351.6406: ClientSetup: Entering UninstallSoftwareTask.Run
    [5336] 110809.100351.6406: ClientSetup: Client MSI is not installed
    [5336] 110809.100351.6406: ClientSetup: Exiting UninstallSoftwareTask.Run
    [5336] 110809.100351.6406: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has TaskStatus=Success
    [5336] 110809.100351.6406: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has RebootStatus=NoReboot
    [5336] 110809.100351.6406: ClientSetup: Exting ConnectorWizardForm.RunTasks
    [4972] 110809.100351.6406: ClientSetup: Back from the Client Deployment Wizard
    [4972] 110809.100351.6406: ClientSetup: Saving Wizard Data
    [4972] 110809.100351.6562: ClientSetup: End of ClientDeploy: ErrorCode=1603

    Wednesday, August 10, 2011 12:37 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It's look like an external issue to me, I should also connect .net team to see this problem to solve it. But if you have time to put more effort on it I can offer you a suggestion. http://support.microsoft.com/kb/241215 How to use the Userdump.exe tool to create a dump file. The net port shareing service is hang, we need to know what does it wait for. I will send my email address to you.
    Wednesday, August 10, 2011 2:46 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I installed the Userdump.exe and ran it for PID 636 which is SMSvcHost.exe. This is the file that the service nettcpportsharing says it is running under services.

    I just ran userdump 636  from a command prompt.  However, the dump file ends up being 91MB which is larger than my email will allow as an attachment

    How do I get it to you ???

    Wednesday, August 10, 2011 5:22 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I got a clue from the internet. In the folder  C:\Windows\Microsoft.NET\Framework\v4.0.30319 I renamed the file SMSvchost.exe.config and copied the SMSvchost.exe.config from C:\Windows\Microsoft.NET\Framework\V3.0\windows Communication foundation. Rebooted the machine and checked local services. The NetTcpPortSharing showed started. I uninstalled the connector for windows home server and rebooted. I then tried to install the connector for windows home server 2011. It installed without any problem. Backed up the client -no problem. It looks like replacing the SMCcvHost.exe.config file with the configuration file from an earlier version fixed my problem.
    After having success on my first winxp SP3 (32bit) machine. I tried on my second XP machine. Again everything went as described above. It is presently being backed up by Windows home server 2011.
    So far I have not seen any negative effects from using an earlier version of the configuration file

    It looks like my problem installing the windows home server 2011 connector on my 2 winxP SP3 (32bit) machines is fixed. I'll watch for a few days and see if using the older version of the configuration file has any negative side effects.


    It was just in time since it is starting to bug me to activate again . I have already used slmgr -rearm twice. I'm not sure it would have worked a third time.  
    • Marked as answer by Jon_Hildrum Tuesday, August 16, 2011 2:25 AM
    Saturday, August 13, 2011 9:50 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    It sounds to me like something subtly corrupted your .Net 4.0 installation. I don't see an answer to this, so I'll ask: Did you try to uninstall Framework 4.0, reboot, then reinstall separate from the connector?
    I'm not on the WHS team, I just post a lot. :)
    Saturday, August 13, 2011 10:30 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes, I tried on both machines. 

    1.  I uninstalled .net 4  - rebooted and installed .net 4 from Microsoft. (same result didn't work)

    2. I uninstalled .net 4 -rebooted and let Windows Home server connector installation install .net 4. It did (but same result didn't work)

    3. I tried doing a repair installation of .net 4 from Add/remove programs in control panel - (Same results didn't work)

    I think there may be a problem with the configuration file SMSvchost.exe.config file in v4.0.30319 when installed on a WinXP  professional SP3 32 bit. Two different computers - one my wifes which has quite a bit of stuff installed the other a test machine which presently has very little installed. However, I tried using a clean install image on my wifes computer from 2008 and then it did work.   

     

    Sunday, August 14, 2011 1:57 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Heh. I had this exact same issue on one of two XPSP3 machines. Replacing the SMSvchost.exe.config as documented above fixed one machine. The other one had the issue with the registry setting for file rename. Thanks for documenting the fix!
    Monday, August 15, 2011 10:21 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Everything seem to be working fine now. I activated Windows home server 2011. The old version has been retired.

    The difference in the two configuration files are as Follows:

    The one from net.3 contains the following line under <runtime>

    <generatePublisherEvidence enabled="false" >

    This line is not in the .net 4 configuration file.

     

    The one from .net 4 contains the following new item not found in the .net 3 version:

    <system serviceModel>

    <!-- SMSvcHost ETW traces are redirected by default to an etwProviderID different from WCF's default.

     To trace to the default provider, remove the etwProviderID attribute below. -->

                    <diagnostic performanceCounters="off"

    etwProviderId="{f188839f5-27ff-4e66-bd2d-639b768cf18b}"/>

     

    I have no idea what the potential impact of these differences may be. If someone has some knowledge please let us know.

    My problem has been resolved !!!!!!

     

     


    Tuesday, August 16, 2011 2:25 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    For what it is worth I have had similar problems expressed here on an XP box (sp3). After thinking about giving up as i tried all the solutions I noticed two thing:

    1) The install looked slighly different on the XP to the WIN7 boxes I have in that I never even got the green progress bars before it bombed

    2) net tcp port sharing was showing as starting not started with the properties greyed out. Once I changed to the log on to local account - there was a weird account it was set to log on to- the connector install proceeded without any problems

    Wednesday, August 17, 2011 7:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I do not recall whether mine was weird or not.  I remember looking at that in properties. This may be a much better solution than the one I found. However after spending months getting it to work, I'm not going back to undo my installation to see if this would have worked for me. (PS I never got a green bar either )

    However after searching the net for solution I noticed there were quite a few people having problems with the connector installation.  There were also quite a few different  solution that had worked for some. I tried them all without success.  

    Wednesday, August 17, 2011 9:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I installed WHS 2011 OEM on an HP MSS EX490 very successfully.  I executed //server1/connect/ on 2 laptops (Win 7 Ultimate), a PC (Win 7 Ultimate), and a laptop (XP Pro SP3).  Installation went perfectly.  Launchpad worked on all 4 machines.

    I installed WHS 2011 OEM on a spare 64 bit PC.  Installed without a hitch.  Activated Remote Web Access (domian/SSL) also without a hitch.  Then I tried to execute //server2/connect/ on one laptop (Win 7 Ultimate) and one laptop (XP Pro SP3).  Unsuccessful ..... totally.  I had gone to great lengths to ensure that all previous traces of //server1/connect/ had been removed.

    On all machines, it accepts the server2 password, thinks for a few seconds, then gives this error message "Cannot connect this computer to the network.  An unexpected error has occurred.  For more information, see Troubleshoot connecting computers to the server".  That troubleshoot has not been helpful.

    Remember that these same computers on the same router, same network, same firewall, etc, connected to server1 (EX490) without any problems.

    I re-installed the XP Pro on the laptop.  Didn't connect.  I installed Win 7 Ultimate on another spare PC.  Didn't connect.

    So to my mind, there is something in the second installation of WHS 2011 that is causing the problem.

    Any ideas, please.

    Wednesday, August 17, 2011 10:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Do you have installed on that machine any one of the following?

    a. Acronis
    b. Quickbooks
    c. Forefront a/v
    d. Microsoft security essentials?
    Monday, October 3, 2011 11:13 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    On SBS Server 2011 connecting an XP SP3 work station resolved my Connector installation issue where the error was 'unable to establish a trust relationship'.

    Quick, easy and fixed the problem!  Grateful for the advice.

    Sunday, May 6, 2012 7:44 PM