Personal Video Database
English => Support => Topic started by: rick.ca on July 02, 2009, 07:28:01 am
-
I have recently downloaded your new version of personal video database but when I install the program it will not load in my old data base from version 0.9.8.20 which means I have to do the whole database again.Could you please fix this problem :'( :'(
Welcome, moxley.
I'm assuming you didn't intend to post this in Solved Issues (http://www.videodb.info/forum_en/index.php?board=4.0). The support here is good, but not that good. ;)
The current version of the program is designed to convert 0.9.8.20 databases for it's use. Please describe exactly how you are attempting to open the database, and what is happening. If you haven't done so already, make a backup of your database first.
-
The Same Way I always open the database but every time I open version 0.9.8.20 it gives me an error message then tells me it cannot open the database and I have over 700 DVD's In that database and I really do not want to restart doing the whole database again unless it is completely nesescery
-
Just to be clear: You're running version 0.9.9.11. With the File - Open dialog, you select the database file created with version 0.9.8.20. That causes an error message to appear. Does it contain any information beyond the fact it cannot open the database?
-
Post the exact text of the error message, please.
-
I cannot tell you precisely what it reads but the error code is 31 the other stuff is in gobble de gook :'( The other error box reads File is not a valid database Connection Authorisation Failure Error Code 3 :'(. If You want me to I can attach my whole database to the next message and when you have time you can play with it and then tell me your solution as I realy don't want to start again especially with 745 videos to put back in
-
Try running the program with the -portable switch so it will start with a "fresh" configuration file. You can do so by double-clicking on the portable.bat file in the installation directory.
-
Sorry That Didn't Work Either and I am beginning To Think It Would Be Easier Starting Again by installing the old version of pvd on my computer in a different folder and manually copying the database into the new version.I really don't know what is wrong Because when I try to go back to the old version of your program and type in a new movie it tells me there was a problem with the server and then give me a 1.1 404 : error which means the two places I use for my database which is imdb and allmovies are not found and now I am thinking it is a problem with my computer as the new version connects to both with no problems at all and I do not want to stop using your program as it is one of the best I have found on the web even though I Bought another program on the web called Movie Collector I still prefer using your program.
I am using Windows XP Media Edition as my operating system with service pack 3 :'(
Thank you for all your assistance in trying to help me solve this problem :)
-
Sorry That Didn't Work Either
I wasn't expecting it to necessarily work. What happened? Exactly, please.
Also, please confirm my assumption about the circumstances of the first error message: "You're running version 0.9.9.11. With the File - Open dialog, you select the database file created with version 0.9.8.20."
You normally cannot open a database in an older version of the program after opening it (or attempting to do so) in a newer version. If you wish to revert to the older version, use a backup of the database that has only been used in that version. But there's not much point in going back to the old version—it's no longer supported. The plugin errors you're getting are probably the result of them not being updated for recent changes in the websites.
Do you have a backup or copy of the original database?
-
Send me the database and the file pvdconf.ini located in C:\Documents and Settings\%USERNAME%\Application Data\Personal Video Database\ if you want, I'll take look. You are giving too few information and it is very unprecise, so it is very difficult to understand what is happening.
-
I'm having the exactly same problem. This bug is serious and it seems to be widespread. I just installed the new version and tried to open old database file in it.
-
Could you provide more detailed information on the problem??? (answer all Ricks and mine questions precisely?)
Could you send me files I mentioned above?
-
error:
unsuccessful metadata update
STORE RDB$RELATION_FIELDS failed
attempt to store duplicate value (visible to active transactions) in unique index "RDB$INDEX_15"
This operation is not defined for system tables.
Error Code: 31
8 in 10 times it shows like that, the remaining two it loaded the database but without "custom fields" like "media location", thus it seems those data are lost.
-
Did you use one of the betas before?
-
Curious about the "normal" behaviour for the conversion of a prior version database, I tried opening a backup of my old 0.9.8.20 database. I got exactly the same error. Unfortunately, I can't swear this database was not "touched" by the early betas that seemed to cause this problem, and it's the only backup I've retained.
Perhaps someone else can try the same experiment—on a 0.9.8.20 database that predates the introduction of 0.9.9.x (October 20), or where they are otherwise be sure it's never before been opened in 0.9.9.x.
-
I have tried and it converts OK without errors...
-
I have tried and it converts OK without errors...
So how confident are you this particular error message means the database must have been damaged by an attempt to open it in one of the early betas?
I'm wondering what advice we should be offering users who run into this. Something a little more hopeful than, "You should have made a backup!" :-\
-
I did make a backup and saved it on a cd but It still doesn't work and to be quite honest with you I am getting the poos with the whole damned thing.By the way do you have an e-mail address so that I can send you the information your require mainly my database and the ini file for both versions
-
I did make a backup and saved it on a cd
It's starting to look like you may have to hope nostra can repair your database. But it would be very helpful if we could eliminate the possibility this file has ever been opened by any version of 0.9.9. Can you tell from the date stamp on the CD and from your recollection of when you first installed any version of 0.9.9 whether this is the case?
-
The Date On My CD Is 22/06/2009 and yes I have tried every new version you have developed including the betas with exactly the same results which is why I remained with 09.08.20 but now that doesn't work :'(
-
That's not what I asked. Did you use that database in any version of 0.9.9 before writing it to the CD? The date is so recent, it suggests that may very well be the case.
-
No When I Made The CD I Was Still Using My Old Version Of PVD.I have only recently downloaded the newer version
Just In case you cannot help me I have already started to redo the complete database in the new version.
Thank You for all your assistance
-
When I Made The CD I Was Still Using My Old Version Of PVD.
If that's the case, then this is something nostra is going to have to determine the cause of and fix. When he does, you'll be able to open the old database (freshly restored from the CD).
-
So is it possible for you to upload the database somewhere, so I can check it???
-
I have already sent you a copy of my full database to Nostra E-mail address I hope along with the pvd ini file
-
I have already sent you a copy of my full database to Nostra E-mail address I hope along with the pvd ini file
I did not get your email. Please check if you the email was really sent to admin@videodb.info or support@videodb.info
P.S. I can provide you FTP access if needed
-
Unless it contains no images, there's not much chance a 700-movie database is going to be within the attachment size limits of most email servers. He'll need to use FTP.
-
I have just tried the ftp site you sent me in a personal e-mail and I have to tell you and Nostra that it didn't work as it gave me an error 530 every time I log in using the information you gave me but the main reason I am writing this is to tell you not to worry about my database any more as I have decided to redo it in the new version of your program and again I would like to thank you for all your assistance. :)
-
It's up to you whether to provide the file, but it could be helpful in identifying the what the problem is. Other users could be affected as well.
I'll have to let nostra verify the login he gave you, but the FTP site is working fine. Error 530 just means an incorrect login.
-
If it helps I will send the database so that you can find out what went wrong.
Sorry the error I got for the ftp server was 550 Directory Not Found
-
I used 0.9.8.20 version before. Thank God I have one more backup (not opened in the new version), so I am just waiting for some fix/miracle by nostra, so I can open it in new version without problems. :)
-
I am just waiting for some fix/miracle by nostra
Have you sent that backup to nostra so he might determine what the problem is?
-
Have you sent that backup to nostra so he might determine what the problem is?
I will, just say me how can I do it, the file is about 45 MB large.
-
Nostra will send you instructions. Or if he'd rather I did so, he'll send me instructions—I'm not sure how he manages the FTP access.
-
I am also having this issue. I get the same error message:
"ProcVersionChanges ->9009000 -> unsuccessful metadata update
STORE RDB$RELATION_FIELDS failed
attempt to store duplicate value (visible to active transactions) in unique index "RDB$INDEX_15"
This operation is not defined for system tables.
Error Code: 31"
followed by
"failed to open database"
Have you had any luck with fixing the issue? I downloaded the portable install as well with no luck.
I was using version 0.9.8.20, tried out beta version 0.9.9.40 (i think), but went back to 0.9.8.20. I backed up my file repeatedly, but the back up I need has been touched by the beta, and won't work. Two of my older backups work but they are really out of date. I also have a large library (816). And i'm not about to start re-entering, so if you have any suggestions let me know. rschip2@gmail.com
-
Welcome, rschip2.
As I understand it, there's no issue to be fixed. Unfortunately, if a database has been damaged by an early beta, then the damage is done and there's nothing the program can do about it. But what do I know... maybe it should detect and repair damage done by bugs in previous versions. 8)
There's still an issue, of course, but I'm not sure what should be done about it. Some like to live dangerously and use their only database in a beta without making backup. More are in the same situation as you—you made backup, but didn't realize your active database was damaged in this particular way for an extended period of time. I've done it myself.
Perhaps the program should be stricter about using databases from different major versions. It could automatically make a backup of a prior-version database before converting it, and refuse to open any database that has been opened in a subsequent version. The same thing could be done for any particular minor revision, if the risk was deemed high enough (e.g., early betas, where "big" changes are being made and bugs may not be found immediately). In hindsight, you would have been better off had you been forced to revert to your original database (i.e., that "untouched" by 0.9.9.x) when deciding to go back to 0.9.8.20.
If it weren't for this particular, perhaps unlikely problem, such precautions might seem like overkill. After all, database formats often change when a major revision is made to the program that creates them—so it's not possible to use the same database in different versions anyway. But it might be an effective way to prevent this sort of thing from happening again. It would also save users from themselves should they be so eager to try a new version they "forget" to make backup. ;)
-
Hi !
I have the same problem under Vista 32 Ultimate.
The -portable to launch the program has been successful but the Error 31 still pops up when I open the Database, I have spent a few hours trying desperately to transfer my old database (0.9.8.20) to the 0.9.9.11.
I unsinstalled 0.9.9.11, reinstalled 0.9.8.20, saved the DB, unistalled 0.9.8.20, reinstalled 0.9.9.11, ran it with the -portable (and tried without), tried to open the untouched DB but still the Error 31 crash.
I have tried the "run as administrator" too
Don't know what to do since the imbd plugin doesnt seem to work on the 0.9.8.20 version...
Thanks for any help ! (and long live PVD)
-
You need a database that was NEVER opened in 0.9.9. Install the new version and use Database -> Open.
The error message you are getting can only come out if you are trying to open a database that was previously open with one of the old betas and got corrupted.
...tried to open the untouched DB but still the Error 31 crash.
Are you suggesting nostra's diagnosis of the cause is incorrect? Have you tried using a backup version you are absolutely positive has never been opened in 0.9.9.x?
-
I am positive, the 0.9.9.11 is the first update I used since 0.9.8.20...
-
Okay, we'll have to wait and see what nostra thinks about this after he returns from vacation.
Just to be clear... Do you get the same error when trying again with a "fresh" copy of your 0.9.8.20 database—one "untouched" by previous attempts to open it in 0.9.9.11?
-
I have a similar problem since I installed the latest version. It worked the first time I opened the program but the second time I started getting these errors:
Failed to open database
File is not a valid database Connection authorization failure Error Code: 3
I do have an untouched version of my old database. What can I do to fix it?
-
File is not a valid database Connection authorization failure Error Code: 3
I'm not familiar with that error message, but the wording of it makes me wonder if the program is trying to connect via a server (which won't work unless you have Firebird installed). Do you get the same error message if you Open the database (i.e., using the command on the file menu)?
I do have an untouched version of my old database. What can I do to fix it?
What happens if you make a copy of that, and try to open the copy?
-
Failed to open database
File is not a valid database Connection authorization failure Error Code: 3
I think I got the same error recently when trying to open a database from a user account that had been opened from an administrator account (actually opened from firebird server running as service which has administrator privileges).
Login as an administrator and try to open the database again, you may well find it works.
-
I am positive, the 0.9.9.11 is the first update I used since 0.9.8.20...
It should not happen when upgrading directly to 0.9.9.11 (I does not in my tests). I'll send you my FTP access login by PM, so I can investigate the problem.
-
Thanks!
I sure hope that my database isn't fried...
-
Tell me when you are ready uploading your database...
-
I uploaded my database a few days ago.
-
I got the same error messages. But the circumstances are different. I work with PVD 0.9.9.11 and this is the first installation of the program on my windows xp pc.
1. start PVD as user1 and create the database MOVIES.PVD in
<D:\Dokumente und Einstellungen\User1\Eigene Dateien\Personal Video Database>
2. Put some videos in
3. Close the program
4. Copy the data base to <D:\Dokumente und Einstellungen\All Users\Dokumente>
5. Try to open the database with dopple click as user2
now I get the two error messages:
Konnte die Datei nicht öffen
file is not a valid database Connection authorization failure. Error Code: 3
As user administrator I don’t have any problems. So it seems to be a security problem. With the process monitor from sysinternals I found out, that PVD (started as user2) tries to open the file “D:\Dokumente und Einstellungen\User1\Anwenderdaten\Personal Video Database\pvdconf.ini”
If I try to open the database <D:\Dokumente und Einstellungen\All Users\Dokumente\ MOVIES.PVD> as user2 with the dialog “Datei -> öffnen”, then only the message “Konnte die Datei nicht öffen” appears.
Why wants PVD to open a file from an other user account?
I hope, this give a hint to solve the problem. I am very interested in a solution. Because in our family each one has his own user account (without administrativ privileges) and the PVD shoud be usable by each family member.
-
I hope, this give a hint to solve the problem. I am very interested in a solution. Because in our family each one has his own user account (without administrativ privileges) and the PVD shoud be usable by each family member.
+1
Well done. Have the same problem and has been present for some time.
-
Why wants PVD to open a file from an other user account?
I don't know of any specific reason why it wouldn't work, but I wonder if the program is intended to be run using a different configuration file for each user...
What happens if pvdconfig.ini is copied to D:\Dokumente und Einstellungen\User2\Anwenderdaten\Personal Video Database?
What happens if the program is started with the -portable switch, forcing it to maintain one configuration file in the program directory?
I'm not sure what impact the location of the database is. To test the above, I would move it outside D:\Dokumente und Einstellungen, and make sure the references in pvdconfig.ini point to the new location.
-
I don't know of any specific reason why it wouldn't work, but I wonder if the program is intended to be run using a different configuration file for each user...
Rick, PVD is recording location information in it's database file. Moving the database to a new user results in it sometimes accessing the old users data (ie uses absolute addresses). This trips an access violation. See http://www.videodb.info/forum_en/index.php?topic=969.msg3888#msg3888
-
...
Have you had any luck with fixing the issue? I downloaded the portable install as well with no luck.
I was using version 0.9.8.20, tried out beta version 0.9.9.40 (i think), but went back to 0.9.8.20. I backed up my file repeatedly, but the back up I need has been touched by the beta, and won't work.
Sounds as if you would have benefited from some warning which hopefully will be available in the future http://www.videodb.info/forum_en/index.php?topic=1241.msg4759#msg4759
-
Rick, PVD is recording location information in it's database file. Moving the database to a new user results in it sometimes accessing the old users data (ie uses absolute addresses). This trips an access violation. See http://www.videodb.info/forum_en/index.php?topic=969.msg3888#msg3888
Thanks, patch. My system is not multi-user, but I'm curious about this. If not a bug, should this not be considered a "design flaw"? I would expect to be able to copy a database file to any system, any location, and still be able to open it. More to the point, if I were in obi's situation, I would expect to be able to create a database in a user-neutral location (i.e., not in a user's "My Documents") that could be opened by any user. I wonder, however, whether that requires using a shared configuration file (by using the -portable switch), or if each user could have their own configuration (by allowing it to be saved in their own application data directory).
Is the issue any different if the Firebird server is used to connect to the database?
-
It seems to be some kind of Firebird Embedded problem. The database should open if you use File -> Connect to server instead of File -> Open (of course you will need to install the Firebird server first)
-
Is that the only solution, or can the problem be avoided in the manner I suggested. Some might prefer not to install the server if they don't otherwise need it. Also, isn't it still necessary to open the database in the usual way to optimize and create a backup?
-
I'll try to fix the problem, but I am not really sure if I can change this behavior from my side. The -portable switch will change nothing in this situation.
Also, isn't it still necessary to open the database in the usual way to optimize and create a backup?
Backup/Restore should work with server connection as well, but I have not checked it.
-
I'll try to fix the problem, but I am not really sure if I can change this behavior from my side. The -portable switch will change nothing in this situation.
I had assumed it was a problem with how firebird prevents multiuser access, thus outside of your control.
With the process monitor from sysinternals I found out, that PVD (started as user2) tries to open the file “D:\Dokumente und Einstellungen\User1\Anwenderdaten\Personal Video Database\pvdconf.ini”
Access to pvdconf.ini gave me some hope though as I thought this was more likely to be from PVD than firebird, but I could well be too optimistic.
-
Hi to all! :D
Thank you for a wonderful program. :)
I'm a new user and spent the night adding movies. Then all of sudden today I got the error code 3 message. I found the solution myself while preparing to ask for help here. I thought I'd mention it in case some other newbie has done what I did.
I accidentally had opened two instances of PVD. The old one ran in the tray and I had forgotten about it. That was all. I'm a happy camper again. :-*
-
Welcome, mumin.
Thanks for pointing this out. In testing this, I see the resulting error messages are exactly as reported here...
I have a similar problem since I installed the latest version. It worked the first time I opened the program but the second time I started getting these errors:
Failed to open database
File is not a valid database Connection authorization failure Error Code: 3
Hopefully, looneytv has since figured that out.
BTW, if you'd rather do without the minimize to tray behaviour, remove pvdtotray.dll from your Plugins directory.
-
Hi again !
Thx again Nostra for fixing my DB. It worked fine for 2 or 3 times but then I get the Error 3 again and if won't load the DB... (I have checked to see if 2 instances were running but they weren't... I even rebooted just to be sure)... The -portable.bat works fine and I can open my db through there, but it resets my settings.
I need some help !
thanks !!!
-
So there are 3 known situations leading to this error message:
1. the database is corrupt
2. you are trying to open multiple instances of PVD with the same database (local)
3. you have created the database under a different user account and the one you are using now has no permission to use the database
P.S. I'll improve handling situation number 3 in the next version.
-
The -portable.bat works fine and I can open my db through there, but it resets my settings.
All the -portable switch does is make the program look for/save its configuration file in the installation folder rather than the Application Data directory. If there is no configuration file there, it creates a new (default) one. This is why your settings are "reset." One of the things saved in the configuration file is recently/last used database information. The fact you can avoid the error by using a new configuration file suggests there might be something wrong with this information.
So, try this...
1. Make a copy of the pvdconf.ini file in your Applications Data directory (in case this doesn't work).
2. Modify the original by deleting the [Database] section (normally located at the beginning of the file, but could be anywhere).
3. Start PVD normally (i.e., not with the -portable switch).
4. PVD should start with no database loaded. Use File - Open to select the correct version of your database.
5. If the database loads, you're done. If it doesn't, restore your original pvdconf.ini, and tell us what happened.
-
It worked !!
THANX !!