Jump to content
RESET Forums (homeservershow.com)

WHS Connector Installation Failure


ZA_Tigger
 Share

Recommended Posts

Hi Guys,

 

So I made the switch (forcefully I might add after loosing my trusty ex485 -- long story) so I am using a mini itx DG45FC mb Chenbro 4 bay chassis and 4gb's of ram on a Intel Pentium Dualcore E2200.

 

1st of all I setup a nice 4x2TB raid 5 array thinking that this was the ultimate solution, until WHS2011 didnt want to install to that volume.

 

So I broke the array create a 1TB standalone(OS Drive) and 3x2TB (Raid 5) array for data formatted for GPT with a total size of 3.7TB

 

So all my data is currently being copied. So while waiting for 4TB of data to be moved I decided to start installing connectors and this is where my pain really started.

 

The connector will install fine till about 95% and then roll back with the most descriptive error of unknown and title of installation was cancelled.

 

I searched the web and then looked at the log files but they didn't really give me more info and I checked the following solutions

 

MediaCenter Services - All were started

Task Scheduler - Was working

Security Credentials for Tasks seemed to be working as well.

 

But now I am at wits end

 

Any ideas?

 

Thanks

Andrew

Link to comment
Share on other sites

  • Replies 26
  • Created
  • Last Reply

Top Posters In This Topic

  • ImTheTypeOfGuy

    3

  • jmwills

    3

  • ikon

    6

  • ZA_Tigger

    5

This will sound bad, but I had a similar problem installing the connector soon after WHS 2011 install but don't recall what fixed it. I think it was a combination of updates happening to the server as well as data transfer I was doing. I have a hypothesis, but I don't even want to give it because even to me it sounds sketchy. I'd suggest waiting until you've updated your server and rebooted it prior to connecting any clients though.

Link to comment
Share on other sites

Hi

 

Thanks, I just connected another client 100% successfully so it cant be the server, the other machine had the old connector from HP on it, but the new one didnt. Here below is the clientdeploy logfile if anyone is interested. It didnt really point me to the issue, but maybe I am missing something

 

Cheers

Andrew

 

[4172] 110816.193933.4017: ClientSetup: Entering DownloadSoftwareTask.Run

[4172] 110816.193933.4017: ClientSetup: Download client package ClientCore.cab

[4172] 110816.193933.4117: ClientSetup: Download file ClientCore.cab from server

[4172] 110816.193933.4117: ClientSetup: Making web request: System.Net.HttpWebRequest

[4172] 110816.193940.4117: ClientSetup: Downloaded file C:\Windows\Temp\Client Deployment Files\ClientCore.cab

[4172] 110816.193940.5517: ClientSetup: Found MSI file within cab: ClientCore.msi

[4172] 110816.193940.5517: ClientSetup: Exiting DownloadSoftwareTask.Run

[4172] 110816.193940.5517: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has TaskStatus=Success

[4172] 110816.193940.5517: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has RebootStatus=NoReboot

[4172] 110816.193940.5517: ClientSetup: Running Task with Id=ClientDeploy.InstallSoftware

[4172] 110816.193940.5517: ClientSetup: Entering InstallSoftwareTask.Run

[4172] 110816.193940.5517: ClientSetup: Install package C:\Windows\Temp\Client Deployment Files\ClientCore.msi

[4172] 110816.193940.5617: ClientSetup: Running MSI: C:\Windows\Temp\Client Deployment Files\ClientCore.msi SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* REBOOT=ReallySuppress

[4172] 110816.194250.7574: 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)

[4172] 110816.194250.7574: ClientSetup: RunMsi returned error: RetCode=1603

[4172] 110816.194250.7574: ClientSetup: Failed to install C:\Windows\Temp\Client Deployment Files\ClientCore.msi

[4172] 110816.194250.7574: ClientSetup: Exting InstallSoftwareTask.Run

[4172] 110816.194250.7574: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed

[4172] 110816.194250.7574: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot

[4172] 110816.194250.7574: ClientSetup: Exting ConnectorWizardForm.RunTasks

[4172] 110816.194743.1143: ClientSetup: Running Tasks for Wizard Page InstallationError

[4172] 110816.194743.1143: ClientSetup: Entering ConnectorWizardForm.RunTasks

[4172] 110816.194743.1143: ClientSetup: Running Task with Id=ClientDeploy.UninstallSoftware

[4172] 110816.194743.1143: ClientSetup: Entering UninstallSoftwareTask.Run

[4172] 110816.194743.1143: ClientSetup: Client MSI is not installed

[4172] 110816.194743.1143: ClientSetup: Exiting UninstallSoftwareTask.Run

[4172] 110816.194743.1143: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has TaskStatus=Success

[4172] 110816.194743.1143: ClientSetup: Task with Id=ClientDeploy.UninstallSoftware has RebootStatus=NoReboot

[4172] 110816.194743.1143: ClientSetup: Exting ConnectorWizardForm.RunTasks

[5088] 110816.194743.1343: ClientSetup: Back from the Client Deployment Wizard

[5088] 110816.194743.1443: ClientSetup: Saving Wizard Data

[5088] 110816.194743.1443: ClientSetup: End of ClientDeploy: ErrorCode=1603

Link to comment
Share on other sites

Actually the "ErrorCode=1603" does help. That is either a corrupted MSI file or a conflict with an already installed file. I'm not completely clear from what you wrote which machine had a previous connector software install - the one that worked with the new connector install or the one that didn't. However, you might want to try clearing your browser's cached files and downloading the connector again, or even transferring it from the one that worked.

 

Unfortunately, I'm still betting it is going to have a file conflict, but it might be as simple as the connector file had a hiccup during download. Seems unlikely in a LAN scenario, but might as well rule it out.

Link to comment
Share on other sites

Hi

 

Yeah sorry about the confusion, the newly installed pc worked fine, the old media center pc which had the previous version of the HP Mediasmart Server connector fails. I copied the connector .msi in c:\windows\temp on the one that worked to the one that failed and the same issues occurred.

 

So it seems it is a file conflict... but how do I find out what it is?

 

thanks.

Link to comment
Share on other sites

I just went through this the other night on a newly built machine. It took me 8 hours to get it working. I tried every suggestion I could find all over the net and nothing worked. It would always make it to 95% then back itself up and quit. In the end, I booted the pc into safe mode, deleted everything that had windows server in it. Like the connector, launchpad c:\program files\windows server, I also while in safe mode my normal norton NIS 2011 disabled, I added the connector and dashboard program to the windows firewall exception list.

 

After a reboot the connector installed. I don't know if the firewall or the deleting all Windows Server files off the pc made the difference. In normal operation, I could not delete the Windows Server folder, I was only able to do that in safe mode.

 

FWIW, I had the exact same error messages you are getting in the log file. One last thing, I also changed my server password temporarily just to be sure. After it installed I changed it back. My server password is just a combination up #'s and letters, no symbols or special characters, but after 8 hours, I was willing to try anything. Why this happened when the connector installed flawlessly on 3 prior computers? Well who knows.

 

Good luck.

Edited by jeffla
Link to comment
Share on other sites

Well, we haven't gotten to "throw PC off coast to great white shark" yet, so there is still hope. :)

 

I'm going to laugh when John Z. is right. When I read his comment I did the forehead slapping motion. That should always be the first recommendation. D'oh.

Link to comment
Share on other sites

Well, we haven't gotten to "throw PC off coast to great white shark" yet, so there is still hope.

 

I'm going to laugh when John Z. is right. When I read his comment I did the forehead slapping motion. That should always be the first recommendation. D'oh.

Should we add the proverbial, "Are you sure it's plugged into the wall?" :) :) j/k

Link to comment
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
 Share


×
×
  • Create New...