Databases
--
Questions
--
Followers
Top Experts
Details:
For years, we ran Filemaker 9 Server on an SBS 2003 box. Â We had Filemaker Pro 9 on the desktops, and we had no problem using the Filemaker Pro client and going file -> open -> remote and clicking on the server name in the left hand pane and the files in the right hand pane. Â We only used it as a database server - not at all web publishing.
We recently upgraded our server from SBS 2003 to SBS 2008 which is of course Windows 2008 64 bit. Â I have Filemaker 10 Server, and since FIlemaker 9 is not certified on Windows 2008, I installed FM 10 Server. Â I installed Bonjour 64 bit, and the install seemed to go fine and all the files are open (I first tried copying the files to the databases folder) and then I removed them and did an upload a database task. Â In each case, everything looked normal. Â Of note - in case it was an issue with 64 bit, I also have a spare server with Windows 2008 Server 32 bit on it, so I also tested in that case and got the exact same results on the client. Â See below.
On the client (all Windows XP) with Filemaker 9.0.3 Pro, if I click File -> Open remote, I see the server and its IP address in the left hand pane, but where I used to see the databases/files to open - there is nothing. Â Not even the sample file - which I think used to be there. Â I have brought down the files to the local workstation and opened them to check the file sharing - and it is indeed on. Â I have even turned it off - closed - reopened - turned on sharing again and closed again and then re-uploaded/added the databases to the FM server. Â I have also tried using Filemaker Pro 10 as the client - same result. Â I can see the server, but I can't see the databases on the server.
I'm at a total loss. Â This should be pretty easy, but I'm just not seeing the databases in filemaker pro. Â Any help is appreciated.
fm-admin-console.jpg
fm-sharing.jpg
fm-pro-client.jpg
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
Start up the database and check to see if you can now see it remote.
It is not obvious but this is the problem






EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
We eventually managed to ascertain that the problem was caused by a damaged certificate file (called 'server.pem'). Â On inspection, we found this file to be 2kb in problem machines and 6kb on machines that were working fine. Â Running FMP's SSL updater from the command line caused the problem for us.
You can locate the server.pem file using TextWrangler - select File / Open Hidden, then navigate to:
Windows:
Program Files >Â FileMaker >Â FileMaker 9
Mac OSX:
Applications >Â FileMaker 9 >Â FileMaker 9.app >Â Contents >Â MacOS
You can generate a new copy of the server.pem file by doing the following:
- Close any open instance of Filemaker Pro 9
- Navigate to and open
C:\Program Files\FileMaker\FileMaker Pro 9\Setup\openssl-new-cert.b
- A dialogue box will open and close, there is no need for input
- A file named server.pem will be generated and will be 6kb in size (the damaged one is 2kb in size).
- Move this file to C:\Program Files\FileMaker\FileMaker Pro 9\ and accept the prompt to overwrite any existing file.
- Open FileMaker Pro and all should be visible again.
I hope this helps!
on the server, I am set to "list all databases" - it's the default setting, and I'm set that way.
On the clients, I looked at two different computers - one where I still had FMP 9 and one where I had upgraded to FMP 10. Â On each one, the server.pem was 6 KB. Â I still renamed the server.pem file and then ran the BAT file as recommended. Â The file size of server.pem was the same after running the BAT file. Â
After putting server.pem in the right place, the results were the same - I could see the server, but not the files available.
I saw recommendations about server.pem - but figured it didn't apply to me since I don't use SSL in any way on Filemaker. Â Even still, that suggestion didn't help.
My next thing to try will be to make a virtual server running Windows 2003 Server and run Filemaker Server on there. Â I hope I don't have to do that.

Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
- has the IP address of your server changed?
- does your server have a proxy name; have you tried entering that into the Favourite Hosts list of File/ Open Remote to see if that comes up with anything?
If you have Filemaker client software installed on your starter, open a non-hosted file and see if you can peer-to-peer connect to it from another machine using the server machine's IP or proxy name. Â
Maybe try doing the same on your client machine to see whether other computers can 'see' the open file. Â That would at least isolate the server machine as the definite problem (if you can peer-to-peer on the client computer but not the server).
Then I installed FMS 10 on another 2008 server 10.10.10.25. Â Same issue - can see the server but not the databases on the server. Â You can see that in my third screen shot from my original question.
Regarding peer to peer, that DOES work. Â If open the databases on FMP on one of the desktops, and I go to another desktop, I can see the other desktop sharing the files. Â I can see the computer name and the databases. Â I'm not quite sure what that means.
Does my server have a proxy name? Â I'm not sure what that means - but that answer is no, I'm pretty sure. Â These machines are all on a typical Windows network.
The next thing I'm going to try is installing a Windows 2003 virtual server with FMS 9 on it and see if I can host the files there.
Databases
--
Questions
--
Followers
Top Experts
Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.