The Windows Home Server 2011 has encountered an unexpected error (code 1603) on two Vista computers RRS feed

  • Question

  • I am have basic IT skills and am dyslexic so sorry in advance for things that look wrong or that I have misunderstood!

    I was given a server at Christmass. All went well with it and installing WHS 2011 on it and the connection software on my W7 Dell laptop. However since then it’s gone downhill with trying to get the Connection software on a Vista desk top and lap top computers. What I have found and felt capable of trying is below but these are not in the order done!

    The installation is cancelled. The Windows Home Server 2011 has encountered an unexpected error log says error code 1603.

    Rebooted router.

    All computers have WORKGROUP as workgroup name.

    Used MS Find My Server Wizard

    chkdsk and sfc /scannow both said said no problems. Disabled Norton and timeline no change.

    Pinging both server and ip address is OK.

    IpV6 was disabled failed.

    Both Vista’s access the server in network ability to open the shared folders, document’s etc. and via networking on the server you can go into all shared folders on all the computers.

    With both there are accounts created on the server.

    Net was uninstalled and Connection Installer allowed reinstalling.

    Tried safe mode but installed failed as soon started!

    In Windows Media services extender was disabled, changed to manual, no good, Receiver and Scheduler were already manual (reapplied the manual again), changed Network Sharing to Automatic the only difference between the working W7 and Vista laptop!

    I have no idea what else to try now so help would be gratefully received.


    I have found the log and wonder if these errers are the problem

    Hi found the log and saw these at the end are they to do with why its noe working/installing
    SI (s) (08:F8) [12:05:56:560]: Note: 1: 1708
    MSI (s) (08:F8) [12:05:56:636]: Note: 1: 2205 2: 3: Error
    MSI (s) (08:F8) [12:05:56:704]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
    MSI (s) (08:F8) [12:05:56:770]: Note: 1: 2205 2: 3: Error
    MSI (s) (08:F8) [12:05:56:801]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
    MSI (s) (08:F8) [12:05:56:845]: Product:Windows Home Server 2011 Connector -- Installation failed.

    MSI (s) (08:F8) [12:05:56:924]: 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) (08:F8) [12:05:57:001]: Attempting to delete file C:\windows\Installer\7ba0c.msp
    MSI (s) (08:F8) [12:05:57:045]: Unable to delete the file. LastError = 32
    MSI (s) (08:F8) [12:05:57:127]: Deferring clean up of packages/files, if any exist
    MSI (s) (08:F8) [12:05:57:194]: Attempting to delete file C:\windows\Installer\7ba0c.msp
    MSI (s) (08:F8) [12:05:57:246]: MainEngineThread is returning 1603
    MSI (s) (08:48) [12:05:57:334]: RESTART MANAGER: Session closed.
    MSI (

    • Edited by john_71 Friday, December 30, 2011 9:58 AM new information
    Thursday, December 29, 2011 1:09 PM

All replies

  • Hi,


    Do these two files exist? If so, can you delete them manually (or move them to a different folder)?

    Is the net.tcp port sharing service up and running (and at least not set to disabled in services)?

    Best greetings from Germany

    Sunday, January 1, 2012 12:13 PM
  • Olaf

    I can find no trace of the path or 7ba0c.msp with a search.

    net.tcp port sharing service is up and running set on Automatic

    net Listener adapter was disabled so turned that on to automatic, no idea if any use but worth trying?


    I found this  http://social.technet.microsoft.com/Forums/en-smallbusinessserver2011essentials/thread/84e2d89b-767f-43bb-a226-c4a328adc1bb and though it’s a XP PC (my problem ones are Vista 32bit) the errors etc. are the same as I am getting. I did have scheduler errors relating I thing  to changing the PC name but sorted them. Disc clean up ran, cleared the PC install from server, changed PC name. ran CCleaner closed Norton and server fire wall and NO good.



    Sunday, January 1, 2012 1:21 PM
  • net Listener adapter has made no diffrence!
    Sunday, January 1, 2012 1:43 PM
  • I'm having the same problem as above.  I've tried all the ideas listed above and still have the issue.
    Tuesday, July 10, 2012 6:02 AM
  • The only way I ever overcame this with the desk top was to install an education version of W7 upgrade and connecter install worked. The HP laptop still just links vas shared folders.

    Given since I have also found a lot of reports elsewhere of just this issue it’s a common one that MS have solved by now pulling the plug on WHS!

    one that MS have solved by now pulling the plug on WHS!

    Tuesday, July 10, 2012 6:54 AM
  • Given that the connector is in the next version of Essential business server, no they didn't "solve" it by pulling the plug.

    What's the log file say in the client side?

    1603 is normally an installer error, have you tried ensuring that .net 4 is fully up to date and trying the install again?

    Tuesday, July 17, 2012 4:57 AM
  • Hi I feel the majority of information I have seen on the ending of WHS is its end, which is the reports of poor sails are true may be justified.  Bit there is little compassion between it and the replacement program in cost alone. WHS cost me with a HP server about £40 the replacement is said to be over £400 and is reportedly not doing all the useful roles of WHS (monitoring, backups and recovery est.) See http://www.redmondpie.com/windows-home-server-discontinued-microsoft-announces-four-new-editions-for-windows-server-2012/

    What I thought were the main bits of the log were in my 1st post here, the originals were lost when I upgraded to W7.

    For more on what I tried with this see


    It’s a known issue and came up a lot with web searches and no one had a solution to it including it apparently being reported to MS. If a solution is found in other software it doesn’t help with WHS2011 as this is reportedly still going to be sold.

    • Edited by john_71 Tuesday, July 17, 2012 8:43 AM
    Tuesday, July 17, 2012 7:53 AM
  • Sorry I was asking for the log file on Kevin's.

    A solution will still help WHS as it will still be a supported product for many years.

    Tuesday, July 17, 2012 1:50 PM