[Bug] Hang on TVService install (1 Viewer)

[doveman]

To try and eliminate any problems, I stopped TVService and checked it wasn't running in TaskScheduler.

However, MP1.2RC install still hung when it got to installing TVService. I had to kill the install and uninstall exes that were running and when I ran the installer again, it no longer had the upgrade option and said MP1.2 was installed. I went to the deploy folder and ran the package-tvengine.exe and that worked fine.

I've attached the logs from both install attempts, although I can't see anything in either that indicates a problem.

 

[infinite.loop]

Seems that you ran into the issue where tvservice.exe (or one of it's files) is simply "locked" for no visible reason.
0003440: Problems upgrading TVserver on some systems - MediaPortal Bugtracker
Replacing "locked" files will be addressed in the complete rework of our installers in 1.3.0.

 

[mrmojo666]

Seems that you ran into the issue where tvservice.exe (or one of it's files) is simply "locked" for no visible reason.
0003440: Problems upgrading TVserver on some systems - MediaPortal Bugtracker
Replacing "locked" files will be addressed in the complete rework of our installers in 1.3.0.

so what do you suggest as workaround, if someone get in this issue and no way to upgrade anymore?

 

[infinite.loop]

Seems that you ran into the issue where tvservice.exe (or one of it's files) is simply "locked" for no visible reason.
0003440: Problems upgrading TVserver on some systems - MediaPortal Bugtracker
Replacing "locked" files will be addressed in the complete rework of our installers in 1.3.0.

so what do you suggest as workaround, if someone get in this issue and no way to upgrade anymore?

run the 2 separate nsis installers which are unpacked into your temp folder manually like doveman did.

 

[doveman]

Running the package-tvengine.exe (in the temp folder) manually worked for me, so perhaps the issue is with the main installer. Hopefully this workaround will work for others as well.

Ah, infinite.loop beat me to it by seconds

 

[infinite.loop]

Running the package-tvengine.exe (in the temp folder) manually worked for me, so perhaps the issue is with the main installer.

The deploytool (GUI for the installation) does nothing else than run package-tvengine.exe with a silent switch.
It is the package-tvengine.exe that fails to replace the (locked) file.

We will take good care of this in 1.3.0.

 

[doveman]

The deploytool (GUI for the installation) does nothing else than run package-tvengine.exe with a silent switch.
It is the package-tvengine.exe that fails to replace the (locked) file.

We will take good care of this in 1.3.0.

But if you look at the earlier of the two logs I posted it seems to have completed installing TVService and the last two lines are:
[ INFO] Starting SetupTv.exe --DeployMode...
[ DEBUG ] FUNCTION .onInstSuccess

So I don't understand how this fits with the idea that it got stuck trying to replace a locked file. Why did SetupTV.exe never execute if it was called?

 

[infinite.loop]

The deploytool (GUI for the installation) does nothing else than run package-tvengine.exe with a silent switch.
It is the package-tvengine.exe that fails to replace the (locked) file.

We will take good care of this in 1.3.0.

But if you look at the earlier of the two logs I posted it seems to have completed installing TVService and the last two lines are:
[ INFO] Starting SetupTv.exe --DeployMode...
[ DEBUG ] FUNCTION .onInstSuccess

So I don't understand how this fits with the idea that it got stuck trying to replace a locked file.

Currently there is a lot logic put into the deploytool and the NSIS installers. This does cause a lot of problems in some cases.
Also leads to wrong info loged sometimes.

During the rework of the installers we will place all the install/upgrade logic into the deploytool.
This will help us to get better info when something goes wrong during install/upgrade and then also forward that info to the user that he also knows what just happened.

Why did SetupTV.exe never execute if it was called?

Many possible reasons.
- It crashes because tvservice.exe was still the old one.
- It is missing
- etc.

All that will be tackled during the rework. Because then the installer will check if all the files, with the correction version are actually in place.
And if they are not, a reboot is requested and the files are moved into position at boottime. Then installation will continue.

 

[doveman]

Cool. Was just confused by that log, but you obviously know what's going on