FM cannot find the volume that the file is located on????

[Cybrwolf]

I have a network of Macs (G4 400s & 500s, and two iMac DVSEs) When I work LOCALLY, and when I am trying to import 12,000 records into a existing DB of around 30,000 records or if I am just deleting records, every once in a while I get the error messge "Sorry FM is unable to update the disk this file is on. Click continue to try again, or click Quit and copy this file to another disk."

I haven't seen this before, and it doesn't matter what computers the DBs are on. Version of FM is 5.0.3, Mac OS 9.0.4

I am out of ideas! has anyone seen this before??

------------------

Cybrwolf

[Kurt Knippel]

quote:

---

Originally posted by Cybrwolf:

I have a network of Macs (G4 400s & 500s, and two iMac DVSEs) When I work LOCALLY, and when I am trying to import 12,000 records into a existing DB of around 30,000 records or if I am just deleting records, every once in a while I get the error messge "Sorry FM is unable to update the disk this file is on. Click continue to try again, or click Quit and copy this file to another disk."

I haven't seen this before, and it doesn't matter what computers the DBs are on. Version of FM is 5.0.3, Mac OS 9.0.4

I am out of ideas! has anyone seen this before??

---

I usually find that FMP has run out of either run out of space on the disk, or has run out of swap space.

I would first verify that you really do not have a problem with the disk. Run Norton and fix any errors.

Then insure that you have enough of the disk space left. I think that the rule of thumb is that you should always maintain 10% of the disk space free. For instance on a 1GB drive you should keep 100MB free at all times.

Also you could just do a recovery on the file. Sometimes when you are doing this much creation and deletion of records, the files can get a little error ridden. Doing a recovery will cause the file to be rebuilt, without any loss of data.

Finally back up regularly, especially before you do any of this importing or deleting. Just in case anything unrecoverable happens to the file.

------------------

=-=-=-=-=-=-=-=-=-=-=-=-=

Kurt Knippel

Senior Filemaker Developer

http://www.inthescene.com

mailto:[email protected]

=-=-=-=-=-=-=-=-=-=-=-=-=

[danjacoby]

Another thing to do occasionally is to save a compressed copy, then replace the current version with the compressed one. That should free up some space.

HTH,

Dan

[Steve]

This is exactly the same problem I have. I am hosting a number of multi user FM 5 databases and from time to time the error message pops up. Which is really a problem because is prevents the db from serving new pages.

I am having this problem on serveral machines (from iBook to G4) all with plenty of memory and disk space (several free GB) and with a number of different databases (8).

Also Okey Dokey Control panel does not get rid of this problem.

FM Pro 5.0v3

System 9 (Extended Formating)

Tried turning Virtual Memeory on or off, no difference.

Any suggestions out there?

[nickelads]

This is the same problem that drew me to this site.

I'm serving about 8 Macs off FileMaker Pro 5.0v3. The server is a 7200/90 with additional RAM and a large HD with over 50% free. All of our office machines are running 9.0.4 with the exception of two old clones running 8.6 and a Titanium G4 PowerBook running 9.1. The office network is 10BaseT Ethernet. (It would be 100, but our ISDN modem (which also provides some hub duties) only has 10BaseT capabilities.)

I'm actually serving three multi-user databases from the 7200, but only one is complaining, and it's doing so frequently. The database is about 8000 records in size, and I'm beginning to fear that we are losing the occasional record due to this problem.

Norton Utilities v5 finds nothing wrong with the server's HD, and the problem repeats itself when the file is moved to another machine. The problem seems to be more frequent during heavy access by many users, or when users simply leave the database open on their machines for long periods of time with no use.

I have the sinking feeling that the file itself is damaged in a way that Recovery won't help (it's been tried) and that I will need to export the records and re-create the database from scratch. I have been hoping, however, that that wouldn't be necessary.

Any ideas?

Michael