FM Server 14 is the finest collection of bugs I have ever encountered
15 posts in this topic
I'm looking for a little feedback on hosting our FM 14 database through a different port other than 5003. We are experiencing latency issues with our Filemaker Go clients being on hospital wifi's and a lot of the accounts are blocking ports. We would like to use 443 to host the file to avoid blocked ports or other issues. We currently have a VPN setup to help with this issue, but, this tends to be hit or miss for our sales rep. These reps typically like to get in and out quickly and have severe ADD, so getting kicked out and having to trouble shoot how to get in and stay is making them feel like the database isn't working well.
Does anyone know of a way to host files through 443 instead of 5003? If so, will this mess with any container fields, or will anything need to be reset as far as the configuration goes? I realize this may be an "off label" type situation, but, we are desperate and if it works but just isn't recommended like many other things Apple shoots down, I would like to pursue it.
Any feedback would be greatly appreciated, thanks everyone!
By Aussie John
Hi - my backup schedule is acting odd. The log says the schedule has aborted as the destination is "not writable" and some files may be left at the destination.
A look at the folders seems to show them being written but they are not deleting after the nominated number. The status in the schedule window also says permission denied.
I am using a custom backup folder but to test, I swapped it back to the default folder with the same issue. Any help much appreciated - thanks
So i've got an active fmp7 database running on a 9.03 server... The hardware is already years passed its expiration point, and (due to that annoying java issue) I don't think I can install it on a newer OS model.. Am currently running on Mac OSX 10.5, and can't seem to get the Admin software to work on 10.6 in any usable way..
So my plan: utilize a new(er) server with FMS 14, install it, and use it to serve the older FMP file..
I've been told that a newer server will handle older files (as long as I don't change them import them into a newer FMP app and re-save them).
Is this path good, bad, or just plain impossible?
I've got a currently-served solution (9.03) happily running on a (now 9yr old) server, which has well, long overdue for heart failure.
Also have FMS 14 and a current machine prepped and ready to run.
I'd like to run the Server 14, host some 14 files, and also host the version 9 file on it (have an unlimited site license for version 9 software, which suits this location well)...
Anybody know if that will work?