Ok folks - I'm ready to throw my Apple 23" cinema display and dual G5 out the window this problem is so frustrating.
A week ago our FileMaker Pro server (Win 2k server) crashed. The boot.ini file was missing and we thought the issue was only a hardware problem. All the hardware problems have been fixed though, the drives reformatted (FM databases were transferred to a network drive & an external hd for safekeeping during this work), the OS installed again from scratch. Well - we could barely get the computer to run once we began hosting the databases with server 5.5.
We decided to examine the possibility that it was a FM issue and not a hardware problem. We found that many of our databases wouldn't open in FM client. We have successfully recovered most of these files. A few that wouldn't cooperate we took from a slightly older backup and used to replace the files we couldn't recover. When these new installations of FM and Windows 2000 server along with the recovered data folder didn't get us in the clear we began to despair.
Since then we have migrated all our data to the aforementioned Mac running OS X Panther. We have successfully recovered and opened all but one or two of our files. These files that won't restore properly will be reconstituted by hand or just deleted. We installed the FM server module (and client) on this Mac (it's running FM server 5.5v4). When we start the FM Server service it shows most of our files. About 20 refuse to be hosted though.
This is thoroughly confusing to the three of us working together on this crisis. Why these files open without issue at all on the machine when we double click them (they open locally with the FM client of course) - yet they appear as 'closed' files when we log into the server via 'remote administration' is supremely frustrating! When we try to 'open' the files via remote admin we receive the following error: "Error occurred; unable to open file"
Please help me out with any advice you might be able to give. I've tried renaming these files but they just refuse to be hosted by the server module despite the fact that the client doesn't see anything wrong with them at all.
Just to recap we're using filemaker pro server 5.5 v4 on a mac running OS X panther;
we're using FileMaker Pro 5.5 client to access these files on a variety of computers ranging from OS 9 G4 iMacs to WinXP P-4 3 Ghz machines.
someone please save me,
~Tom