OK this may be an OttoDeploy question, but since we was reading the logs from OttoFMS, I’ll put it here.
Client has a bunch of issues with FileMaker Server 18, and some data issues with their aprox 65 files (about 6GB). They agreed to build new (in house) servers to move to FileMaker Server 24/21. A new Dev and Prod Server are created.
Clean up of files has occurred and the cleaned up files are put on the new Dev, and copies of the current production files are placed on the new Production server so that we can do a test migration for the client.
• Note, I’m can’t do this directly because my account is isn’t set up, so I step my boss the process on his account. All though though a Citrix connection of some sort.
Eventually the boss agrees with my suggestion to break down deployment into multiple sub deployments. This helps find the myriad files that did NOT have our developer password installed. There was much frustration on his part with this.
But finally there were three hold holds that didn’t want to migrate. I think all of these may have had a Capitalization difference. This shouldn’t affect things normally with FileMaker, but still we were getting errors so he made sure the name matched.
Still we get the following kinds of errors “File not found: Chi log book fmp12 on the server. Can’t migrate it.” yet, the file is right there.
This has caused much consternation and distain for the product (it was his first time using it). So, I’m hoping for some guidance. Keep in mind, I’m still having to work on this a proxy in the middle.
Although it doesn’t normally effect FileMaker operations, ie using FileMaker, File Name case absolutely does effect dev ops types of operations which are subject to the operating systems file system case sensitivity.
OttoFMS uses a combination of the Admin API, the FileMaker command line tool, and node file system commands, to locate files on the hard disk. Linux is going to care about case. Windows doesn’t.
If the files are not cased and spelled identically then you would get the result you are seeing.
If somebody asked me to dive into this I would address one file at a time, looking very carefully at things like extra spaces and mismatched case. I would also make sure the FileMaker Server opened the files and displayed them with the correct case on the Admin Console.
I understand that a new persons might not understand the nuances of this stuff and will have a hard time trusting something that seems to fail at something so easy. I can only say that in 2024 OttoFMS migrated over 60,000 FileMaker files. It is now going at a clip of about 10,000 successful FileMaker File migrations a month. I don’t believe any other tools comes close to this level of use.
A challenge came for my supervisor, however, in that he changed the actual name of the files (the capitalization) so that they would match the destination files. OttoDeploy, keeps showing the “wrong/old” capitalization. Now, so long as the Destination files were done right, it worked, yay. Is there a way to refresh this?
He did try creating a new deployment but it was the same result.
Thanks Kyle, I pass the word along. At the moment, I can’t test this because…I don’t yet have access to that server. The fun part was that the Otto file browser (a great gift man kind) shows the files in their actual name
The whole “must match case” thing (on the destination server, at least) has caused much consternation.
Yeah I can see that that would be frustrating. I can’t think of any ways that OttoFMS could work around this, as it is possible to host multiple files with the same name cased differently, so we can’t match insensitive of case. Is there anything that would’ve made the process less frustrating beyond a button to refresh the server file list in OttoDeploy?
After testing, command R did not, in fact, correct the capitalization files in the source file list. So, go figure. If it matters, this is a windows machine.
