Connector installation issue

I’ve set up a 4TB unit in a branch office and now I’m beginning deployment of an 8TB in our corporate office. I have set it up successfully on my laptop and ran into an issue on my 2nd install. The computer is XP Service Pack 3 with all Windows Updates. I go to the webpage through Internet Explorer 8, click to install the connector. The installer begins and I’m able to choose the computer name, power options, etc. The installation fails and says it has encountered an unexpected error. Click Close to undo any changes made by this installer.

Going off of suggestions on other forums, I have downloaded and re-installed .NET Framework 4 in repair mode, started some sort of Windows Media Player sharing service and disabled Windows Firewall. The installer still fails on this computer.

It registers with the server because when I try to re-install, it says the computer already exists on the server and it does. But the launchpad does not install and it shows that computer as offline on the server dashboard.

Any ideas?

Can you tell us the exact version of the Windows XP OS?

Is it Windows XP Home or Professional or something else? 32 Bit OS or 64 Bit OS?

Xp pro 32bit. My laptop, which works fine, is the same thing.

Look at this post. While it mentions SBS 2011 and WHS, WSSe is member of the same server family and the same steps apply. Please let us know here if this helps:

Also, you will find several troubleshooting topics on Microsoft Online Help for Windows Storage Server 2008 R 2 Essentials here:


ClientDeploy.log has this: Note the first line. I think that’s my issue. Now I just have to figure out how to resolve that… I disabled the service and got the same result. Before I disabled, it said it was running, which is one of the desired states.

[3640] 111208.155550.6718: 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’, 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)
[3640] 111208.155550.6718: ClientSetup: Exiting PrepareClientTask.Run
[3640] 111208.155550.6718: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Failed
[3640] 111208.155550.6718: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot
[3640] 111208.155550.6718: ClientSetup: Exting ConnectorWizardForm.RunTasks
[2868] 111208.155553.2343: ClientSetup: Running Tasks for Wizard Page InstallationError
[2868] 111208.155553.2343: ClientSetup: Entering ConnectorWizardForm.RunTasks
[2868] 111208.155553.2500: ClientSetup: Running Task with Id=ClientDeploy.UninstallSoftware
[2868] 111208.155553.2500: ClientSetup: Entering UninstallSoftwareTask.Run
[2868] 111208.155553.2500: ClientSetup: Client MSI is not installed
[2868] 111208.155553.2500: ClientSetup: Exiting UninstallSoftwareTask.Run
[2868] 111208.155553.2500: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has TaskStatus=Success
[2868] 111208.155553.2500: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has RebootStatus=NoReboot
[2868] 111208.155553.2500: ClientSetup: Exting ConnectorWizardForm.RunTasks
[2940] 111208.155553.2812: ClientSetup: Back from the Client Deployment Wizard
[2940] 111208.155553.2812: ClientSetup: Saving Wizard Data
[2940] 111208.155553.2812: ClientSetup: End of ClientDeploy: ErrorCode=1603

The service is actually stuck in a starting state. It’s a component of .net framework 4. I uninstalled 4, reinstalled and it still wouldn’t start. When it left work, I had windows updates going which found 7 patches for he freshly installed framework 4. I will give an update tomorrow.