Sql error on start

[Steve Barnes]

Just updated to 3.3.8 on the client and I get this error on NPVR start.
Sql error.
Recordings show up and play but no epg and the error popup reappears every time I try to do anything.
I am a bit reticent to upgrade the server side in case I get more problems. I don't have sqlite installed as far as I know on either machine, do I need to install that? and if so on which machine.
I am posting the logs but they mention nothing that seems odd to me.

[sub]

It looks like your database didn't get updated, or you've restored your old database on 3.3.8 after upgrading.

Try running "nextpvr.exe -updatedb"

[Steve Barnes]

I tried uninstall and rolled back to 3.2.9 and the problem remained. Then tried uninstall, delete folder npvr in prog files and user public, then install 3.3.8, same problem.
Then uninstall, delete folder npvr in prog files and user public, then install 3.2.9. No problem, all good.
As I am only working on the client side this is really quick, about 5 mins per uninstall/install and setup.
If the info I just gave can help you suss out the problem then I will give it a go. If you like I could do a clean re-install of 3.3.8 and see what the logs say.
When I rolled back to 3.2.9 without deleting those folders I got, not only the sql error but also a .Net popup which just wouldn't go away until I force the Npvr services to halt in task manager.
Seems strange that a clean roll-back solved the problem, I guess there must be something in the new code for 3.3.8 that messes with .net.

[Steve Barnes]

Just went to watch the news and it hadn't recorded. Whats worse is that all but 2 of the pending recordings had disappeared. Seems epg had not updated but on checking I
discovered that it had but the database on the server had dropped them all. An update from the epg xml file corrected this.
Got me flummoxed I can tell you. Could these errors be connected? the timing looks the same.

[Lao Pan]

The Client & Server must be on the same version - databases are not compatible between version usually.

[sub]

Yep, you need to update both. Client and Server both need to be running 3.3.8

[Steve Barnes]

Ah ha. Wish I had known that earlier. I guess we now all know why. :-)
Thanks guys.
So, would that have caused the problem at the server end?.

[sub]

It certainly could have caused unexpected problems, like things not being able to be saved or loaded from the database.

[Steve Barnes]

Cheers. May I take this opportunity to thank you again for all the hard yards you have put in over the years so we can all sit on the couch and watch TV. ;-)
Have now updated both client and server, Mothership and baby are doing fine.

[brettlg]

It looks like your database didn't get updated, or you've restored your old database on 3.3.8 after upgrading.

Try running "nextpvr.exe -updatedb"

Can you please give more details on how to use the command line to do this? I am trying but it is not recognizing it.