Database may be damaged use the Recover command in FileMaker Pro 16. FileMaker Server 16.0.3 on FMS reported the following event:.Note that, because there are certain details of my client's environment that I do not want to publicly disclose, I changed the FileMaker host name to ' FMS' and the database file name to 'FMDB'. (This particular solution consists of just one file.) It said the database was damaged and could not be opened.īelow is the full notification that was sent. I learned about the outage about an hour later, thanks to a 12:40 pm FileMaker Server email notification.

My client's server crashed on Tuesday, April 17th at 11:45 am. Error 242 Database could not be opened may be damaged What follows is an account of how the new Data Migration Tool made it possible for me to quickly address a database corruption issue for one of our clients. This is exactly what happened to me not too long ago. However, if you find yourself in a situation where you have to recover from a damaged file, you will suddenly develop a strong appreciation for the existence of this new tool.

The second use case will probably not garner as much notice. Please see my colleague Matt Hintz's post for a detailed examination of this use case. The first use case is likely to receive the most attention.

Revert to a known clean clone by migrating data from a damaged production file.

Deploy development changes by migrating production data into a development file.

The Data Migration Tool has two primary use cases: has rolled out a new tool to make migrating data between copies of a database file much faster and easier. As part of the FileMaker 17 release, FileMaker Inc.

See user history in filemaker pro 16