I am currently attempting to set up a deployment from a development server to a testing server. The initial deployment process was successful and efficient, as I was working with a relatively small test file. However, upon duplicating the deployment and modifying the destination, I encountered an issue that necessitated the abortion of the process after it had run for 21 hours. The error message indicated that the file AssetsTestFile.fmp12 was not found while attempting to open the files. It is important to note that the only significant difference in this scenario is that the new server operates on a Mac and is connected via a VPN.
Hey Malcolm,
Could you send along the deployment debug information for that deployment? I’d like to take a look at the logs and see whats going on here. I suspect what is happening is that your FileMaker admin server is hanging or something similar, and a restart of the admin server on the destination may fix it, but I’d still like to take a look at the logs.
-Kyle
Hi Kyle.
I really appreciate you checking this out. I did a quick FMS restart first and also updated OTTOFMS to version 4.9! Thanks!
Attached the Logs
Malc
Hey Malcolm,
I think what is happening here is that the source server is unable to push the build to the destination server, probably due to your callout about the VPN. I would try toggling off the “push build” option in OttoDeploy and try it again.
The “filename.fmp12 was not found when opening” error is a bit of a red herring, it just means the file was not installed but it tried to open it anyways.
-Kyle
Hi Kyle
Many thanks for you help with this, after a bit of research i found out how to toggle the button you mentioned and it worked fine, im a happy bunny now
1 Like
Glad you found it, sorry, I could totally have sent a pic along to help you get there. I’m glad its all working now!
-Kyle