Plugin Failing to install / OTA only

[GoogleCodeExporter]

What steps will reproduce the problem?
1. I'm finally getting back to working with the latest plugins (no time during 
the holidays). I uninstalled whatever version I had from last year by removing 
the sources and upgrading the plugin. I got as far as entering the zipcode for 
the first new source and it failed to connect to the server. This is an exact 
repeat of the symptoms from earlier on (if that helps) where sage says it 
cannot connect to the sage server and you cannot go any further to install the 
source. I'm attaching log files. It's been so long since I've posted an issue I 
hope I'm supplying all the correct info.
.
2.
3.

What is the expected output? What do you see instead?

What version of the product are you using? On what operating system?
.
Win7, SageTV latest. Plugin 19.1 (I beleive).

Please provide any additional information below.
One note: I did recently use this install to connect to a sage server as a 
client. But not when removing/installing the plugin.

Original issue reported on code.google.com by bobbyd...@live.com on 16 Jan 2013 at 4:48

Attachments:

• sagetv_3.txt
• sd4j-api.log
• sdepg.log

[GoogleCodeExporter]

There are two things here:

First, it appears you may not have removed the old sd4j-api plugin?  Please 
check your SageTV\JARs\ folder.  If you have an sd4j-api.jar and sdjson-api.jar 
then you must remove the sd4j-api.jar by going to your list of installed 
plugins in Sage, viewing Libraries and uninstalling sd4j-api plugin.  If both 
of those jars exist then you'll end up with class conflicts on the classpath, 
which definitely seems to be happening based on the log output I'm seeing.

Second, the SD web service is in a transitional state at the moment.  Beta 19.1 
(and any older ones) can no longer talk with SD (as of Sunday night).  Beta 20 
will be the next beta that can talk with SD again.  I hope to have that ready 
by the end of the weekend or early next week.  However, your logs aren't 
showing the expected errors you should be getting, but this is due to the jar 
conflict, I believe.  So cleanup the jar conflict and then try again.  The 
error I'm expecting you to see is something along the lines of:

"API version error: 20121231 received; 20130107 expected"

I don't think that's the exact wording, but it's close.  Once you get to that 
error then everything is fine and will start to work again once beta 20 is 
ready.

If you're not able to get to that error message then repost your latest logs 
and we'll see where you are at.

Original comment by de...@battams.ca on 16 Jan 2013 at 12:47

• Changed state: Reviewed
• Added labels: Type-Support, Plugin-sdepg
• Removed labels: Type-Defect

[GoogleCodeExporter]

Thanks Slugger! The sd4j-api.jar was indeed there. While uninstalling from the 
library I found a few other dependancies outdated... Namely args4j, 
commons-compress and groovy. So those are now up to date and sd4j-api has been 
removed. The latest log file does have the error.."Wrong API version. Expected 
20130107, received 20121231". Attaching the new sdepg.log. See you at Beta 20!

Original comment by bobbyd...@live.com on 16 Jan 2013 at 4:36

Attachments:

• sdepg.log

[GoogleCodeExporter]

Looks good.  You should be good to go when beta 20 is ready.  Open a new ticket 
if that's not the case.

Original comment by de...@battams.ca on 16 Jan 2013 at 6:10

• Changed state: Verified