2.1.4 Is -UpdateEPGOnly working from command line?

[sub]

Might be getting confused here. We tend to use N-PVR for watching recorded Freeview TV (Terrestrial).
All I've done in the past is copy anything not yet watched into the Video folder and watch from there while any new recordings go to the Recording directory.

My problem is that the 'TV Guide' screen shows a matrix of 'no show details'.

Your problem is occurring because there is a field missing in your database.

2011-07-06 17:24:40.993 [ERROR][5] Unexpected error saving listing: System.Data.SQLite.SQLiteException: SQLite error
table EPG_EVENT has no column named dvb_service_event_id

Either of my suggestions from above should fix it, then you'll be good to go.

[Buster]

This is true. Your second suggestion worked for me. Thanks.

[skinny]

A set of log files is attached after running through the procedure describe below
When UpdateEPGOnly is run from the command line, it only seems to take effect after NPVR is restarted.


Fresh start of NPVR
Empty EPG from Settings Menu
Check TV Guide is empty
Run NPVR.exe -UpdateEPGOnly from command prompt
No change seen in TV Guide
Exit NPVR
NPVR1.log

Restart NPVR, immediately check TV Guide and it is populated
Empty EPG from Settings Menu
Check TV Guide is empty
Exit NPVR
NPVR2.log

Restart NPVR, TV Guide is still empty
Exit NPVR
NPVR3.log

Run NPVR.exe -UpdateEPGOnly from command prompt
Wait 30 sec
Restart NPVR, the TV Guide is populated
NPVR4.log

Empty EPG from Settings Menu
Check TV Guide is empty
Exit NPVR
NPVR5.log

Run NPVR.exe -UpdateEPG from command prompt
NPVR restarts after 10 seconds and TV Guide is populated
NPVR6.log

[skinny]

Unable to resolve the above issue I have started to use UpdateEPG.bat and PostUpdateEPG.bat for the first time.
UpdateEPG.bat runs as expected and the TV Guide is updated but there was an issue with PostUpdateEPG.bat

From the NRecord.log
2011-07-19 02:01:28.569 [DEBUG][8] About to run C:\Users\Public\NPVR\Scripts\PostUpdateEPG.bat
2011-07-19 02:01:33.580 [DEBUG][8] C:\Users\Public\NPVR\Scripts\PostUpdateEPG.bat has completed

The problem was that the script in PostUpdateEPG.bat did not run. The script is a backup routine, if there is nothing to backup it takes about 2 minutes to execute (not 5 seconds) It did run as expected when I executed PostUpdateEPG.bat manually.

PostUpdateEPG.bat contained these commands

CD \
CD C:\Program Files\unison
....

Changing to this format seems to have fixed the problem

CD \
CD "Program Files\unison"
....

Question: is there a resource that helps to write scripts in a format that NPVR can handle?

Cheers
Paul

[johnsonx42]

the "scripts" are just windows batch files (which are generally equivalent to DOS batch files). they have nothing to do with NPVR, other than the fact that NPVR asks Windows to run them for you. you can find all sorts of info on the internet for batch file commands.

I promise your PostUpdateEPG.bat did not work properly when you ran it manually without the double-quotes in the CD command (necessitated by the space in "program files"). it may have appeared to work, but that would have been strictly by accident.

[skinny]

I promise your PostUpdateEPG.bat did not work properly when you ran it manually without the double-quotes in the CD command (necessitated by the space in "program files"). it may have appeared to work, but that would have been strictly by accident.

I promise you it did work, on more than one occasion, calling it from a command console as well as from an explorer window

[johnsonx42]

genuinely bizarre, as the double-quotes are absolutely required.

edit: I am actually incorrect here, at least on Windows 7 'cd' doesn't require the double-quotes

[sub]

NPVR doesnt take any part in processing the contents of these batch files. It just askes Window's to run it, and Windows takes care of the rest.

We've never found a case of it not running being attributed to some NPVR problem. It always ends up being one of two things:
1) script making assumptions about the current working directory or drive. You should explicitly change drive (in multi-drive setups), and explicitly directory to where you want the commands to run from.
2) script running commands that dont work across desktop sessions. The recording service runs as LocalSystem, so isnt able to use WM_COPYDATA etc to pass data to other applications. (ie, no shared clipboard, which some utilities use for passing data around).

From memory, "CD" is a special case and doesnt require quotes around parameters with spaces.

[johnsonx42]

From memory, "CD" is a special case and doesnt require quotes around parameters with spaces.

yeah, you're right, at least on Windows 7 it does work without the double-quotes (I'm sure this has not always been the case). in that case I have no idea why adding them appeared to fix skinny's problem.

[skinny]

Thanks johnsonx42 & Sub
for future I'll stick with more traditional command line syntax, just in case.
Cheers