none
Net.Tcp Port Sharing Service WHS 2011 connector

    Întrebare

  • Not sure if this is the right place....pleae advise or move if necessary.

    Trying to add XP pro clients to WHS 2011 using Connect.

    Connect install dies at about 95%...log shows issue with Net.Tcp port sharing service.

    I have four XP machines all running net 4.0, current updates....none of them will start the service.

    Reg points to correct folder...think this might be a problem with the new update?

     

    Thanks for input, suggestions, etc....

    • Mutat de edhickey 26 august 2011 14:23 (From:.NET 4: Windows Workflow Foundation)
    25 august 2011 23:55

Toate mesajele

  • FYI, I replaced the SMSvcHost and SMSvcHost.exe.config files found in C:\WINDOWS\Microsoft.NET\Framework\v4.0.30319 with the ones located C:\WINDOWS\Microsoft.NET\Framework\v3.0\Windows Communication Foundation.

    Service then started and connect software for WHS completed.  

     

    PLEASE have this information provided to or posted in a form that will let someone from Microsoft look into these files to find the problem.  If you know of issues this might cause in my system please let me know.

     

    Thanks,


    **********UPDATE NOTE**********

    I had this posted in the NET 4: Windows Workflow Foundation because I'm fairly positive this is a Net Framework issue with V4 and windows XP.  They apparently believe it is a WHS issue and have moved it to this forum.  If you know anyone in the NET development team that will look at this issue let them know...I'm done with messing with this 20 hrs. wasted time to install clients on a WHS....I think I could have taught myself to work with linux in that time....Will not pay for another MS product for a while.  Thanks all.

    26 august 2011 04:15
  • js, could you please post a bug on Connect? The URL is

    http://connect.microsoft.com/WindowsHomeServer

    For what it's worth, I think you're more likely to be right about where the issue lies than the folks who moved your post here. :) Especially so if any of your clients with the issue had never been joined to Windown Home Server as a client.


    I'm not on the WHS team, I just post a lot. :)
    26 august 2011 17:32
    Moderator
  • Thanks for the input. This was my first WHS build...it went so smooth to begin with.  None of my clients had ever been connected to WHS.  Some of the XP computers had OS installed years ago...one was only a month old (that's what made me look for another solution, didn't think it was a file permission issue or security certificate issue).  I have posted in the other forum per your suggestion...don't know if it went to the right place. http://social.microsoft.com/Forums/en-US/whshardware/thread/9617865b-2827-405d-90c5-58a804f55126 I have also posted in the we got served forum.  I'm sure others will have this problem if not corrected.  I don't know if it just has to do with the new WHS update since I never tried to connect to it prior to installing the update.  I think I got new Net 4.0 updates right before this also...don't really know.  I do know I updated everything Client and Server prior to trying.  PS...all clients healthy and backed up! I'm much happier now....just not many places to go for help with a DIY build. 
    26 august 2011 18:27
  • Do you have installed on that machine any one of the following?

    a. Acronis
    b. Quickbooks
    c. Forefront a/v
    d. Microsoft security essentials?
    3 octombrie 2011 23:10
  • Microsoft Security Essentials installed on all clients.
    3 octombrie 2011 23:16
  • Interesting, that Susan asks about Acronis! I have installed Acronis True Image Home on one Windows XP client and I also have this issue. But I could connect another Windows 7 client with an installed Acronis without problems. So therefore, I don't think, that this is a critical software. Could Windows Intune be a problem? That is installed on the pc.

    When I try to connect the faulty PC (Windows XP, SP3) to the server Windows Small Business 2011 Essentails, it also fails because the service NetTcpPortSharing cannot be started.

    I could see, that the service will even not start, when I try to start it manually. But the tip with copying the files from the .NET 3.0 is also not working in my case. Until now, I don't have an idea to fix this!  Also I have tested the connector after a complete de- and installation of .NET (2.0, 3.0, 3.5, 4.0) and all updates. This was also not working.

    The only chance, to start the service is to change the accounts from Local Service to Local System Account. But I think, this is not a solution, because I don't know about the drawbacks.

    Has anyone the same issues?

    7 octombrie 2011 21:47
  • FIXED!!! The XP-Machine is really old and some "normal" rights had gone lost: The service NetTcpPortSharing needs the rights to read to the root drive C:! I found that hint at http://kb.herator.se/index.php/article/comment.

    Because this right was missing, the error "The process was terminated due to stack overflow" with the id 1027 was reported in the event log and the error message "Error 1053 - service could not be started" was popped up.

    After I corrected that, the service could be started and the PC was connected to the server Windows Small Business 2011 Essentails.

    • Propus ca răspuns de RoDiPa 17 octombrie 2011 23:15
    17 octombrie 2011 23:15
  • I recently had an issue with security update for net framework:  This might also help people with .net issues, i.e. complete removal and re-install.

     

    Microsoft response to update issue:

    From your description, I understand that KB2572067 failed to install. If I have misunderstood your concern, please do not hesitate to let me know. 

     

    I understand the inconvenience you have experienced. Please be assured that I will do my best to help you.

     

    Before moving on, I would like to let you know that .NET Framework 1.1 was designed for the developers. As the general user, I suggest installing .NET Framework 3.5 directly.

     

    Step 1: Remove .NET Framework using removal tool

    ================================

    1. Please download the tool from the following link:

    http://www.box.net/shared/3f6vezktt9

     

    Please Note: The third-party product discussed here is manufactured by a company that is independent of Microsoft. We make no warranty, implied or otherwise, regarding this product's performance or reliability.

     

    2. Please save the zip file (dotnetfx_cleanup_tool.zip) from the above link to the local Desktop and extract it.

    3. Double click cleanup_tool.exe to run the tool.

    4. Please follow the instructions given.

    In the "Product to cleanup:" box, please select ".NET Framework – All versions".

    5. Click "Cleanup Now" button.

    6. Restart the computer.

     
    Step 2: Manually downloading and installing Microsoft .NET Framework 3.5
    =======================================================
    Please note: The size of Microsoft .NET Framework 3.5 and .NET Framework 3.5 Service Pack 1 is a little big. Your patience to download the update is much appreciated. 
     
    1. Click the following link: 
     
    Microsoft .NET Framework 3.5 and .NET Framework 3.5 Service Pack 1
    http://download.microsoft.com/download/2/0/E/20E90413-712F-438C-988E-FDAA79A8AC3D/dotnetfx35.exe 
     
    Microsoft .NET Framework 3.5 SP1 and .NET Framework 2.0 SP2 Update for Windows Server 2003 and Windows XP x86 (KB982524)

    http://download.microsoft.com/download/4/2/6/426111FA-E964-44A1-B84E-90EAB1DE3EC8/NDP30SP2-KB982524-x86.exe

     
    2. When the file download window appears, please click "Save", and follow the directions to save it on the Desktop. After downloading the Microsoft .NET Framework 3.5 setup file on your Desktop, double-click to manually install it. (Please install dotnetfx35.exe first.)

     

    Please try the above steps and inform me of the results at your earliest convenience. If anything in my email is unclear or you have any questions, please don't hesitate to let me know.

     

    I look forward to your reply.

     

    Best regards,

    Kim Zhou

    18 octombrie 2011 16:14
  • Excuse me I have 1.1 on a machine because of Quickbooks. I have to install it people.
    18 octombrie 2011 16:24
  • Not sure what the "Excuse me...people" is for....?

    Doing the "fix" above that microsoft suggested left my machine "windows xp Media Center" with the following .NET installed:

    .Net 1.0 Hotfix

    .Net 1.1

    .Net 2.0 sp2

    .Net 3.0 sp2

    .Net 3.5 sp1

    .Net 4 client

    .Net 4 extended

     

    when I was done....unfortunately now back to not connecting to the server.  Have uninstalled connector software and just had a failure of the re-install.

    Will try the fixes above again!

    20 octombrie 2011 04:36
  • The comment "Before moving on, I would like to let you know that .NET Framework 1.1 was designed for the developers. As the general user, I suggest installing .NET Framework 3.5 directly."  I have to have .net 1.1 installed. 

    20 octombrie 2011 04:48
  • Is your c drive a basic disk or a dynamic disk btw?
    20 octombrie 2011 04:48
  • That whole post was a quote from an email from microsoft support...I am an end user.
    20 octombrie 2011 18:40
  • My c drive is basic.

    I believe I am getting past the NetTcpPortSharing issue....I have the service running.

     

    I still can not install connector software. Quits at like 99%.

     

    Your link http://kb.herator.se/index.php/article/comment. is dead.  I would like to try it and see if it works....please provide more details.

     

    Thanks, 

    20 octombrie 2011 18:42
  • Can you post up the client connector log file please?

    http://social.technet.microsoft.com/wiki/contents/articles/3887.aspx

    20 octombrie 2011 18:46
  • Thank you for your help.

     

    Background:  This computer used to connect to the server just fine.  The .NET patch/security (whatever it was) update around the 11th of Oct. wouldn't install.  To install they had me uninstall .NET i.e. info above, then install it again.  The computer than updated .NET, it would no longer connect to the server.  The first time this computer was connected to the server late Aug. early Sept. it had issues with the Net.Tcp Port Sharing service not starting.  I had to use the SMSvcHost.exe.config and SMSvcHost from .NET 3.0 in .NET v4.0.30319 to get it to start.  I had the same issue this time (I used the Net 3.0 SmsvcHost files again), only it now starts NetTcpPort Sharing but I still can not complete the connector install.  It dies at about 99%.  Message "The installation is cancelled: The Windows Home server 2011 connector has encountered an unexpected error."   I have verified that NetTcp Port Sharing is started (it starts on it's own).

    I have also noticed that IIS is not running or even showing in services client windows xp media center (Internet Information Service)....don't think it matters, I know it has to be running on server and it is.  Media Center extender service and scheduler service are running (others have said they are necessary).

    I have cleared the log, run the connector software....below is the new log.

    ---------------------------------------------------------

    [3016] 111020.123536.7343: ClientSetup: Start of ClientDeploy

    [3016] 111020.123536.9218: General: Initializing...C:\WINDOWS\Temp\Client Deployment Files\ClientDeploy.exe

    [3016] 111020.123536.9375: ClientSetup: Loading Wizard Data

    [3016] 111020.123537.2968: ClientSetup: Current DeploymentStatus=Failed

    [3016] 111020.123537.8593: ClientSetup: Showing the Client Deployment Wizard

    [3016] 111020.123538.1718: ClientSetup: Adding Server Info data in the Product Registry

    [3016] 111020.123538.2968: ClientSetup: Set the Deployment Sync Event

    [728] 111020.123553.6093: ClientSetup: Running ValidateUser Tasks at WizardPage HomeServerCred

    [728] 111020.123553.6250: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [728] 111020.123553.6250: ClientSetup: Running Task with Id=ClientDeploy.ValidateUser

    [728] 111020.123553.6718: ClientSetup: Entering ValidateUserTask.Run

    [728] 111020.123553.6875: ClientSetup: Install root cert to local trusted store

    [728] 111020.123553.7656: ClientSetup: Validating User

    [728] 111020.123553.7656: ClientSetup: Call MachineIdentityManager.GetMachineStatus

    [728] 111020.123559.5156: ClientSetup: Current Machine Join Status: ActiveWithCert

    [728] 111020.123559.5156: ClientSetup: Exiting ValidateUserTask.Run

    [728] 111020.123559.5156: ClientSetup: Task with Id=ClientDeploy.ValidateUser has TaskStatus=Warning

    [728] 111020.123559.5156: ClientSetup: Task with Id=ClientDeploy.ValidateUser has RebootStatus=NoReboot

    [728] 111020.123559.5156: ClientSetup: Exting ConnectorWizardForm.RunTasks

    [728] 111020.123559.5156: ClientSetup: Running JoinNetwork Tasks at WizardPage HomeServerCred

    [728] 111020.123559.5156: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [728] 111020.123559.5156: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork

    [728] 111020.123559.5156: ClientSetup: Entering JoinNetworkTask.Run

    [728] 111020.123559.5156: ClientSetup: Network Join Client to Server: ClientComputerName=HTPC ServerName=SERVER

    [728] 111020.123559.5156: ClientSetup: Maximum amount of joined machines: 15

    [728] 111020.123559.5156: ClientSetup: Current amount of joined machines: 7

    [728] 111020.123559.5156: ClientSetup: Server already contains a computer joined with Client Machine Name

    [728] 111020.123559.5156: ClientSetup: Network Join has not been forced

    [728] 111020.123559.5156: ClientSetup: Network Join will not be Run

    [728] 111020.123559.5156: ClientSetup: Exiting JoinNetworkTask.Run

    [728] 111020.123559.5156: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Retry

    [728] 111020.123559.5156: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot

    [728] 111020.123559.5156: ClientSetup: Exting ConnectorWizardForm.RunTasks

    [3016] 111020.123559.5312: ClientSetup: JoinNetwork Tasks returned TaskStatus=Retry

    [728] 111020.123601.0000: ClientSetup: Running JoinNetwork Tasks at WizardPage ComputerAlreadyExists

    [728] 111020.123601.0000: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [728] 111020.123601.0000: ClientSetup: Running Task with Id=ClientDeploy.JoinNetwork

    [728] 111020.123601.0000: ClientSetup: Entering JoinNetworkTask.Run

    [728] 111020.123601.0000: ClientSetup: Network Join Client to Server: ClientComputerName=HTPC ServerName=SERVER

    [728] 111020.123601.0000: ClientSetup: Maximum amount of joined machines: 15

    [728] 111020.123601.0000: ClientSetup: Current amount of joined machines: 7

    [728] 111020.123601.0000: ClientSetup: Server already contains a computer joined with Client Machine Name

    [728] 111020.123601.0000: ClientSetup: Network Join has been forced

    [728] 111020.123601.0000: ClientSetup: Running Network Join

    [728] 111020.123601.0000: ClientSetup: Call MachineIdentity.GetCert

    [728] 111020.123609.8593: ClientSetup: Exiting JoinNetworkTask.Run

    [728] 111020.123609.8593: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has TaskStatus=Success

    [728] 111020.123609.8593: ClientSetup: Task with Id=ClientDeploy.JoinNetwork has RebootStatus=NoReboot

    [728] 111020.123609.8593: ClientSetup: Exting ConnectorWizardForm.RunTasks

    [3016] 111020.123609.8750: ClientSetup: JoinNetwork Tasks returned TaskStatus=Success

    [728] 111020.123615.7343: ClientSetup: Running Tasks for Wizard Page ConfiguringComputer

    [728] 111020.123615.7343: ClientSetup: Entering ConnectorWizardForm.RunTasks

    [728] 111020.123615.7343: ClientSetup: Running Task with Id=ClientDeploy.PrepareClient

    [728] 111020.123615.7500: ClientSetup: Entering PrepareClientTask.Run

    [728] 111020.123615.7656: ClientSetup: Ensuring that ServiceName=NetTcpPortSharing is Running

    [728] 111020.123615.7968: ClientSetup: Ensuring that ServiceName=SSDPSRV is Running

    [728] 111020.123615.8125: ClientSetup: Enabling Compression on the Log Directory.

    [728] 111020.123618.5000: ClientSetup: Exiting PrepareClientTask.Run

    [728] 111020.123618.5000: ClientSetup: Task with Id=ClientDeploy.PrepareClient has TaskStatus=Success

    [728] 111020.123618.5000: ClientSetup: Task with Id=ClientDeploy.PrepareClient has RebootStatus=NoReboot

    [728] 111020.123618.5000: ClientSetup: Running Task with Id=ClientDeploy.DownloadSoftware

    [728] 111020.123618.5468: ClientSetup: Entering DownloadSoftwareTask.Run

    [728] 111020.123618.5468: ClientSetup: Download client package ClientCore.cab

    [728] 111020.123618.5468: ClientSetup: Download file ClientCore.cab from server

    [728] 111020.123618.5468: ClientSetup: Making web request: System.Net.HttpWebRequest

    [728] 111020.123628.8906: ClientSetup: Downloaded file C:\WINDOWS\Temp\Client Deployment Files\ClientCore.cab

    [728] 111020.123629.1875: ClientSetup: Found MSI file within cab: ClientCoreX86.msi

    [728] 111020.123629.1875: ClientSetup: Found MSP file within cab: KB2554637-x86.msp

    [728] 111020.123629.1875: ClientSetup: Exiting DownloadSoftwareTask.Run

    [728] 111020.123629.1875: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has TaskStatus=Success

    [728] 111020.123629.1875: ClientSetup: Task with Id=ClientDeploy.DownloadSoftware has RebootStatus=NoReboot

    [728] 111020.123629.1875: ClientSetup: Running Task with Id=ClientDeploy.InstallSoftware

    [728] 111020.123629.1875: ClientSetup: Entering InstallSoftwareTask.Run

    [728] 111020.123629.1875: ClientSetup: Install package C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi

    [728] 111020.123629.2187: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* PATCH="C:\WINDOWS\Temp\Client Deployment Files\KB2554637-x86.msp" REBOOT=ReallySuppress

    [728] 111020.123906.8125: 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)

    [728] 111020.123906.8125: ClientSetup: RunMsi returned error: RetCode=1603

    [728] 111020.123906.8125: ClientSetup: Failed to install C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi

    [728] 111020.123906.8125: ClientSetup: Exting InstallSoftwareTask.Run

    [728] 111020.123906.8125: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has TaskStatus=Failed

    [728] 111020.123906.8125: ClientSetup: Task with Id=ClientDeploy.InstallSoftware has RebootStatus=NoReboot

    [728] 111020.123906.8125: ClientSetup: Exting ConnectorWizardForm.RunTasks

     

     

    As you can see NetTcpSharing passes...looks like issue with ClientCoreX86.msi 

    error code 1603.

     

    What should I try next?

     

    Thanks

    20 octombrie 2011 19:57
  • Found this in the ClientCoreX86.msi LOG

     

    This stands out:

    "Update Rollup for Microsoft Windows (KB2554637)"

     

     

    === Logging stopped: 10/20/2011  12:39:06 ===

    MSI (s) (B8:88) [12:39:06:578]: Product: Windows Home Server 2011 Connector - Update 'Update Rollup for Microsoft Windows (KB2554637)' could not be installed. Error code 1603. Additional information is available in the log file C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs\ClientCoreX86.msi.log.

     

    MSI (s) (B8:88) [12:39:06:578]: Windows Installer installed an update. Product Name: Windows Home Server 2011 Connector. Product Version: 6.1.8800.16389. Product Language: 1033. Update Name: Update Rollup for Microsoft Windows (KB2554637). Installation success or error status: 1603.

     

    MSI (s) (B8:88) [12:39:06:578]: Note: 1: 1708 

    MSI (s) (B8:88) [12:39:06:593]: Note: 1: 2205 2:  3: Error 

    MSI (s) (B8:88) [12:39:06:593]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708 

    MSI (s) (B8:88) [12:39:06:593]: Note: 1: 2205 2:  3: Error 

    MSI (s) (B8:88) [12:39:06:593]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 

    MSI (s) (B8:88) [12:39:06:593]: Product: Windows Home Server 2011 Connector -- Installation failed.

     

    MSI (s) (B8:88) [12:39:06:593]: Windows Installer installed the product. Product Name: Windows Home Server 2011 Connector. Product Version: 6.1.8800.16389. Product Language: 1033. Installation success or error status: 1603.

     

    MSI (s) (B8:88) [12:39:06:593]: Attempting to delete file C:\WINDOWS\Installer\c880dc.msp

    MSI (s) (B8:88) [12:39:06:609]: Unable to delete the file. LastError = 32

    MSI (s) (B8:88) [12:39:06:609]: Cleaning up uninstalled install packages, if any exist

    MSI (s) (B8:88) [12:39:06:609]: Attempting to delete file C:\WINDOWS\Installer\c880dc.msp

    MSI (s) (B8:88) [12:39:06:609]: MainEngineThread is returning 1603

    MSI (s) (B8:50) [12:39:06:718]: No System Restore sequence number for this installation.

    MSI (s) (B8:50) [12:39:06:734]: User policy value 'DisableRollback' is 0

    MSI (s) (B8:50) [12:39:06:734]: Machine policy value 'DisableRollback' is 0

    MSI (s) (B8:50) [12:39:06:750]: Incrementing counter to disable shutdown. Counter after increment: 0

    MSI (s) (B8:50) [12:39:06:750]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 

    MSI (s) (B8:50) [12:39:06:750]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2 

    MSI (s) (B8:50) [12:39:06:765]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

    MSI (s) (B8:50) [12:39:06:765]: Restoring environment variables

    MSI (c) (E4:38) [12:39:06:781]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

    MSI (c) (E4:38) [12:39:06:781]: MainEngineThread is returning 1603

    === Verbose logging stopped: 10/20/2011  12:39:06 ===

    20 octombrie 2011 20:25
  • Searching updates installed on my computer and KB2554637 is not found!  It appears this update comes from the server....don't know how to install it directly?  I have checked server for update rollup 1 2554634  (http://support.microsoft.com/kb/2554634/ ) and can not find it...I know it was installed, came out a day or two prior to my build....I can not find it on the server?  Windows update on server does not offer it to me.


    I show WHS 2011 SP1 installed...is it possible this update was included in SP1 and not needed?  Really confused now....just don't want to mess with this anymore!
    20 octombrie 2011 20:25
  • It's part of the push out from the server.

    When you try to install an update for the .NET Framework 1.0, 1.1, 2.0, 3.0, or 3.5, you may receive Windows Update error code "0x643" or Windows Installer error code "1603":
    http://support.microsoft.com/kb/923100

    1603 is generic installer barf.  See if that windows installer fix up in that link will help you.

    20 octombrie 2011 20:35
  • Thanks for the suggestion...didn't work.

     

    I have confirmed that the update rollup kb2554234 is installed on server...thus it should push the update kb2554637 to the client or install when connector is run.  It shouldn't appear on the client until the connector software completes....why this is not installing I do not know.

    20 octombrie 2011 21:32
  • I just don't know when to quit.....Trying this now "Article ID: 834484 - Last Review: August 18, 2011 - Revision: 5.0

    You receive an "error 1603: A fatal error occurred during installation" error message when you try to install a Windows Installer package"

    http://support.microsoft.com/kb/834484

     

    Waiting........waiting..........

     

    Trying Connector..........waiting..........waiting.........waiting.........waiting.......FAILURE!!!!

     

    Client Deploy Log:

    Install package C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi

    [4840] 111020.154931.8757: ClientSetup: Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* PATCH="C:\WINDOWS\Temp\Client Deployment Files\KB2554637-x86.msp" REBOOT=ReallySuppress

    [4840] 111020.155152.8913: 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)

    [4840] 111020.155152.8913: ClientSetup: RunMsi returned error: RetCode=1603

     

    ClientCoreX86.msi LOG:

    === Logging stopped: 10/20/2011  15:51:52 ===

    MSI (s) (6C:A4) [15:51:52:657]: Product: Windows Home Server 2011 Connector - Update 'Update Rollup for Microsoft Windows (KB2554637)' could not be installed. Error code 1603. Additional information is available in the log file C:\Documents and Settings\All Users\Application Data\Microsoft\Windows Server\Logs\ClientCoreX86.msi.log.

     

    MSI (s) (6C:A4) [15:51:52:657]: Windows Installer installed an update. Product Name: Windows Home Server 2011 Connector. Product Version: 6.1.8800.16389. Product Language: 1033. Update Name: Update Rollup for Microsoft Windows (KB2554637). Installation success or error status: 1603.

     

    I quit!

     

     

     

     

    20 octombrie 2011 22:59
  • Apologies, I didn't get pack to you.  I think you are going to have to rip out .net and reinstall it.
    30 octombrie 2011 06:52
  • Still have not resolved this, had been using retrospect for back up EMC.

    Trying to get around this...re-read post.

    I do have an Acronis driver for my sis raid drives.

    ClientCoreX86.msi error 1603 during install.

    Client Deploy logs:

    Running MSI: C:\WINDOWS\Temp\Client Deployment Files\ClientCoreX86.msi  SOFTWARE_NAME="Windows Home Server 2011" ADMIN_USERNAME="Administrator" ADMIN_PASSWORD=******* PATCH="C:\WINDOWS\Temp\Client Deployment Files\KB2630445-x86.msp" REBOOT=ReallySuppress
    [3596] 120223.100513.7031: ClientSetup: Running MSI threw an exception:Microsoft.Deployment.WindowsInstaller.InstallerException: Fatal error during installation.

    23 februarie 2012 17:35
  • thanks for the solution

    This fix is working for me to...

    1 mai 2012 15:23