Open Source Windows Installer

[tmiranda]

Originally Posted by tmiranda

I installed the latest build over a V7 install that was upgraded to V9 by copying the Sage 9 jar file. The upgrade went smooth and everything is working.

Thanks for doing this.

I did notice that I had to reenter my license key. I had the key stored in the environment variable as a local variable. The installer never asked me for a key but the new version of Sage didn't find it. Making the key a global environment variable fixed the issue.

Maybe the installer should check for thins condition?

[Tiki]

Originally Posted by tmiranda

I did notice that I had to reenter my license key. I had the key stored in the environment variable as a local variable. The installer never asked me for a key but the new version of Sage didn't find it. Making the key a global environment variable fixed the issue.

Maybe the installer should check for thins condition?

I think he said that starting with the latest version of the installer and going forward, the installer would not deal with license keys at all. This is because when they integrated Schedules Direct into the core, they also made changes to prompt for a key when you configure your lineup.

[jusjoken]

Originally Posted by Tiki

I think he said that starting with the latest version of the installer and going forward, the installer would not deal with license keys at all. This is because when they integrated Schedules Direct into the core, they also made changes to prompt for a key when you configure your lineup.

Now that the core is using activkey file on both linux and windows I think the use of the environment variable should be phased out. It's always hard to remove older ways of doing things but at least the core does check for the system environment variable and I believe if found it will then write the activkey file.

Perhaps a change to the core to check both local and system environment variables should be made but not sure it is worth it for existing users. Existing users can just create/copy the activkey file into the SageTV folder after install. New users will all just get prompted during config in the UI.

k

[tmiranda]

Originally Posted by jusjoken

Now that the core is using activkey file on both linux and windows I think the use of the environment variable should be phased out. It's always hard to remove older ways of doing things but at least the core does check for the system environment variable and I believe if found it will then write the activkey file.

Perhaps a change to the core to check both local and system environment variables should be made but not sure it is worth it for existing users. Existing users can just create/copy the activkey file into the SageTV folder after install. New users will all just get prompted during config in the UI.

k

Ah, I didn't realize using the activkey file was the way to go.

I'm not sure the new core actually creates the file if it finds the env variable. I searched my system and there is no activkey file yet the EPG updates are working.

[EnterNoEscape]

Originally Posted by Tiki

I think he said that starting with the latest version of the installer and going forward, the installer would not deal with license keys at all. This is because when they integrated Schedules Direct into the core, they also made changes to prompt for a key when you configure your lineup.

I don't want these changes to be confused with each other. Narflex improved the key entering situation and error messages with WarlockRipper before the Schedules Direct changes were put in place.

[EnterNoEscape]

Originally Posted by tmiranda

Ah, I didn't realize using the activkey file was the way to go.

I'm not sure the new core actually creates the file if it finds the env variable. I searched my system and there is no activkey file yet the EPG updates are working.

It's checking the environment variable after it determines the activkey file doesn't exist.

[Tiki]

Originally Posted by EnterNoEscape

It's checking the environment variable after it determines the activkey file doesn't exist.

But, sounds like maybe it only checks for global and not local env variables

[EnterNoEscape]

Originally Posted by Tiki

But, sounds like maybe it only checks for global and not local env variables

If you are referring to system variables, that is correct.

[CptKirk]

.

[tmiranda]

I noticed something else which I suspect was caused by the installer but can't confirm. I was running Sage as a service under a specific user. Recently I noticed the service was running under LocalSystem. I didn't (knowingly) change this. C Is it possible that the installer changed it to LocalSystem?

[UgaData]

Originally Posted by tmiranda

I noticed something else which I suspect was caused by the installer but can't confirm. I was running Sage as a service under a specific user. Recently I noticed the service was running under LocalSystem. I didn't (knowingly) change this. C Is it possible that the installer changed it to LocalSystem?

I have run into this as well. After each upgrade I now check the service to verify the account it is using. Each time it is using the default. However, it does seem to remember the user account I want to use (when I click on "Change User" the correct user is shown), it just reverts to using the default after each upgrade.

[Tiki]

Originally Posted by UgaData

I have run into this as well. After each upgrade I now check the service to verify the account it is using. Each time it is using the default. However, it does seem to remember the user account I want to use (when I click on "Change User" the correct user is shown), it just reverts to using the default after each upgrade.

I'm pretty sure it has always been that way. I seem to remember having to set this when upgrading to Sage 4, 6, and 7. But, it would be nice if this setting could be retained when upgrading.

[EnterNoEscape]

Originally Posted by Tiki

I'm pretty sure it has always been that way. I seem to remember having to set this when upgrading to Sage 4, 6, and 7. But, it would be nice if this setting could be retained when upgrading.

I believe this behavior can be changed in the installer.
http://stackoverflow.com/questions/2...reinstallation

[Taddeusz]

I'm not finding the answer anywhere but I'm trying to install the client on a clean install of Windows 10 x64 and getting the registration errors. Not seeing any updates for the VC libraries when running Windows Update and none of the fixes on that KB are for Windows 10. Any ideas?

[baudfather]

Big thanks to everyone who's put in the work to get v9 off the ground and put together the Windows installer. I upgraded from v7 and things went fairly well, though I hit the issue with the old lucene JAR file that borked things. Took a bit of work searching the forums to find the solution. For future users, would it be possible to have the installer automate the deletion of this file, or is it just a rare occurrence? If not, it might be worth highlighting this issue for users if they are coming from a previous version.

Other than that, everything went well. Cheers to all, long live Sage!

[jusjoken]

Originally Posted by baudfather

Big thanks to everyone who's put in the work to get v9 off the ground and put together the Windows installer. I upgraded from v7 and things went fairly well, though I hit the issue with the old lucene JAR file that borked things. Took a bit of work searching the forums to find the solution. For future users, would it be possible to have the installer automate the deletion of this file, or is it just a rare occurrence? If not, it might be worth highlighting this issue for users if they are coming from a previous version.

Other than that, everything went well. Cheers to all, long live Sage!

I added a note to the installer thread.

[sflamm]

I thought the latest installer fixes the old lucene jar problem:

Done.

I created a test on a V7 install that had the older lucene jar and installed the last 9.0.12.506 version and it failed...as expected.

I built a new installer for 9.0.13.536 and that install went smooth and V9 ran fine with the old and new lucene jars in place

I am in the midst of uploading the new Windows Installer versions and will be done later today.

https://forums.sagetv.com/forums/sho...0&postcount=20

Is that not true? Is it still required to remove the old lucene jar?

[jusjoken]

Originally Posted by sflamm

I thought the latest installer fixes the old lucene jar problem:


https://forums.sagetv.com/forums/sho...0&postcount=20

Is that not true? Is it still required to remove the old lucene jar?

I removed that note now as the latest installer no longer has that issue. Thanks for the reminder.

k

[EnterNoEscape]

Originally Posted by sflamm

I thought the latest installer fixes the old lucene jar problem:


https://forums.sagetv.com/forums/sho...0&postcount=20

Is that not true? Is it still required to remove the old lucene jar?

As of 9.0.13, it will now load the correct lucene jar first preventing the issue that required removal of the old lucene jar prior to upgrading. I would still recommend uninstalling the old jar at some point through the plugin system.

[sflamm]

Will the old plugins continue to work for now? (e.g. Phoenix, BMT...)
These continue to use the old Lucene jar?