I think the only way you can run into that error is when you refreshed the kmttg Now Playing List table the subsequent RPC call failed. So refresh the NPL again and play close attention to the 2nd part (the "Remote" job) that immediately follows. If that is failing then that would explain it.

(There's 2 jobs: 1st one is normal way of getting NPL XML from TiVo http server, 2nd call is the RPC to obtain corresponding id's which allows kmttg needs to delete).

I think the only way you can run into that error is when you refreshed the kmttg Now Playing List table the subsequent RPC call failed. So refresh the NPL again and play close attention to the 2nd part (the "Remote" job) that immediately follows. If that is failing then that would explain it.

(There's 2 jobs: 1st one is normal way of getting NPL XML from TiVo http server, 2nd call is the RPC to obtain corresponding id's which allows kmttg needs to delete).

All RPC calls to my Premier, including from kmttg, are suddenly failing. The SSL handshake is croaking. Both kmttg and orangeboy's YATR TiVo Remote Control suddenly started failing a couple of days ago. They were working fine until then. I've tried the utilities from a couple of different workstations, but they both fail from both machines. Everything but the RPC calls seems to be working.

All RPC calls to my Premier, including from kmttg, are suddenly failing. The SSL handshake is croaking. Both kmttg and orangeboy's YATR TiVo Remote Control suddenly started failing a couple of days ago. They were working fine until then. I've tried the utilities from a couple of different workstations, but they both fail from both machines. Everything but the RPC calls seems to be working.

'Anyone have any ideas for further troubleshooting?

Click to expand...

You are using the cable company Premiere, not the consumer version right? What's the software version? If you are not running kmttg v0p8r or later then you should update and that may solve the problem as TiVo tightened authentication in the consumer software in the last update, and maybe the cable company is playing catch up with their software.

I think the only way you can run into that error is when you refreshed the kmttg Now Playing List table the subsequent RPC call failed. So refresh the NPL again and play close attention to the 2nd part (the "Remote" job) that immediately follows. If that is failing then that would explain it.

(There's 2 jobs: 1st one is normal way of getting NPL XML from TiVo http server, 2nd call is the RPC to obtain corresponding id's which allows kmttg needs to delete).

then you should update and that may solve the problem as TiVo tightened authentication in the consumer software in the last update, and maybe the cable company is playing catch up with their software.

Click to expand...

It is entirely possible this is related to a software upgrade, of course. Indeed, it is rather likely. I'm hesitant to call TiVo, however, because they are liable to give me the "supported software" brush-off.

Well, I'm using orangeboy's software, not Yoav's. It's quite possible they use the same approach, of course. Orangeboy doesn't credit Yoav, which he should have done if it is derivative of his work.

I've been thinking of modifying orangeboy's code to work with the telnet interface as well as the RPC inerface, so it can be used with S3 TiVos. That may move up in priority, now, but I would rather still use the RPC interface for the Premier, as it does have a few features not in the telnet interface.

Could well be there's consumer software update coming that breaks things there as well. Seems like TiVo is obsessively protective of the RPC interface which suggests perhaps there are even bigger and better things that can be done with it that haven't yet been discovered...

Ah. At first glance that would suggest the leased box software is lagging the purchased box software, but the fact kmttg has also stopped working suggests the opposite, assuming this is related to a softwre release, at all.