I’m getting the following error when trying to run a “migrate” deployment:
Build server error. http Status: 400. FMS Error 18003: The following files were not open with a NORMAL or CLOSED (for copies) status when the build was started: Amps_OttoTest.fmp12 CLOSED
I got this same error on two separate setups. One is a pair of Soliant.cloud servers, the other is on-prem.
otto-logs.zip (1.7 KB)
That error looks like the file is closed on your source server. OttoFMS cannot make clones of closed files. Is the file on the source server closed?
-Kyle
Thanks kduval. That error is misleading. The file was open on the server when I tried to run the deployment.
Hey @Mislav ,
Just for clarity’s sake, the file was open on both the source and destination servers when the deployment was run? Thank you!
-Kyle
the file was open on both the source and destination servers
That’s correct.
Hi Kyle, I sent them to you in a DM.
Any news? Im getting the exact same error.
@Mislav Did you get this error solve?
Nope, I did not. One of my colleagues did a troubleshooting session with Proof Geist. but they didn’t succeed in nailing down the problem. They said they’d add more logging into a future version of Otto to get better insight into what the issue is, but looking at the current release, it doesn’t look like that additional logging has been added yet.
Correction, the additional logging hadn’t been added to v4.11.0. We haven’t had a chance to check out v4.11.1 yet.
Its the same thing with v4.11.1
@kduval Any update?
Hey @yorleumas ,
Can you send me the debug logs for the deployment you’re having the issue with?
-Kyle
The process that is checking to see if the file is open is using the fmsadmin list databases command and the status therein. I would check a few things:
Its possible that the list database command can display different files and statuses from the admin console/OttoFMS if you have multiple files with the same name in your Databases directories. I’ve seen this happen when renaming files into the folders with the same name. FileMaker doesn’t really handle having multiple files with the same name.
The other possibility I could see is if you’re on a Windows server the list databases command does not handle non-ASCII characters. So if you have a database name with an umlaut or something in it the command will not find your file properly.
In @Mislav 's case, I suspect it is a multiple files with the same name problem, I am not sure about your case @yorleumas without seeing an error message.
-Kyle
Hey Kyle, our issue wasn’t due to multiple files with the same name. I just ran the test today with a previous deployment build that didn’t work but it is working now. What we did was below:
I was able to run a install in place, also a migration from the dev server (now running on FMS 21.1.5.500) to production which is running on FMS19
Hi @kduval, Here the link to the log. I cannot add file directly to the conversation cuz im new.
https://drive.google.com/file/d/1wf-dtVmPctg7EEwqhOqBd2wKRaqDhIf_/view?usp=sharing.
Both servers had the FileMaker file open. The file is named Histlog.fmp12, which contains no special characters, and there are no other files with the same name.
Can you see whats wrong into the log file?
Thanks
Samuel
@yorleumas do you have access to the command line on the source server? can you run the fmsadmin list files command for me and let me know what the values you get for that file are?
-Kyle
@kduval Here the list files for both Dev and Prod server : The file is showing.
@yorleumas sorry, could you run it with the “-s” flag? that will return the file statuses as well as the paths. I should’ve been more clear when I requested that, my apologies.
