#1102 Unable to create intermediate backup in Password Safe 3.30

[Buck]

I am reporting the same issue for v.3.30 as reported in v.3.29 with regards to the error message "Unable to create intermediate backup".

The only difference is, the details regarding the different options of saving the file and the full path did not correct the situation.

In this case, the file exists on a server, Windows Server 2008 R2 standard Service Pack 1.

I have double checked security, full rights on the source and target directories are in place.

It must be something where the file was not closed properly from the previous use.

A solution that I found to work, copy the file: i.e. copy a.psafe2 a2.psafe2 Opening the second version of the file allows editing without any other changes.

[Rony Shapiro]

Since you have a workaround, and I don't have access to Windows Server 2008 R2 to try to reproduce the problem, I'm closing this as "won't fix". Let me know if it pops up again.

[Buck]

yes - I can reproduce the issue. which is why I reported it in the first
place. the work around is just annoying but proves that it still works. I
have not found the reason for it yet.

On Wed, Aug 28, 2013 at 1:48 PM, Rony Shapiro ronys@users.sf.net wrote:

• status: open --> wont-fix

---

• [bugs:#1102] http://sourceforge.net/p/passwordsafe/bugs/1102/ Unable
  to create intermediate backup in Password Safe 3.30*

Status: wont-fix
Created: Wed May 29, 2013 01:08 PM UTC by Buck
Last Updated: Wed May 29, 2013 01:08 PM UTC
Owner: nobody

I am reporting the same issue for v.3.30 as reported in v.3.29 with
regards to the error message "Unable to create intermediate backup".

The only difference is, the details regarding the different options of
saving the file and the full path did not correct the situation.

In this case, the file exists on a server, Windows Server 2008 R2 standard
Service Pack 1.

I have double checked security, full rights on the source and target
directories are in place.

It must be something where the file was not closed properly from the
previous use.

A solution that I found to work, copy the file: i.e. copy a.psafe2
a2.psafe2 Opening the second version of the file allows editing without any
other changes.

---

Sent from sourceforge.net because you indicated interest in
https://sourceforge.net/p/passwordsafe/bugs/1102/

To unsubscribe from further messages, please visit
https://sourceforge.net/auth/subscriptions/

--
~ Kind regards ~
Jeff Buckley

[Andrey Kuznetsov]

When Password Safe create intermediate backup, it move original file (.psafe) to backup file (.ibak). If move operation is failed, it'll report about backup error. So to successfully create intermediate backup, user should have change/write rights not only to source and destination directories, but for .psafe file too.
Could you please check, that user, that run Password Safe, have necessary rights for original file (for example by renaming the file in Explorer, or using icacls command line tool, if pwsafe.exe and .psafe file have different integrity(mandatory) levels)?
If problem isn't in access rights to .psafe file, you can try to trace file operation with Process Monitor (http://technet.microsoft.com/en-us/sysinternals/bb896645.aspx). Process Monitor's log for pwsafe process should help to solve this problem.

[Bill Osler]

I have the same problem intermittently. I keep Password Safe (currently 3.27) on my desktop which runs Win 7 64 bit Professional. I have the desktop set to open the Password Safe database as Read Only because I almost never edit it at the desktop. Instead I usually access it and edit it via my laptop which also runs Password Safe 3.27 on Win 7 64 bit Professional. It's a long story.
Anyway, sometimes when I add a password (more often) or edit a password (only occasionally) on the laptop I get the error "Cannot create intermediate backup". I have found that if I exit Password Safe I am then prompted to save the safe, which I do, and when I re-open the safe the new data does appear to be there.
The permissions are correct and the problem does not occur every time.
I have had the problem with various Password Safe versions for years, and reported it previously when the safe was on a Vista system and I was accessing from an XP PC. If memory serves Ronys did not have access to a Vista system and thus was not able to investigate it at that time.
I do not have had anything like the expertise to figure out what is going one.