Link to home
Start Free TrialLog in
Avatar of j_rameses
j_ramesesFlag for United States of America

asked on

How do we re-open the status of a database when it does not allow us to do so?

We have Filemaker Pro 9 on the client machines and Filemaker Server 9 on our server.
In the Panel, section Administration --> Databases, we can see the list of our databases.
One of them has the status of "Closed".
We try right-clicking on it and selected the option to "Open" but nothing happens.
We also, try selecting, "Resume" but nothing happens.
We copied the database itself from the server to a flash drive to the client and copied it to the desktop.
When we clicked on the file itself we get an error message that says:
"Access priviledges to this file has been damaged or possible tampered with.  Contact Filemaker technician support if this cannot be resolved."
We tried restoring our SBS Server but nothing happened, we still get the same error message and problem.
Pls advise how to resolve this.
ASKER CERTIFIED SOLUTION
Avatar of billmercer
billmercer

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of j_rameses

ASKER

billmercer,

unfortunately, the recent copy of the file is dated May 16, 2008.
I thought I made a copy of it on June 16, 2008 but it was a copy of the May 16th file.
The file I named it "back up name_of_file", and the date on it when last accessed was the 16th of May.
Where does FileMaker keeps the original file, under C:/Program Files/FileMaker/FileMaker Server/Data/Databases?
The other databases we created were not affected, it was the main database that was affected.
On the server side it displays the status as "Closed" it won't open when I right-cllick on open.
We just started working non-stop with it for the last two weeks.
And we created many new layouts and databases.
Our database is not online, so we are lucky that we did not have data.
Why is it when we do a SBS restore (roll-back) to the 18th, it does not provide the file on the server?
Does an SBS back-up takes care of FIleMaker as well or only itself (Microsoft)?
THe only thing we did last on the server was to close a database and remove one from the FM server, I tried to do this but I forgot to turn off my client side FileMaker, but the server-side informed to close it before it could close and remove the database.  When I closed the client, I selected close on the databse then remove.
When we later went to play with FileMaker it did not respond(the main database).
Any other solutions?
SOLUTION
Avatar of Member_2_908359
Member_2_908359
Flag of France image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
thank you both for your help
Avatar of billmercer
billmercer

"Any other solutions?"
You might want to contact FileMaker tech support, they have a service that can sometimes recover databases better than you could do on your own. I don't know how much it costs though.
"Why is it when we do a SBS restore (roll-back) to the 18th, it does not provide the file on the server?"
I'm not familiar with SBS backup so I don't know what it includes and excludes by default, but running a backup of a FileMaker database on a server with third party software is pretty much a no-no.

Anything which accesses a FileMaker database file while it is open can cause problems. That includes not only backup software, but also virus scanners, and even having the database in a shared folder that's visible to others. FileMaker Server has its own backup function, you should use that instead.

Going forward, use FileMaker's built-in backup to make a backup copy of your live database files in a separate Backup folder.

Then, when running your backup software, make sure that the backup is set to EXCLUDE the live database folder, and INCLUDE the Backup folder. Also make sure the FileMaker backup is scheduled to run half an hour or so before the server backup starts, so they won't overlap each other.