Build says it fails on-screen, but the build had been zipped and outboxxed already. Deployment Fails

OttoFMS
1

I’m trying a deployment that I have run in the past, but this time it keeps failing.
There are events in the log that show up complaining that authentication fails, but it refers to a database that has nothing to do with the deployment I’m running.



|2025-11-19 07:51:17.108 -0800|Information|518|atlas.sierrahardware.net|Administrator connected: admin [10.147.20.185] (fmsadmin).|
|---|---|---|---|---|
|2025-11-19 07:51:17.109 -0800|Information|738|atlas.sierrahardware.net|Database SAPLaunchpad being closed by admin...|
|2025-11-19 07:51:17.122 -0800|Information|168|atlas.sierrahardware.net|Database SAPLaunchpad closed.|
|2025-11-19 07:51:17.122 -0800|Information|520|atlas.sierrahardware.net|Administrator disconnected: admin [10.147.20.185] (fmsadmin).|
|2025-11-19 07:51:17.819 -0800|Information|518|atlas.sierrahardware.net|Administrator connected: admin [10.147.20.185] (fmsadmin).|
|2025-11-19 07:51:17.822 -0800|Information|520|atlas.sierrahardware.net|Administrator disconnected: admin [10.147.20.185] (fmsadmin).|
|2025-11-19 07:52:10.844 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:11.541 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:12.238 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:12.936 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:13.633 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:14.318 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:15.013 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:15.710 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|
|2025-11-19 07:52:16.402 -0800|Warning|661|atlas.sierrahardware.net|SECURITY: Client richarda [127.0.0.1] authentication failed on database SierraHardware.fmp12 using richarda [fmxml].|

The correct database is SAPLaunchpad, the unrelated one is SierraHardware.
I did recently change my username in SierraHardware, so that is the incorrect username.

Two Questions:

  1. Why is my deployment of SAPLaunchpad failing and trying to authenticate to SierraHardware.
  2. Where is Otto getting this ‘richarda’ username from? I’ve updated the username everywhere, I thought. I don’t think I’m using Data API keys.
2

Hi Richard,

That log is FileMaker log. Otto doesn’t use that log. So I think those log entries are unrelated to an Otto Deployment

Take a look at the full debug log

And send us that if you need more help debugging.

Thanks

Todd

3

debug-logs-49.zip (53.4 KB)

I was suspicious because every failure looked the same in that area of the logs, but you’re right of course. I think I tracked those authentication problems to a CalDAV client talking to the 360works Zulu Calendar. The FMXML, and the Localhost IP led me there. This part is moot.

Anyway… I checked out the logs you pointed to. I’m not sure what the problem is. The logs seem to show the build being successful and placed in the outbox, but I interpret the on-screen log differently.

Screenshot 2025-11-19 092807
Screenshot 2025-11-19 0928071185×395 56.7 KB

4

Hey Richard,

We’ve seen a similar issue before, in the build log on the source server does it get stuck right after a log that says “zip file completed” or something similar? I’d try restarting your source OttoFMS server and trying again.

-Kyle

5

That worked.
I changed the post title accordingly.

I have more information that may be of little help. I noticed something else odd in our server event log:

2025-11-19 03:08:37.476 -0800	Warning	1109	dev.sierrahardware.net	WARNING: Your licenses have expired. You must uninstall or contact Claris International Inc. immediately: https://www.filemaker.com/redirects/fms22_admin.html?page=license_violations&lang=en

According to our Admin Console, our license had already been valid, and wouldn’t expire for a long time. But it’s possible that the server had not been restarted since a license update.