Sage Client open source upgrade from trial

[jughead]

Hi, I have a licensed Sage 7 machine that I'm turning into a server now that the open source thing is happening. On a second PC, I've installed the trial version of Client v7. It's working well but is obviously going to expire soon.

Is upgrading to v9 from the v7 trial of Client as easy as copying the two jar files as seen here?

Do I also have to copy the jar's to the server machine or will v9 Client work fine with a v7 Server?

Will it nag me for a license that I have to ESC past or something, or does replacing the jar's fix that?

Thanks in advance! I've wanted to have a server/client setup for years but never had a Client license. Exciting

Thanks!

[tmiranda]

Originally Posted by jughead

Hi, I have a licensed Sage 7 machine that I'm turning into a server now that the open source thing is happening. On a second PC, I've installed the trial version of Client v7. It's working well but is obviously going to expire soon.

Is upgrading to v9 from the v7 trial of Client as easy as copying the two jar files as seen here?

Do I also have to copy the jar's to the server machine or will v9 Client work fine with a v7 Server?

Will it nag me for a license that I have to ESC past or something, or does replacing the jar's fix that?

Thanks in advance! I've wanted to have a server/client setup for years but never had a Client license. Exciting

Thanks!

You must put the new Jar files on the server and the client or the client will not connect. If you are running Windows the .exe will prevent you from running Sage when the trial expires until we get a new Windows sage.exe compiled.

[jughead]

Aww, damn. I am running windows so I guess I jumped the gun shifting my stuff around and installing the Client trial. Thanks for the answer and I guess I'll just have to wait for the people who know how to do those things to do them!

Thanks!

[Fuzzy]

In the mean time, you should be able to use the windows Placeshifter as your client, as it's licensing is handled server side, which would be skipped in the v9 server.

[jughead]

I hadn't thought about that but after reading up on placeshifter I think I'll stick with Plex once the trial expires and just wait for the exe. I'm glad there is an alternative solution though if Plex doesn't cut it.

Thanks!

[jughead]

The exe file in THIS post, along with changing the 2 jar files on both PC's seems to be working Client launches with no complaining about registration.

Thanks everyone for the hard work!

[Damstas]

Originally Posted by jughead

The exe file in THIS post, along with changing the 2 jar files on both PC's seems to be working Client launches with no complaining about registration.

Thanks everyone for the hard work!

I did that too, but neither of the Schedules Direct plugins seems to be compatible. :/

[jughead]

I'm noticing a few issues now too. I just noticed that my favorites are all missing. My Gemstone menus seem to have gone back to default on the server as well.

I had to rename lucene-core-3.0.1.jar in addition to copying the new lucene jar file to the jar folder on the server or it wouldn't launch. In both the client and the server, there was an error that complains of the missing lucene-core-3.0.1.jar file. Are both the new and old lucene jar files supposed to be in the jar folder? If so, any ideas why my server won't launch with both in there??

Thanks again!

edit- attached error i get if both lucene jar files are in the jar folder on the server when launching

[Fuzzy]

If this is on an existing install, you should remove the lucene plugin, as the new phoenix core doesn't require it anymore. Then make sure the new lucene file is there, as SageTV 9 uses it.

[jughead]

Originally Posted by Fuzzy

If this is on an existing install, you should remove the lucene plugin, as the new phoenix core doesn't require it anymore. Then make sure the new lucene file is there, as SageTV 9 uses it.

Thanks Fuzzy,

yep, it's an old install. i'll be redoing it one of these days. i uninstalled the plugin and that resolved everything but my missing favorites. i'm checking the forum now to see if that is a known issue with the upgrade. if it's not, any ideas how to get them back? i opened wiz.bin in notepad and it appears that they are still in there, though garbled looking, of course.

Thanks!

[Fuzzy]

On first run, the wiz.bin needs to be upgraded. If you had an issue of sage crashing out when it is run, it likely started the upgrade, then crashed out, wiping out the wiz.bin (which is where the favorites are).

[jughead]

Originally Posted by Fuzzy

On first run, the wiz.bin needs to be upgraded. If you had an issue of sage crashing out when it is run, it likely started the upgrade, then crashed out, wiping out the wiz.bin (which is where the favorites are).

damn, that's not good news. even when i replace the wiz.bin with a backup from last year it says there are no favorites created. i'm hoping that one isn't empty because it's much smaller, about 5.7 MB but it's the most recent backup i can find :/

[wnjj]

Originally Posted by jughead

damn, that's not good news. even when i replace the wiz.bin with a backup from last year it says there are no favorites created. i'm hoping that one isn't empty because it's much smaller, about 5.7 MB but it's the most recent backup i can find :/

If you want to see if they are in the DB, add this to sage.properties before you start it up:

dump_db_on_startup=true

Then check the Sage dir for a wiz.dump file. Inside that file, grep for "LikeTitleTrend". Those lines are your favorites.

[jughead]

Originally Posted by wnjj

If you want to see if they are in the DB, add this to sage.properties before you start it up:

dump_db_on_startup=true

Then check the Sage dir for a wiz.dump file. Inside that file, grep for "LikeTitleTrend". Those lines are your favorites.

thanks, i'll try that tonight!

[jughead]

i got my favorites back

sage had made a "backup" called wiz.bin.corrupt0 that worked fine and restored my favorites when i named it back to wiz.bin. it must have not converted properly on runonce, due to crashing because of the old jar file in there along with the new one like Fuzzy said. Whew.

thanks wnjj, that tip was helpful and now i have a backup of my favorites in plain text

i think i'm all good now! thanks all!!