AnsweredAssumed Answered

Year End Clone of database cannot be opened from the server

Question asked by KeithFletcher on Dec 31, 2014
Latest reply on Jan 6, 2015 by TSGal

Summary

Year End Clone of database cannot be opened from the server

Product

FileMaker Server

Version

FMS 13

Operating system version

Windows

Description of the issue

Each year I clone a database and re-name it for the next year. I turn of the server (close the files on the admin console), then go into the server and open the file I want to clone and clone it. I then turn the server back on (open the files) and when I attempt to open the new cloned database, I receive an alert that reads <"NewClonedDatabase.fmp12" is currently in use and could not be opened. If the file is shared, you can use the open remote command to open the file on the network.> I have never had this problem before but considering it is only done once a year, I may be missing something. If I go into the server administation and close that database, I can open it so it seems that the server is not allowing it to be opened if it is open on the server. All other files open fine except the new cloned copy.

Steps to reproduce the problem

1. Turn off server from server admin console (close)
2. Go to the server and open the file I want to clone directly from the server.
3. Save a copy as a clone on the server.
4. Close the file
5. Go to the server admin console and start the server (Open)
6. Confirm that all files are showing a status of normal.
7. Open the file from FM pro - cannot open the file

Expected result

Being able to open the new clone file from FM Pro after saving a new clone onto the server

Actual result

Cannot open the new cloned file unless i change that file to closed on the server

Exact text of any error message(s) that appear

"NewClonedDatabase.fmp12" is currently in use and could not be opened. If the file is shared, you can use the open remote command to open the file on the network. (If you've opened the file before, check the opene recent menu)

Workaround

Open remote allows me to open the database.

Outcomes