Command failed with exit code 10904

OttoFMS
1

Migrations have been failing every week after upgrading from 4.8.x to 4.11 with an error code 10904.

The exact error is:
Error closing files: Command failed with exit code 10904: C:\Program Files\FileMaker\FileMaker Server\Database Server\fmsadmin.exe CLOSE _ActiveQueue.fmp12 -y -m Please quit FileMaker immediately for a scheduled update. -u admin -p ******** 10904 (No applicable files for this operation)

The files eventually do close, but OttoFMS has already given up. This server is under heavy use; it’s not uncommon to have up to 100 connected users during the scheduled migration, so it takes a long time for them to close out. If I rerun the migration immediately after the error it works fine each time. Is there an option somewhere to allow extra time for the files to close?

TIA,

Dave

2

Wow that is a weird one.

I have never seen Please quit FileMaker immediately for a scheduled update

Not sure where that comes from.

But I do think we are giving up to soon on closing files. We’ll address that next week.

Here is what I would do. Build a head of time. This should probably be your default mode on any large migrations, it’s a better workflow

Run your build, optionally push that build to the Prod servers inbox.
When it’s done, On prod, close the files manually, then kick of a deployment that uses the servers inbox for the source.

The migration will start immediately as the source files are already there.

We’ll see if we can add more wait time, or fix the issue next week.

Thanks

Todd

1 Like
3

Hmmm… I could have sworn that OttoFMS had an option to change the default message when closing files, but I can’t find it now. I’m pretty sure that’s a custom message that I came up with. That, or I’m losing my mind.

4

I confirmed that it’s a custom close message. I forgot that it was in the deployment options in OttoDeploy, not an OttoFMS setting.

image
image1197×233 49.6 KB

5

Oh yeah. I forgot about that.

Thanks for tracking that down

Todd