Search the Community
Showing results for tags 'databases'.
Found 1 result
First, thanks for some good products which I have used since 2011. I have just upgraded to - Mediaserver 18.104.22.168 - DVBViewer 22.214.171.124 ... and ... an old problem came back. My list of recordings in the Web inteface now only includes 114 of 145 recordings. What has happened so far moved recording folder to a new NAS (using a UNC-path for access) Upgraded DVBViewer and Media Server Moved a few recordings from the PC to the NAS (the wrong location was caused by Media Server installation which did modify the windows service login info) Then I noticed that the list of recordings in the Web-Interface was mising some recordings. I have reported this problem in 2014 see http://www.DVBViewer.tv/forum/topic/55334-workaround-fixing-incomplete-recordinglist-in-webinterface/?tab=comments#comment-414931 What is NOT working Update Database (and also with variation of Clean Up Database and Clear Recording History) Stop server, delete SvcDatabase.db3 and restart server Trying 2. did in fact loose another 6 recordings What is working Rename the .ts, .log and .txt file followed by an "Update Database". I just add an "xxx" in front of the file extension. This works exactly as reported in 2014 and the only difference seen from the Media Server is the changed filenames. My conclusion is the same as in 2014 that the filename is cached somewhere preventing correct detection. A workaround I can easily send a script through and rename all the files - but would rather learn what is wrong, so I will wait a few days before I do this. Question/Way Forward I could not find any debuging of the "Update Database" task. It would be nice to see why some recordings are rejected. What should I do next? Will a suppot ZIP include debug info from "Update Database"?