WHS install error message -- ignore

[Grasshopper]

Yesterday afternoon I decided to upgrade my WHS Sage install from 6.3.5 to 6.3.10. As per other Sage upgrades I've done, I thought it'd be just fine to simply stop the Sage service and install the new version right over the old. So I saved the msi to the Add-ins folder and logged into WHS. The new version appeared as an available add-in, so I stopped the service using the WHS console tab and clicked Install. The old version was still installed as an add-in.

It processed for a while, then popped up an error message -- something like "Windows needs to stop the following program -- SageTV". Three choices, Abort/Retry/Ignore. I was confused, since I knew the service was stopped and the UI wasn't running on the server. So I hit Retry. Same error.

I thought about it for a bit, then ran down to the basement and logged in locally to my WHS box to confirm that the Sage UI wasn't running. After doing this I figured that the only Sage related program that could possibly be throwing that error message was whatever makes the SageTV tab in the WHS console. So I saved my properties and wiz.bin to a flash drive (just in case), clicked Ignore, and crossed my fingers.

Worked fine.

Hope this helps somebody...

[oaamaas]

I'll add that the upgrade from 6.3.5 on my WHS did behave strange. I was told to reboot the server after the uninstall (I think). Anyway - my add-in page still shows the old 6.3.5 along with the current in "Installed" tab. Since everything works fine I don't bother - but 6.3.5 had some issues for sure.

Then I think I should comment to the way you upgraded - that's not the way to upgrade an Add-in on the WHS. Do it like this the next time to avoid errors:
1 - Stop the service
2 - In Add-ins "Installed" tab: Uninstall the current version
3 - Restart the WHS console (you'll have to)
4 - In Add-ins "Available" tab: Install the new version
5 - Restart the WHS console (you'll have to)
You could of course make a backup of the wiz.bin upfront of the upgrade, but there's really no need.

[inlvnv]

My upgrade path was same as the above poster. No problem that I've noticed.