DVArchive wont update TV listings?

[Chip718]

Hi. Ever since Sept. 31 DVArchive V3.1 wont let me update my TV listing. Every time I try I get "Error while updating TV Listings -- 95." I tried registering for the DVArchive forum to ask tgere, but I never received the conformation e-mail from the sites admin.

Can anyone give me some advice? Thanks in advance.

[Crunchy Doodle]

I suggest completely removing DVArchive 3.1 from your system. Be sure to delete all of the files it uses for a database. Then install DVArchive 3.2. That's likely to cure your problem.

Though others will argue to the contrary, JAVA based applications are very fragile and easily corrupted. With DVA, I've found that completely removing it and starting over works for all the times it's chocked on me.

Bye. :cool:

PS. DVA is one of the coolest apps I've ever used.

Hi. Ever since Sept. 31 DVArchive V3.1 wont let me update my TV listing. Every time I try I get "Error while updating TV Listings -- 95." I tried registering for the DVArchive forum to ask tgere, but I never received the conformation e-mail from the sites admin.

Can anyone give me some advice? Thanks in advance.

[Clay Schneider]

That happened to me when the cable provider lineup changed. I don't remember if it was because the replay itself was wanting me to select an updated provider listing, or if it was because I had a channel set up in dvarchive that wasn't there anymore. I do know that I was able to get everything working again without removing dvarchive or the xml control files.

Given that you were hit right at the end of a month, it wouldn't surprise me if there was a provider change.

[Chip718]

Thanks for the replies. I tried removing the program through Add/Remove and re-installing it, but when I went into it all my info was there? I assume I didn't remove all the files on the uninstall. Does anyone what I could have missed? Thanks.

[gduprey]

Actually, at least for DVA, it really is not fragile at all -- at least not because of anything related to Java (though Java itself can get wanged on the head by things like incompatibe video card drivers and such).

The problem you are seeing is related to a bug in DVA 3.1 that was fixed in 3.2. I recommend you download 3.2. While DVA is not running, you want to locate and delete DVA_TV.xml as it's likely corrupted in some way (something else that was substantially addressed in 3.2).

There is absolutely no need to uninstall DVA and reinstall it. Unless you had a bad spot on your hard disk, doing so does nothing at all. Unlike Windows program that stick their fingers in your system all over the place (and consequently can get a finger or two chopped off periodically by other apps), DVA is all contained in a single file that is never modified or changed.

Just download the latest Java update, if you aren't already running it (that is just a "good idea", nothing particular to DVA) and DVA 3.2. Install 3.2 right over your existing 3.1 install (DVA should not be running when you do it), delete the above mentioned file and start DVA. Then do a TV listings update via pressing the button on the TV Listings tab.

Finally, the reason your data stuck around between installs is that the actual config files are not stored in the installation directory, but in your home directory. This prevents "bad" things from happening if you do updates or move things around later on.

Gerry

[Chip718]

Your awesome, Gerry. Thanks a ton. It is working great now. I wasn't aware there was a newer version of DVA out. I thought 3.1 was the newest. I just have 1 more question. On the TV listing I used to see my shows that are scheduled to record, but I don't no more. Will the program fix that by itself?

Thanks again for all your help. -Chris

[gduprey]

Howdy,

For some reasons, occasionally the Upcoming Show system won't kick over until it sees a change on one of the ReplayTV units. So if this is happening to you, deleting or chaning a show (or your ReplayTV having recorded a new show) on each unit will "free" it.

I'm hoping to have a fix in the not too distant future.

Gerry

[Chip718]

Thanks again, and keep up the good work. This is an awesome program.

[DarkScreen]

Howdy,

For some reasons, occasionally the Upcoming Show system won't kick over until it sees a change on one of the ReplayTV units. So if this is happening to you, deleting or chaning a show (or your ReplayTV having recorded a new show) on each unit will "free" it.

I'm hoping to have a fix in the not too distant future.

Gerry

Hello Gerry,

I just upgraded from DVArchive 3.1 to 3.2 and have the same problem: Doing an "Update Listings..." causes the scheduled recording icons go away (I'm using 3 ReplayTV units and Java 1.4.2_11). If I close and restart DVArchive (or wait long enough), the recording icons do come back. Is there a fix for this yet?

BTW, I LOVE DVArchive. Even though I've been trying to fully migrate to SageTV for the last year and a half, I still find I'm often using VLC thru DVArchive to watch old or back-up ReplayTV recordings that "didn't quite make it to" my SageTV server.

[Ace987]

If I close and restart DVArchive (or wait long enough), the recording icons do come back. Is there a fix for this yet? I have to ask. How long is long enough? Every time I update the listings, the red dots disappear for a minute or two after it finished updating. I always thought it was normal, but maybe it's just something in which I've become accustomed.

[YBDBDOO]

On my buggy but marginally usable network it takes about 5-8 seconds to collect data from 6 rtv units and show the red dots. A minute or two sounds like network trouble to me...

One of my dva servers has about 2400 shows and its gui goes away for 5-10 seconds about every 30 seconds when I am doing manual edits of the show descriptions. No delays on my other dva servers with less than 500 shows each.

Don't know if that helps, but hope it does.

[DarkScreen]

I have to ask. How long is long enough? Every time I update the listings, the red dots disappear for a minute or two after it finished updating. I always thought it was normal, but maybe it's just something in which I've become accustomed.

As I think Gerry implies in message #7, doing an update freezes the updating of both the recording dots in the "TV Listings" and the adding of new shows in the "Upcoming Shows" tab until some new event takes place (like a new or deleted recording). This seems like a bug in 3.2 (or maybe some new compatibility issue with my two PCs).

When I say freezes, I mean that in version 3.1, the recording dots showed up within a few seconds of finishing a listings update. With version 3.2, tens of minutes or more go by with nary a dot to be seen.

And to YBDBDOO, Nothing's changed in the network. Everything else seems to work as before. And an observation: With 6 units, I'm surprised that you don't use unique dot colors for each Replay using the DVR properties settings in DVArchive. Even with my 3 Replays, I find this a very useful feature.

[gduprey]

It is a problem in 3.2. It's very much related to hearing activity from each ReplayTV and in particular, the analyzer sends a request for guide updates and waits to hear an update from each ReplayTV before it does it's work. While I've not had a chance to dig into it yet, what I think happens for some folks is that a fetch of the ReplayTV guide produces a "no change" report and that doesn't trigger an event the analyzer is waiting for.

There is no explicit time delay -- it's really tied to when whatever pending ReplayTV finally has a change in it's guide to report (show deleted, new recording added, new show recorded, etc).

So in general, the "busier" the ReplayTVs are, the less likely you'll see this.

It's on my list to look into, but frankly, I haven't had much time lately.

Gerry

[DarkScreen]

It is a problem in 3.2. It's very much related to hearing activity from each ReplayTV and in particular, the analyzer sends a request for guide updates and waits to hear an update from each ReplayTV before it does it's work. While I've not had a chance to dig into it yet, what I think happens for some folks is that a fetch of the ReplayTV guide produces a "no change" report and that doesn't trigger an event the analyzer is waiting for.

There is no explicit time delay -- it's really tied to when whatever pending ReplayTV finally has a change in it's guide to report (show deleted, new recording added, new show recorded, etc).

So in general, the "busier" the ReplayTVs are, the less likely you'll see this.

It's on my list to look into, but frankly, I haven't had much time lately.

Gerry

Thanks for the detailed explanation. This certainly matches my observations. Since I'm still using Java 1.4, I guess I could revert back to 3.1.