yapi2xml epg not updating

[insshc]

Hi, I'm using yapi2xml and it worked great for a couple weeks. However, the last couple days all the show infos are blank, displaying "No Show Details" on the tv guide. I've tried to manually update through the System menu option in pvrx2, and I tried doing update in the Capture Sources tab in config.

The only thing that's really changed I think is I changed a couple things like making some services "manual" instead of "automatic", namely SQL server services, trying to fix a problem where my computer just hangs for a half minute every 30-60 minutes (unsuccessfully)... but I restarted those services and retried the EPG updates and they still didn't go through.

Here's config and config-native logs from when I did the config update. Notably, there's one error line:

2008-09-24 20:02:08.044 ERROR [4] Failure in ChannelFactory::LoadCompleteGenreList(): The database file is locked
database is locked

Thanks!

[sub]

Reboot. After that if you can reproduce it and repost the logs, then I'll take a look.

[insshc]

oops here is the zip with the configs

[insshc]

okay just rebooted couple times, trying to update it before/after each reboot... same problem, log file looks the exact same as posted above. Would other log files be helpful?

[sub]

I would appreciate seeing a log after a reboot.

[insshc]

here they are

thanks!

[sub]

You might need to set <LogSQL>true</LogSQL> in config.xml, then reboot and try again, then zip and attach a complete set of logs.

[insshc]

okay, here's the new config log

I see an error line now

2008-09-24 22:49:48.009 ERROR [5] Unexpected error informing recording service that EPG has updated: System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:7968

This made me remember that I did upgrade my router firmware... this may be causing it?

[sub]

You didnt enable the SQL logging I mentioned above, so you'll need to redo it.

The error you mention above is typically because either the recording service isnt running or you have some firewall software getting in the way of communication.

[insshc]

weird, sorry about that. Here's the new log