Open Source Windows Installer

[jusjoken]

Originally Posted by rnadeau

This is the log file you asked for.

HUGE log file

I will get better at reading these over time but I found the issue (I believe).

The creation of the firewall rules is failing as the firewall on your machine is reporting that it is OFF/Disabled. If this is indeed the case please enable it and rerun the setup and let me know if it works ok (then feel free to disable it after again).

I have changed the installer code to ignore these errors so the next installer should work fine for this situation if the firewall is disabled.

Hopefully this is the real issue....difficult to find but easy to fix

Thanks
k

[rnadeau]

Thanks for the firewall tip. that did it. I installed over sage 7.1.9 with version 9 exe files installed over that. I also use the schedules direct program guide plugin. The install went fine and everything works right "EXCEPT"

When sagetv started, it showed me sagtev 7 default screen and the link to enable Gemstone. I clicked it and my setup was back to normal. Not a major issue. It also changed my custom video menus to all the same options. Had to go back into option and rest filters for the different menus. Again not a big issue.

I use Fuzzy's external dvd playback plugin and have Zoomplayer Max setup to play the dvds. I guess somehow the zoomplayer filters must have gotten uninstalled or unregistered because zoomplayer gave error message with filter error. I reinstalled zoomplayer over itself and all is working fine. I know the zoomplayer isn't part of the install, but wanted to mention it for someone elses benefit.

edit: After restarting Sagetv, the menus were all correct.

Thanks for the great work!

[jusjoken]

I have noticed on occasion that SageTV reverts some settings. Not sure what triggers it...perhaps the new STV, or the new Sage.jar or something else. The actual properties files are all retained as far as I have seen so in theory Sage should start exactly as it was previously configured.

Perhaps others may know what the trigger is that makes it load the default STV...then we may be able to change something so it does not revert when it really should not.

k

[bryanzim]

The next time I attempt a newer install from beta 001, I will enable the debug mode and create a log. Unfortunately, I did not save my directory before the upgrading and after several hours of getting back to a stable state in 001, I was not ready to attempt again.

On a side note I did have my firewall enabled during the install, so I do not think that was the cause of my HD Home Run failures.

If other people have had successful SiliconDust tuners install with beta 003 then it would be good to hear.

[sacrament055]

Originally Posted by jusjoken

I have noticed on occasion that SageTV reverts some settings. Not sure what triggers it...perhaps the new STV, or the new Sage.jar or something else. The actual properties files are all retained as far as I have seen so in theory Sage should start exactly as it was previously configured.

Perhaps others may know what the trigger is that makes it load the default STV...then we may be able to change something so it does not revert when it really should not.

k

My Gemstone config has reset to default every time I update the JAR so that might be it.

[Narflex]

Originally Posted by jusjoken

I have noticed on occasion that SageTV reverts some settings. Not sure what triggers it...perhaps the new STV, or the new Sage.jar or something else. The actual properties files are all retained as far as I have seen so in theory Sage should start exactly as it was previously configured.

Perhaps others may know what the trigger is that makes it load the default STV...then we may be able to change something so it does not revert when it really should not.

k

This property defaults to true "wizard/revert_stv_on_upgrade". And then will cause the STV to be reset to the V7 one after an upgrade of SageTV versions. We did this because too many people had problems with custom STVs when we did software upgrades and we wanted to isolate out those problems.

This setting is in UIManager.java; and I have no problem approving a change which sets the default value to be false.

[bryanzim]

I have retested with the latest installer. I confirmed that the correct Firewall entries have been made. However, I still experience capture failure with beta 003 where the beta 001 installer works.

I have attached the setup logs using the /log option.

[jusjoken]

Originally Posted by bryanzim

I have retested with the latest installer. I confirmed that the correct Firewall entries have been made. However, I still experience capture failure with beta 003 where the beta 001 installer works.

I have attached the setup logs using the /log option.

I am sorry I should have been clearer. I need to see the sagetv_x.txt server log file with debug enable and a capture failure so I or perhaps Jeff can see what might be wrong in the install.

k

[Skirge01]

@jusjoken: First, thanks so much for taking this part of the OSS project on!

Second, I just did a server install on a brand new Windows 7 Pro (64 bit) OS in a VM, using the beta 003 installer. During install, I entered the EPG license, used the default install location, started the service control, changed the user and password and then stopped. I was about to check which ports needed to be opened and went into Windows Firewall to verify that nothing had been done already. I was a bit surprised to see that the following entries were made.

This looks as though the default install is set to open up absolutely everything to the SageTV service. Am I reading that right? If so, is that intentional?

[BobPhoenix]

Originally Posted by Skirge01

@jusjoken: First, thanks so much for taking this part of the OSS project on!

Second, I just did a server install on a brand new Windows 7 Pro (64 bit) OS in a VM, using the beta 003 installer. During install, I entered the EPG license, used the default install location, started the service control, changed the user and password and then stopped. I was about to check which ports needed to be opened and went into Windows Firewall to verify that nothing had been done already. I was a bit surprised to see that the following entries were made:

This looks as though the default install is set to open up absolutely everything to the SageTV service. Am I reading that right? If so, is that intentional?

That is what my SageTV v7 install did.

[videolog]

Just a quick question. Sorry if this has been asked already but I didn't see it. If I install this over my v7 do I need to enter the license or is that only for a new install using the original license? I know before whenever I upgraded there was no need to reenter the license.

[jusjoken]

Originally Posted by Skirge01

@jusjoken: First, thanks so much for taking this part of the OSS project on!

Second, I just did a server install on a brand new Windows 7 Pro (64 bit) OS in a VM, using the beta 003 installer. During install, I entered the EPG license, used the default install location, started the service control, changed the user and password and then stopped. I was about to check which ports needed to be opened and went into Windows Firewall to verify that nothing had been done already. I was a bit surprised to see that the following entries were made:

This looks as though the default install is set to open up absolutely everything to the SageTV service. Am I reading that right? If so, is that intentional?

Correct. That was intentional and mimics v7.

[jusjoken]

Originally Posted by videolog

Just a quick question. Sorry if this has been asked already but I didn't see it. If I install this over my v7 do I need to enter the license or is that only for a new install using the original license? I know before whenever I upgraded there was no need to reenter the license.

Yes you need to enter your license as v9 stores it differently. If you have already done a previous v9 install, even manually, then the key will show in the text box in the installer.

k

[videolog]

Okay, Thanks. Now I just have to find my license. lol Seems like I've been running Sage forever.

[phantomii]

Posting this as something I learned regarding Version 9 which I installed with the 003 installer. May be true for other versions as well. Also, confirmed this issue existed on two separate systems. I had historically increased the Java Heap to 500 or 600 hex on systems I had installed. I found with version 9 if I increase this above 400 SageTV has issues with capture (throws back errors) and it will exit the application if you click the back arrow in the top left corner of the screen after navigating the menus. Not sure It shouldever be set above 400 but I had done so in the past and never had issues with Version 7. Just an FYI......

[jusjoken]

Originally Posted by phantomii

Posting this as something I learned regarding Version 9 which I installed with the 003 installer. May be true for other versions as well. Also, confirmed this issue existed on two separate systems. I had historically increased the Java Heap to 500 or 600 hex on systems I had installed. I found with version 9 if I increase this above 400 SageTV has issues with capture (throws back errors) and it will exit the application if you click the back arrow in the top left corner of the screen after navigating the menus. Not sure It shouldever be set above 400 but I had done so in the past and never had issues with Version 7. Just an FYI......

I have never been able to get a stable system above 400 with v7 as many others have also reported over the years so i think you were just lucky or something else was different that was allowing it to not fail in the past.

k

[Skirge01]

Just did an install of the client and it seems to have gone off quite nicely. I'll have to do some testing, but initial results are quite promising. One thing I didn't verify before the upgrade from v7 was any registry settings I had customized in order to ensure they stayed afterwards. There's a chance the demuxer's numbuffers setting may have been reset back to 64, but I'm not certain that I had a different number in there. I use Andy's utility to make these changes, so I'm not sure where the registry setting would be. Other settings seem to still be identical to what I remember them being before the v9 upgrade.

This isn't related to your installer, but I did notice that quite a few imported episodes (or entire shows) didn't retain the edits I had made to them in BMT under v7 and will need to be edited a second time so they import properly.

UPDATE: Regarding the import "issue", I forgot to copy my MediaTitles.xml file over to the new server. This didn't resolve all the importing issues, but it did fix the majority of them.

[Ghildebr]

I did the upgrade to my server over the weekend and received the attached error message while upgrading the server. So far everything seems to be working correctly and I see no side effects of the error.

[jusjoken]

Originally Posted by Ghildebr

I did the upgrade to my server over the weekend and received the attached error message while upgrading the server. So far everything seems to be working correctly and I see no side effects of the error.

Were you using the newest installer? Was it on top of v7? Any chance the server or service was still running?

Can you also advise what OS version you were using.

thanks
k

[Ghildebr]

I was using the beta 3 installer, and yes this was an upgrade of version 7 with the sagetv service stopped. The one thing that may make my situation unique is that my server resides on a HP Proliant ML350 running Server 2012 R2 with multiple tuners. As I said, as far as I can tell everything is working correctly. I used the server virtually all day yesterday watching the Super Bowl and never had a glitch. I believe it actually recorded a couple of episodes while I was watching live TV. I did go back and spot check one of those episodes and it did record. I did initially go back and attempt to re-register the .dll but I received an error message stating something about unable to register due to dependencies. I can get you the exact error tonight if you need it.