AnsweredAssumed Answered

Delayed Write Failed

Question asked by PhilAllen on Mar 12, 2012
Latest reply on Mar 12, 2012 by PhilAllen

Summary

Delayed Write Failed

Product

FileMaker Pro

Version

8.5

Operating system version

Windows 7

Description of the issue

Hello, and thanks for reading. We have tried installing FileMaker Pro 8.5 on a new-ish Windows 7 Pro laptop. The program is accessing a file across the network and is getting the following error when closing the program:

{Delayed Write Failed} Windows was unable to save all the data for the file ; the data has been lost. This error may be caused by network connectivity issues. Please try to save this file elsewhere.

We also get this error when opening.

"CafeBackUp.fp7" could not be created on this disk. Use a different name, make more room on the disk, unlock it or use a different disk


There are other computers accessing the network file using FileMaker Pro 8.5 without any issues. We have connected the computer via Ethernet in case it was a poor wireless signal. Any suggestions on what to try?

Steps to reproduce the problem

Close the program to get one error. Open the file/program to get the other error.

Expected result

No errors on opening or shut down. File to be saved properly (it isn't).

Actual result

Errors and no saving of the file.

Exact text of any error message(s) that appear

The program is accessing a file across the network and is getting the following error when closing the program:

{Delayed Write Failed} Windows was unable to save all the data for the file ; the data has been lost. This error may be caused by network connectivity issues. Please try to save this file elsewhere.

We also get this error when opening.

"CafeBackUp.fp7" could not be created on this disk. Use a different name, make more room on the disk, unlock it or use a different disk

Configuration information

FileMaker Pro is installed on a Windows 7 Pro machine. The network is made up of multiple sub-networks. There are several physical locations with one hosting the main data server. Only one physical location is having this problem. Each location accesses it's own 'cafebackup.fp7' file, though they are all hosted in the same main directory on the main file server.

Workaround

None yet. We have tried uninstalling and reinstalling it.

Outcomes