Jump to content
RESET Forums (homeservershow.com)
fredp1

Cannot install client connector for a Win XP workstation- unexpected error

Recommended Posts

fredp1

I have a XP client that will not install the client.

The error is 'The windows home server 2011 connector has encountered an unexpected error'

 

The machine is fully patched. AV was turned off/on. There are no viruses.

The pc is connected via cat5 to a switch.

I've checked the service NetTcpPortSharing and it is running.

The PC is part of the workgroup and can see the WHS 2011 (FS1)

 

I've run out of ideas to fix this.

 

Has anyone come across this before?

 

 

Here is the log from C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs\ClientDeploy.log

 

[2456] 110915.063702.0468: ClientSetup: Start of ClientDeploy

[2456] 110915.063703.5468: General: Initializing...C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe

[2456] 110915.063703.7968: ClientSetup: Loading Wizard Data

[2456] 110915.063707.4218: ClientSetup: Current DeploymentStatus=Failed

[2456] 110915.063709.0156: ClientSetup: Showing the Client Deployment Wizard

[2456] 110915.063709.2500: ClientSetup: Adding Server Info data in the Product Registry

[2456] 110915.063709.3906: ClientSetup: Set the Deployment Sync Event

[1376] 110915.063716.8750: ClientSetup: Running ValidateUser Tasks at WizardPage HomeServerCred

[1376] 110915.063716.9062: ClientSetup: Entering ConnectorWizardForm.RunTasks

[1376] 110915.063716.9062: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser

[1376] 110915.063717.0156: ClientSetup: Entering ValidateUserTask.Run

[1376] 110915.063717.0468: ClientSetup: Install root cert to local trusted store

[1376] 110915.063717.1093: ClientSetup: Validating User

[1376] 110915.063717.1093: ClientSetup: Call MachineIdentityManager.GetMachineStatus

[1376] 110915.063722.8281: ClientSetup: Current Machine Join Status: ActiveWithCert

[1376] 110915.063722.8281: ClientSetup: Exiting ValidateUserTask.Run

[1376] 110915.063722.8281: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Warning

[1376] 110915.063722.8281: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot

[1376] 110915.063722.8281: ClientSetup: Exting ConnectorWizardForm.RunTasks

[1376] 110915.063722.8281: ClientSetup: Running JoinNetwork Tasks at WizardPage HomeServerCred

[1376] 110915.063722.8281: ClientSetup: Entering ConnectorWizardForm.RunTasks

[1376] 110915.063722.8281: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork

[1376] 110915.063722.8281: ClientSetup: Entering JoinNetworkTask.Run

[1376] 110915.063722.8281: ClientSetup: Network Join Client to Server: ClientComputerName=KIDSCOMPUTER ServerName=FS1

[1376] 110915.063722.8281: ClientSetup: Maximum amount of joined machines: 15

[1376] 110915.063722.8281: ClientSetup: Current amount of joined machines: 4

[1376] 110915.063722.8281: ClientSetup: Server already contains a computer joined with Client Machine Name

[1376] 110915.063722.8281: ClientSetup: Network Join has not been forced

[1376] 110915.063722.8281: ClientSetup: Network Join will not be Run

[1376] 110915.063722.8281: ClientSetup: Exiting JoinNetworkTask.Run

[1376] 110915.063722.8281: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Retry

[1376] 110915.063722.8281: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot

[1376] 110915.063722.8281: ClientSetup: Exting ConnectorWizardForm.RunTasks

[2456] 110915.063722.8281: ClientSetup: JoinNetwork Tasks returned TaskStatus=Retry

[2956] 110915.063735.6718: ClientSetup: Running JoinNetwork Tasks at WizardPage ComputerAlreadyExists

[2956] 110915.063735.6718: ClientSetup: Entering ConnectorWizardForm.RunTasks

[2956] 110915.063735.6718: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork

[2956] 110915.063735.6718: ClientSetup: Entering JoinNetworkTask.Run

[2956] 110915.063735.6718: ClientSetup: Network Join Client to Server: ClientComputerName=KIDSCOMPUTER ServerName=FS1

[2956] 110915.063735.6718: ClientSetup: Maximum amount of joined machines: 15

[2956] 110915.063735.6718: ClientSetup: Current amount of joined machines: 4

[2956] 110915.063735.6718: ClientSetup: Server already contains a computer joined with Client Machine Name

[2956] 110915.063735.6718: ClientSetup: Network Join has been forced

[2956] 110915.063735.6718: ClientSetup: Running Network Join

[2956] 110915.063735.6718: ClientSetup: Call MachineIdentity.GetCert

[2956] 110915.063745.2500: ClientSetup: Exiting JoinNetworkTask.Run

[2956] 110915.063745.2500: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success

[2956] 110915.063745.2500: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot

[2956] 110915.063745.2500: ClientSetup: Exting ConnectorWizardForm.RunTasks

[2456] 110915.063745.2500: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success

[2956] 110915.063751.3125: ClientSetup: Running Tasks for Wizard Page ConfiguringComputer

[2956] 110915.063751.3125: ClientSetup: Entering ConnectorWizardForm.RunTasks

[2956] 110915.063751.3125: ClientSetup: Running Task with Id=ClientDeploy.PrepareClient

[2956] 110915.063751.3437: ClientSetup: Entering PrepareClientTask.Run

[2956] 110915.063751.3437: ClientSetup: Ensuring that ServiceName=NetTcpPortSharing is Running

[2956] 110915.063951.5312: 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)

[2956] 110915.063951.5312: ClientSetup: Exiting PrepareClientTask.Run

[2956] 110915.063951.5312: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Failed

[2956] 110915.063951.5312: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot

[2956] 110915.063951.5312: ClientSetup: Exting ConnectorWizardForm.RunTasks

[1376] 110915.064008.8750: ClientSetup: Running Tasks for Wizard Page InstallationError

[1376] 110915.064008.8750: ClientSetup: Entering ConnectorWizardForm.RunTasks

[1376] 110915.064008.8750: ClientSetup: Running Task with Id=ClientDeploy.UninstallSoftware

[1376] 110915.064008.8750: ClientSetup: Entering UninstallSoftwareTask.Run

[1376] 110915.064008.8750: ClientSetup: Client MSI is not installed

[1376] 110915.064008.8750: ClientSetup: Exiting UninstallSoftwareTask.Run

[1376] 110915.064008.8750: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has TaskStatus=Success

[1376] 110915.064008.8750: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has RebootStatus=NoReboot

[1376] 110915.064008.8750: ClientSetup: Exting ConnectorWizardForm.RunTasks

[2456] 110915.064008.9062: ClientSetup: Back from the Client Deployment Wizard

[2456] 110915.064008.9218: ClientSetup: Saving Wizard Data

[2456] 110915.064008.9218: ClientSetup: End of ClientDeploy: ErrorCode=1603

Share this post


Link to post
Share on other sites
jmwills

Copy the Software to the XP machine and install from there. Check your IPv6 settings as well as the Time Zone settings making sure both are the same.

Share this post


Link to post
Share on other sites
fredp1

I tried running it locally.

Share this post


Link to post
Share on other sites
jmwills

Reading thru the Events, the server already contains a machine named "KidsComputer". Check the Server to make sure the computer doesn't already exist or give the XP client a new hostname. Check the XP machine for any prexisiting WHS certs (provided you had a V1 machine) and remove them. Heck, I'd remove any WHS Certs at this point and then install the connector software.

Share this post


Link to post
Share on other sites
Greg Welch

[1376] 110915.063722.8281: ClientSetup: Network Join Client to Server: ClientComputerName=KIDSCOMPUTER ServerName=FS1

[1376] 110915.063722.8281: ClientSetup: Maximum amount of joined machines: 15

[1376] 110915.063722.8281: ClientSetup: Current amount of joined machines: 4

[1376] 110915.063722.8281: ClientSetup: Server already contains a computer joined with Client Machine Name

[1376] 110915.063722.8281: ClientSetup: Network Join has not been forced

[1376] 110915.063722.8281: ClientSetup: Network Join will not be Run

[1376] 110915.063722.8281: ClientSetup: Exiting JoinNetworkTask.Run

 

as stated by JMWILLS (good eye , i missed it the first time)

Share this post


Link to post
Share on other sites
fredp1

Problem solved it was a .Net 4 config issue of some sort.

 

I added the IPv6, made no difference. Timezone was the same.

I spotted this thread http://social.micros...3a-81b94ddf71a9

before trying quite a few others. The solution was to copy the SMSvchost.exe.config from a 3.0 install and replace the v4.0.30319 install.

It now works.

 

Here is the relevant section

 

"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. "

Share this post


Link to post
Share on other sites
ikon

That's a pretty strange fix but, since I think the connector uses .NET 4, it kinda makes some sense.

Share this post


Link to post
Share on other sites
SteveH SW Portland OR

I had given up on connecting my XP Pro laptop to the WHS2011 server until I saw this. Replacing the .net 4.0 SMSvchost.exe.config file with the same file from the .net 3.0 fixed the problem with connecting my XP PC to the server. Thanks for sharing your solution.

Share this post


Link to post
Share on other sites
ikon

I had given up on connecting my XP Pro laptop to the WHS2011 server until I saw this. Replacing the .net 4.0 SMSvchost.exe.config file with the same file from the .net 3.0 fixed the problem with connecting my XP PC to the server. Thanks for sharing your solution.

So, IOW, Back To The Future :)

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...