FbwfMgr failed: The network path was not found.

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I've noticed that after opening a file (with or without locking it for
exclusive use), fbwfmgr /commit commands fail with this cryptic message:

FbwfMgr failed: The network path was not found.

I cannot find any documentation on it specific to fbwfmgr. MSDN says I
should turn off the firewall... well this is a local file. For good measure I
did it, and ofc it still fails.

In my VFP program, before I open the files, I can commit. After opening
them, I cannot commit. After CLOSING the files, I still cannot commit! It's
confirmed that the files are closed (had another test program which attempted
to open the files exclusively at this point, and they opened).

Anybody seen this before?
 
Yes, we have the same problem. We designed our installation software around
this feature, so I'm hoping we can get a reply to this thread.
 
Ah, it appears that if you *delete* a file and then replace it, FBWF somehow
remembers that the file was deleted but forgets that it was replaced, so that
when you try to commit it, FBWF thinks it was deleted. But if you *copy over*
the file, all is well.
 
Back
Top