TEMP_FILE error just on client. Help, please :-)

[bendecker]

Hi --

I've been all over the forums and am having trouble figuring this out. I keep getting a "no such table: TEMP_FILE" error on my client upon startup of the "NPVR Recording Service". The error always pops up as a graphic that cannot be saved to a text file, so I attached a screenshot. Please find my logs attached as well.

1. It only happens on startup on the client. It's when the service starts

2. It happens regardless of firewall setting on both the client and server -- on or off.

3. Everything else seems to work fine -- recording just fine, playing back, schedules, etc.

4. It only shows up on the client -- never on the server.

5. I don't remember exactly when it started happening. It's been months (life got in the way of debugging it...)

6. I tried running nextpvr.exe -updatedb with and without a) replacing the npvr.db3 file and b) replacing my copy of empty.db with a blank one that I found on the forums from Sub. None of this helped.


It's really just an annoyance on the client. Any ideas?

Thanks!

-Ben

P.S. This is my first support post, so my apologies in advance if I have left anything out that is expected or done anything proving my newbie cluelessness .

[sub]

I'm not sure how it would have got like that on the client, unless maybe they're running different versions?

Try running "nextpvr.exe -updatedb" on the client.

[johnsonx42]

you don't need to be running the recording service on the client. it doesn't do anything, just disable it.

if you want to update the database on the client I *think* you need to go into Settings and turn off client mode, then exit NextPVR and run "nextpvr.exe -updatedb". or you could just replace the npvr.db3 with empty.db3. this will let you run the recording service on the client, but doesn't change anything about how the client runs.

[bendecker]

you don't need to be running the recording service on the client. it doesn't do anything, just disable it.

Well, that was easy! I disabled the service on and removed "NextPVR Tray" from the startup folder. Rebooted and no more error message.

Thanks for the help!

-Ben

[bendecker]

I'm not sure how it would have got like that on the client, unless maybe they're running different versions?

Try running "nextpvr.exe -updatedb" on the client.

They are both running the same version and I did try that earlier. Disabling the service seems to have done the trick. I'll keep my eye out for any unexpected side-effects. Thanks!

[johnsonx42]

Well, that was easy! I disabled the service on and removed "NextPVR Tray" from the startup folder. Rebooted and no more error message.

glad you have it working. you can still have the NextPVR Tray icon if you want it, it just looks in the config.xml file to determine where the NPVR server is.

[johnsonx42]

by the way sub, I recall having this error pop up on my client a few times too during testing on 3.0/3.1 but figured it was just cosmetic and didn't report it... it seems to have gone away now though, and the database on my client does appear to be getting updated as I install various 3.2 pre-releases even though I don't use it.