Work at SourceForge, help us to make it a better place! We have an immediate need for a Support Technician in our San Francisco or Denver office.

Close

#1006 Silent error writing to Database

open
nobody
V3 (197)
5
2012-10-04
2011-12-23
Rob Wilson
No

I have just updated to v3.27 from v3.23. I have always used a simple CMD script on windows to start PasswordSafe consistently: start ..\bin\ps\pwsafe.exe PWS.psafe3 -u auser -h ahost

In v3.23 all was fine. I could add an entry, quit, restart and the entry was there.

In v3.27, something is broken. I add an entry, it appears to be be saved (you see the telltale pause and flicker), but when I quit and restart the change is NOT there. For my change to work, I have to first explicitly "close" the database, and then reopen it from the "File" menu (either from Open... or from the list of recent databases) and then make the change.

On a likely related note, I had to turn off "Intermediate Backups" in the configuration menu. When it is ON, I get an "Write Error" dialog which says "Unable to create intermediate backup.. Either try to save database with another name or exit without saving." I have never seen this in v3.23 or earlier

Discussion

<< < 1 2 (Page 2 of 2)
  • DrK
    DrK
    2012-01-04

    Rob,

    Did Validate fix your issue?

    David

     
  • James Walters
    James Walters
    2012-02-25

    Sorry this took so long to get back on this. I have discovered another data point. When I do a "Compare" of two databases (generally one on my main Windows machine that I have added entries to, against the database on my laptop) for syncronization purposes (yes, there may be other ways to do this, I realize that), I found two issues, the first only allowed me to transfer two entries across ("Copy to original") while ignoring the right click after two entries copied. This is a new issue just encountered.

    The main issue is that after I ran the compare again and it let me copy the last entry across, running "Validate" on this latest database showed an invalid UUID for the just copied last entry only. The other two entries that were copied first were ok. I then ran a validate on the original database with no problems found. Looks like there are some issues with copying from database to database, with the UUID being corrupted. As I now remember, the other entry that I found a bogus UUID with was also copied across using this same procedure.

    Hope this helps.

     
  • James Walters
    James Walters
    2012-02-25

    Oh, also, the two entries that had bogus/corrupted UUIDs had "0"s in them for a UUID. All other entries in the XML seemed to be correct. I hope this would make my sending you the XML now not necessary.

     
  • DrK
    DrK
    2012-02-25

    Please upgrade to the just released V3.28. This release validates all databases at open time unless overridden with a command line flag "--novalidate" (without quotes).

    It may have fixed this issue, although no promises as I don't fully understand your issue.

    David

     
  • Rob Wilson
    Rob Wilson
    2012-03-07

    I am the original problem person in this thread. I just updated to 3.28 and still have the same problem.

    I open the PS (and the DB), and then edit an entry. PS complains that incremental backup has failed (until I turn that off in the preferences), and the write does not happen.

    I then close the DB (but leave PS open). I reopen the same (and only) database. At this point I can do edits and saves will happen without a problem.

     
  • DrK
    DrK
    2012-03-07

    Did you add the "start" command line flag "/D" as I suggested back in 2011-12-25 15:56:14 PST?

    David

     
  • Matt
    Matt
    2012-10-04

    Bug report #1063 may help explain why the 'intermediate backups' issue is happening. I just discovered this myself and did some thorough testing and came to a conclusion that when including the safe file (i.e. <file>.psafe3) in the path of the shortcut or command line statement, if you do not include the absolute path, the program doesn't look at the directory in which the psafe3 file came from properly. It will open, but when you go to close the file, since it doesn't include the present directory in which the psafe3 file came from, it can't save back to its original file/location.

    Please review the report for more details.

     
<< < 1 2 (Page 2 of 2)