You likely have a damaged or corrupted server.pem file. Replace it on the clients showing symptoms and it should fix the problem. The file is located in:
C:\Program Files (x86)\FileMaker\FileMaker Pro 12 (Advanced)\Extensions\OpenSSL\.
I copied the server.pem from my working Windows 8.1 install over to one of the "broken" clients, no change. Any other ideas out there?
If you're trying to connect via "Local Hosts", have you tried setting up a Favorite Host, with the explicit address of the server? Also, have you tried entering the name of the database in the Network File Path field of the open remote dialog?
You said that the machines couldn't "see open databases", but I'm not sure whether you can see the server itself or not. If you can't see the server, it could be a network issue, where it's not seeing the "local" host. If you can see the server but not the file, try entering the database name.
I doubt this is a solution, but it might provide new clues as to what's going on.
FM13 Certified Developer
We usually install FileMaker with the database server setup in Favorite Hosts. I have tried using the full Network File Path in the open remote window with no luck.
To rule out firewall or network issues I opened a telnet session from one of the broken computers to the server over port tcp 5003 and was able to connect. I can also get into the admin console, so as far as I can tell it isn't a network issue.
I have even tried placing a shortcut to the database on the desktop that uses the FMP:// URL to the database directly with no luck.
I think my only option left is to wipe the machine and reinstall windows. I was hoping to have an answer as to what caused the problem, but I'm not getting anywhere. Thankfully, out of 500 installs 3 are messed up.
EDIT: to add to the symptoms list... The computers cannot see any remote host. I have tried our primary, our backup and an offsite hosted service (tripple8) no luck accessing remote databases on any of them.
I have replaced the server.pem file in C:\Program Files (x86)\FileMaker\FileMaker Pro 13\Extensions\OpenSSL as well as C:\Users\username\AppData\Local\FileMaker\FileMaker Pro\13.0 with no luck.
Time is running out, so a fresh reimage may be the only answer.
Still having issues with this issue.
To add to the problems, when FileMaker 13 Pro Advanced is launched on this machine, the "getting started" database comes up as corrupt or damaged.
I am still unavailbe to open any remote databases.
Have you verified the hard drive on this machine? I'm wondering if you don't have bad sectors.
I assume you have checked to make sure that the databases FM12 can't see have not been checked to require minimum version 13?
The laptop functions fine in other ways. I haven't done a disk check yet, the user is okay without FileMaker for awhile. I'm cloning the drive to another laptop and will hopefully find a solution. We had a similar issue with an out of box laptop running Windows 8.1. The fix there was to wipe and reinstall the OS, then FileMaker worked.
We have a mix of FM 12 and Fm13 users connecting to the databases. We have ruled out network issues, it is just this one laptop that cannot see the open remote databases.
Given that, you might still have some bad sectors that didn’t get marked properly. Or, you might have another OS install issue that’s preventing FM from accessing something it needs.
We have issues like this from time to time. One machine just decides to act flaky. Wipe and reload is painful, but might be necessary.