Closed GoogleCodeExporter closed 9 years ago
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
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:
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
Original issue reported on code.google.com by
bobbyd...@live.com
on 16 Jan 2013 at 4:48Attachments: