Bug 14797 - WHS MSI package fail to install
: WHS MSI package fail to install
Status: CLOSED INVALID
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Installer
: 7.4.1
: PC Windows Home Server
: P1 normal (vote)
: Investigating
Assigned To: James Richardson
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-10-16 09:18 UTC by James Richardson
Modified: 2012-02-27 17:19 UTC (History)
3 users (show)

See Also:
Category: Bug


Attachments
First error message on install (105.53 KB, image/jpeg)
2009-10-16 09:18 UTC, James Richardson
Details
Second error message on install (98.84 KB, image/jpeg)
2009-10-16 09:20 UTC, James Richardson
Details
Third error message on install (19.23 KB, image/jpeg)
2009-10-16 09:21 UTC, James Richardson
Details

Note You need to log in before you can comment on or make changes to this bug.
Description James Richardson 2009-10-16 09:18:35 UTC
Created attachment 6132 [details]
First error message on install

Please see attached images.  Attempting to install 7.4.1 r28887 on WHS will
fail.

is there any extra logs you need?
Comment 1 James Richardson 2009-10-16 09:19:20 UTC
First error box is during install
Comment 2 James Richardson 2009-10-16 09:20:24 UTC
Created attachment 6133 [details]
Second error message on install

Second error message happens after you click Abort on the 1st message
Comment 3 James Richardson 2009-10-16 09:21:26 UTC
Created attachment 6134 [details]
Third error message on install

Third error box that happens after clicking Cancel on 2nd error

Clicking Retry on 2nd dialog will just 'bump'
Comment 4 Michael Herger 2009-10-16 11:35:56 UTC
Was this a fresh install or an update? What have you been running before (if you did)? Did yountry to redownload the file?

I installed the same build perfectly fine today.
Comment 5 James Richardson 2009-10-16 11:55:17 UTC
This was an 'upgrade' from yesterdays build.

uninstalled 28862 > installed 28887 (no reboot of server)

Downloaded the file from http://downloads.slimdevices.com/nightly/7.4/sc/

28862 > 28887
Comment 6 James Richardson 2009-10-16 11:59:56 UTC
I am able to install 28862, even after getting the errors.
Comment 7 Michael Herger 2009-10-16 12:10:04 UTC
Did you download the file on the server itself, or on a client machine?  
How did you move it to the add-on folder?
Comment 8 Michael Herger 2009-10-16 12:10:36 UTC
> I am able to install 28862, even after getting the errors.

You can install in a second trial, or does it work fine, even with the  
errors?
Comment 9 James Richardson 2009-10-16 12:50:11 UTC
download the .msi from a Client system, open up the link to the Shared Folders, move the file from Client to //software/add-ins folder

Launch the WHS Console on the Client system

Navigate to Settings > Add-Ins >  Uninstall current version r28862

WHS Console times out

Restart Console, Navigate to Settings > Add-Ins > Install new version r28887

See error messages
=============================

Since getting these, I have performed a 'full' uninstall, going so far as to find and remove any and all SBS files/folders on WHS by logging onto the box.

Download fresh copies of r28862 & r28887 and move them to the //add-ins folder

I still had the same issues.

THEN, I mistakenly Double Clicked on the 28887.MSI folder while logged onto the box via Remote Desktop,  strangely enough SBS installed.  I then went to the WHS Console to see if the add-in showed up, it did not.

When I tried to install via  Settings > Add-Ins, SBS attempted to 'uninstall' its self, which it did.  I was then able to install 28887 with out any errors
==========================

Since we have not 'officially' released WHS yet, I don't know how you want to handle this bug.  I'm willing to close it for now, or leave it in my bucket to investigate further.
Comment 10 Michael Herger 2009-10-16 22:52:55 UTC
Let's not have this hold off 7.4.1. Can't reproduce this :-(
Comment 11 Michael Herger 2009-10-16 23:33:00 UTC
FWIW: just tried this on another WHS installation. No problem at all.
Comment 12 James Richardson 2009-10-20 11:23:53 UTC
The server I was using crashed, I think this caused the errors I was seeing.
Comment 13 James Richardson 2012-02-27 17:19:04 UTC
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version.  If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.