Claris has terminated the Admin API of FMS17 which means that this tool does not work as of September 27th, 2019. Please upgrade your FileMaker server to version 18 and download The Missing Admin Tool 18 from this site.
FileMaker, Inc. has just released the FileMaker 17 platform.
While we are excited about some of the new great features, the FileMaker 17 Server now features a new web admin console, that looks like the FileMaker Cloud Admin Console.
While the web console is nice looking, it lacks several features, that can be vitale in order to manage your FileMaker server.
Most features are not completely gone, but now you will need to use Command Line commands or use the new Admin REST API. For many Server admins, this new way of managing FileMaker Server, might be difficult to master all these interfaces.
In order to help our colleagues, we built this tool, that combines all the interfaces you will need in order to manage your FileMaker Server 17.
When you install FileMaker Server 17, you will need to install a Custom SSL Certificate. Unfortunately, the web admin console will no longer have a feature to generate a Certificate Signing Request, which you need in order to purchase your custom SSL certificate. In order to do so, you will need to do this via CLI commands.
The FMS 17 Missing Admin Tool has a feature to generate this command, so the process will be easier.
We also include a lot of information and links to videos, we’ve done with Richard Carlton in the past, in order to help you through this process.
The tool is completely free and completely unlocked, so you can dig in and learn from the code.
The only thing we ask of you, is your name and email address so we can send you an email, when we publish new helpful tools and articles.
If you like this tool, please let us know and let your colleagues know.
PLEASE NOTE THAT THE ADMIN API WILL CEASE WORKING ON SEPTEMBER 27, 2019.
THIS IS AN EXPIRATION SET BY FILEMAKER INC. IN THE FILEMAKER SERVER 17.
AFTER THIS DATE, THE FUNCTIONALITY OF THIS TOOL, THAT USES THE ADMIN API, WILL ALSO CEASE WORKING.
HOWEVER, THE OTHER PARTS WILL STILL FUNCTION AFTER THIS DAY.
This is why I love the FM community because of developers like yourself who share awesome developer tools and personally have saved this fellow developer tons of time so I can focus on developing great stuff for my Filemaker clients which is how I make my living.
Thank you this is awesome!
Get this error trying to download
Error establishing a database connection
Yeah, sorry. The server is a bit overloaded currently and it looks like I need to do a reboot.
Please try again later – the link should still work…
Hej Claus, good work! Had a very short look and appreciate the work you put down.
Still, I believe this is something that should be integrated into the basic admin console provided by FM.
Besides I do see security and performance issues. (Either putting a client on the server or opening the console and admin api to the world). And then, FM will report e.g. PHP as running even though it is not running, just experienced yesterday… We will certainly talk about it in Berlin or at Devcon. Regards from summerly warm Finland, Volker
Thanks for your kind words.
We can agree that it tools to manage FMS17 is scattered into several places. That’s why I created this tool, so at least you have a single tool, that combines all “admin interfaces”.
We also need to bear in mind, that the new web admin console for FMS17 is a v1. I am sure FMI will get feedback on this…
See you soon !
Thanks for this wonderful tool, Claus! This will save developers a lot of time and get them up to speed much faster. Kudos to Richard Carlton for the videos, too.
And thanks for spreading the word, so we can help our colleagues.
I have not tested this tool yet. Need to install the server first.
For what I can see from the screenshot it is all I always wanted to have over the years.
Having to constantly look for CLI commands, certificates storage and all other bits was always a pain.
Thank you so much as I believe it will do a fantastic job. Greg
I saw the demo of “FMS 17 Missing Admin Tool” as part of Richard Carlton’s FileMaker 17 training videos. All I can say is “Wow”! What a gift! Thank you!
I am not able to “log in” after I enter the Hostname, username/password. I am getting “Something went wrong connecting to the API: 1631”
NOTE: My username has spaces in it. Is that causing the HTTP/1.1 400 Bad Request?
admin REST API does not support the same password characters as the web admin console.
I’m pretty sure the you need to change your password and avoid spaces.
Currently, I can not give you precise information on which characters is allowed and which is not.
But try to create a password without spaces and with regular characters and numbers and it should work.
Thanks for your interest in the tool.
Having the same problem as Klaus. Username has spaces in it. Password does not.
I’ve put in 4 different emails but it doesn’t seem to have worked for me. Sounds like a tremendous tool that I’d love to have. Thanks for your generosity.
We’ve had some issues, which is now resolved, so please try again.
I’ve tried on 2 occassions to get the download link for the “Missing Admin Tool” and each time I have not received an email with the link. please advise if there is a problem.
We’ve had some issues, which is now resolved, so please try again.
Great tool! Thank you. I am in the process of creating my certificate request and paste the info into Terminal. It appears to be processed. Where is the file located? Should it appear in the field of the Utility or do I need to copy and paste? If so, where is the Private Key File located on Mac High Sierra? Thanks!
Please disregard my previous question. I missed your excellent Help on the SSL Info tab!
Claus, I tried the tool today and I must say that it works really nicel Thanks for creating this wonderful masterpiece!
I found a little bug which made the tool unable to open or close a database file. The Admin API docs state that a header of ‘Content-Length: 0’ is required if the request has no parameters. I resolved the issue by editing the script ‘API || File Actions’ on line 40 by setting the content of the $curl variable to: “-X PUT ” &
“-H \”Authorization: Bearer ” & $$token & “\” ” &
Case ( $function = “open” or $function = “close” ; “-H \”Content-Length: 0\” ” ; “” ) &
“-H \”Content-type: application/json\” ” &
If ( $function = “openEncrypted” ; “-d ” & $data ; “” ) &
” -D $ResponseHeaders –show-error” (I aded a header Content-Length in case of an open or close request)
Thanks for trying out this tool and to provide feedback.
I am aware of the recommended -H “Content-Length: 0” but in my testings it was not required to make these commands work.
However, I appreciate your feedback as it might be helpful to others as well.
Thanks for doing this! FileMaker really dropped the ball on this. We all purchase FileMaker because its designed to be easy and what FileMaker did does not make things easier.
I am not clear on how to run the tool. Can I install it on my FMS 17 and run it from my host computer? My FMS server does not have FM 17 installed on it. I am also getting the API: 1631 error when I try to login using the REST API, even before it asks me for the FMS credentials. My FMserver username has a space in it, but my FMserver password does not. I appreciate your assistance and can’t wait to start using your tool.
Hi Ben and thanks for your interest.
You open the tool in your local copy of FMPA17.
Make sure you can open the admin console of your FMS17 in a webbrowser on your local computer.
On the first screen, you enter the FQDN of your FMS17 and the credentials.
If you get a 1631 error, when you try to connect via the admin API, this can be an indication that you need to change your password for the root user of the FMS17 admin console. As others write above, the password needs to be alphanumeric with no spaces. Even if you can set a password in the web admin console of FMS17 with special characters, such is not supported via the admin REST API.
Hope this helps.
UPDATE: I solved the problem. I ran it from my regular computer and used the local IP address of the FM server (192.168…) as the hostname, and it connected.
Thanks so much for doing this. I wonder how you make living doing all this stuff for free 🙂
But, if you have few minutes, a really great addition would be easy access to the log files. Debugging server-side scripts is quite tedious sometimes. A tool to capture and display the log entries generated in the interval a specific script is run would be very, very handy 🙂
Glad you like the tool.
Log entries is another big thing missing from the FAC. The ability to watch log entries is essential for server admins.
We have created FMS WhistleBlower as a kind of response to this need, along with so many other needs.
Recently we release a BETA with known bugs.
Since we release it for free to the community, it also means that it gets low priority over customer projects.
That’s the reason it took us 2 years to release the first BETA, although we have been using it internally for 18 months.
An addition to FMS Missing Admin Console, that could give you log entries is not a small task. So I will not add such feature to a free tool. Time simply doesn’t allow that.
Hi – I appreciate the work that went into this tool and your offering it to the community for free. I’m using it with FMS server on the same machine, and have been able to login to the REST API. It correctly reports all the status info, databases, status etc. However, when I try to close a database, the database icon turns blue temporarily and then goes back to green, and the database never closes. Closing it from the web admin interface works fine and your tool then reports the db as closed, but I can’t use the tool to actually close it. Exact same situation for opening a closed database.
Thanks for any suggestions.
Thank you for your interest in this tool.
Please look at Jeroen’s comment above. He suggest to put Content-Length: 0 in the header for the open/close commands.
As I write, in my tests while making the tool, this was not needed on the 3 machines, I tested with, but that might be needed for you.
Hi Claus – thank you. I tried replacing the $Curl variable in line 40 with the suggested value, but unfortunately it didn’t make any difference.
Any other thoughts?
I don’t have any other tips right now. I’m really busy preparing for DevCon and I will need to debug the code, in order to find the issue.
That being said, the tool should work. A lot of people have downloaded it and have it working.
No worries, totally understand. I can just open the databases from the web admin panel of course.
I’m trying to generate the certificate request. I’ve changed my FM server admin password so that it is just numbers and letters. Everything looks to be in order. I copied the terminal command, and pasted it into the Terminal (I tried this both on my computer, and the server itself using Remote Desktop). After pasting the command, and hitting enter, it asks for the admin password. I put in the password, and yes, I’m certain it is the correct password for that computer, it gives me this error:
fmsadmin: Permission denied.
Error: 9 (Access denied).
Any thoughts on what I’m missing?
The SUDO command requires your computer password. I sounds like you have used your FileMaker Server password in the command line prompt.
Rick, did you ever get this figured out? I’ve done a number of installs of FMS 17 so far and have only now just run into this issue, installing on a new Mac Mini running High Sierra with nothing but FMS and FMPA installed. I can open the Admin Console using the Username/pw entered during the install process but running almost anything from the command line generates the Permission denied Error: 9 response.
I’ve tried without sudo using the FMS credentials and with sudo using the Mac Account credentials. The only command that seems to run without this error is fmsadmin restart admin server and fmsadmin -v (Version number).
just installed you tool, pretty exciting. I have an issue though: when I click on the Web Admin Console Tab. . . I get nothing displayed and no error message.
FMS 17 is installed on my computer, it’s a dev server. The computer is an iMac running Sierra. I ca open the server console without any issue. Is there something I am doing wrong ?
On the REST admin console I have set ServerName to the name of my computer and de Hostname to 127.0.0.1 – I also tried localhost that didn’t work either.
That’s the problem. You need to setup a FQDN for your server and you should also install a custom SSL certificate.
FQDN = Fully Qualified Domain Name.
Things will not work correctly, until you setup and use FQDN.
Please watch some of the other videos on this site, where we try to explain this topic.
the FMS Server is only accessible from inside the office, there is no way to access it through Internet. Then we don’t need SSL protection. Is there some way to use the included Self Signed Certificate ?
No. There is 2 modes for FMS17; Encrypted WITH Custom SSL Certificate or NOT encrypted with no certificate. So no way to use self signed certificates. If you turn off SSL, you can manage your server via the web admin console, but the admin REST API requires custom certificate and SSL.
It really doesn’t matter if your server is only on a closed LAN. It is built to be secure and require SSL with Custom certificate. So you should always install a custom certificate and turn on SSL.
Thank you for making your tool publicly available. I was wondering if per chance the tool included the ability to turn on or configure notification for completed backups?
The article above alludes to the fact you can only do this now via the API.
We are moving to FMS 17 this evening and I have only just become aware that this function has gone from the admin console interface and I really need to enable this somehow.
I had a quick look after I downloaded the tool but cannot see it in the great wealth of options you have included.
Any advice appreciated.
I get this error even though I have FM 17 advanced
“DM_FMS17_TheMissingAdminTool.fmp12” was created by version 17.0 of FileMaker and cannot be opened by this version.
Use version 17.0 to view this file.
Please make sure you are in fact trying to open the file in FMPA17.
Double click can make it open in FMPA16
This is really a great tool, thanks very much!
However I ran into a problem I cannot solve.
I used your tool to start the php service and everything seemed fine.
But I couldn’t open a php page in my browser.
After restarting my Mac (Mojave) no change.
Restarting FMS via the terminal gave the following message:
========== graceful ==========
ma 8 okt 2018 11:10:23 CEST
/usr/sbin/httpd -k graceful -D FILEMAKER -f /Library/FileMaker Server/HTTPServer/conf/httpd.conf
httpd: Syntax error on line 495 of /Library/FileMaker Server/HTTPServer/conf/httpd.conf: Syntax error on line 9 of /Library/FileMaker Server/Web Publishing/publishing-engine/php/sierra/httpd.fmi.conf.php: Cannot load /Library/FileMaker Server/Web Publishing/publishing-engine/php/sierra/libphp5.so into server: dlopen(/Library/FileMaker Server/Web Publishing/publishing-engine/php/sierra/libphp5.so, 10): no suitable image found. Did find:\n\t/Library/FileMaker Server/Web Publishing/publishing-engine/php/sierra/libphp5.so: code signature in (/Library/FileMaker Server/Web Publishing/publishing-engine/php/sierra/libphp5.so) not valid for use in process using Library Validation: mapping process is a platform binary, but mapped file is not\n\t/Library/FileMaker Server/Web Publishing/publishing-engine/php/sierra/libphp5.so: stat() failed with errno=22
exit code 1
And, trying with your tool to login to the server I get this message:
Something went wrong connecting to the API: 1631
Thanks for the interest in our free tool.
It sounds like you did not install PHP with your FMS17 installer – or at least it didn’t get installed correctly.
I would recommend that you un-install FMS17 (make sure to backup your files first), make sure to trash the entire FileMaker Server folder (/Library/FileMaker Server) after the un-install. And then re-install. Make sure to check the installation of the PHP library, that is provided with FMS17. (and yes, it is an older version of PHP, but PHP is going away from FMS, so they are not going to spend much time on this in the future)
The error message you posted indicate that php library, provided by the FMS installer is either not installed at all, or the configuration is not correct. Either way, a re-install, should help.
The API error of 1631 is unrelated. This is a connection error to the admin API. This process is running through the nodeJS server and not dependent on Apache. Most likely you either entered a wrong username/password or you have a password with spaces or special characters. Even if you are able to log into the FAC with these credentials, the admin API does not support all characters. So you could try changing your password to be alphanumeric.
Hope this helps.
Many thanks for your answer. I will take the steps you indicated and will let you know the results.
Right now the webserver and admin console don’t work at all anymore.
Yes I have a ‘&’ in my password. Never had any trouble with that before.
Do you mean that we will not be able to work with PHP in the future?
In the future, FileMaker will pull the FM PHP API from the FileMaker Server.
When that will happen, no one will know for sure right now. But it will happen and FileMaker have told us to start moving from using the PHP API to using the data REST API.
Hi Claus, thanks for your answer.
I did all you suggested, removed the ‘&’ out of the admin password, activated PHP, restarted mac, but it resulted in no different behaviour at all.
During installation there was no mention of PHP installing.
I really don’t understand what’s going wrong
I haven’t installed FMS17 in the last couple of weeks, but as far as I remember, you still get the options to install PHP and XML during installation. My experience is that you should install everything from the start, even if you don’t want to use it. Then you can always turn it off afterwards.
I went back to a clean install of Sierra and a clean install of FMS 17.
Choosing the FM PHP gave again a webserver crash. Choosing the system PHP doesn’t give a crash, however PHP pages still don’t show.
Sounds like you have installation issues, which you should contact FMI support to get help with.
Well, last update of Sierra did the trick.
FileMaker changed to the use of the FileMaker PHP.
Thanks for your support!
this is just to congratulate you to a fantastic tool and your attitude.
Just saved my day
Thank you very much for sharing this wonderfully useful tool with the community. I kept getting the 1631 error – I tried changing the admin password a couple of times. In the end I got it to work but it seems like the FM Admin API does not like passwords that start with a number. Maybe? I can’t find any documentation about the admin password. Is there a specification for the password? My advice you get a 1631 error try a short simple password, just letters, to test, then you can go back to a secure password when it’s working.
Thanks for your feedback.
Indeed, we need better documentation from FMI, but we also have to acknowledge that the admin REST API is currently in beta.
I can confirm this and it was my issue as well. Password was 28holmes18.
// error 1631
“password” : 28,
“username” : “simon”
“password” : “holmes18”,
“username” : “simon”
Thank you Michael.
Essentially, this comes down to the FM JSON functions, that override the type setting. So e.g. in this case, the JSON function thinks your password is a number and then it formats the password as a number. However, the admin API expects a string.
I should have accounted for that in the tool, but clearly this was an oversight.
However, you can easily fix this yourself by adding Quote() function around the password field in the login code. Then it will always be treated as a string.
I don’t seem to be able to open the database
Am I doing something wrong?
Username and password is admin
Correction for Login script:
JSONSetElement ( $json ;
[ “username” ; INT_Interface::Username ; JSONString ] ;
[ “password” ; INT_Interface::Password ; JSONString ]
The quotes for JSONString must be removed to make it work with passwords which are only numbers.
I think the quotes around JSONString must always be removed.
Login succeeded after I made this little patch in the login script.
You are absolutely right !
This is an embarrassing bug, I made.
Old habits with always putting strings in quotes – and FileMaker is not complaining nor is it handling the JSON Type.
Fortunately, this is easy to fix, since you all have access to the code, so you can just remove the quotes around the JSON types. Only a few places, mainly in the login script.
Thanks for pointing this out here.
I really love this tool! I decided to test it with a server setup I have here with about 35 files.
I am quite frustrated with the 17 admin console interface, as I cannot easily open/close files that are in a folder (I have a dev and a production folder). You obtain that data in the file list, so I plan to make a portal filter that allows me to make folder selections.
I also cannot see who’s logged into which file using which credentials.
So my plan is to expand on your development and add a user interface for that. I think I have to parse out the “guestFiles” nodes, and make records from them. They contains accountNames and privsetNames, that’s exactly what I need.
One could argue that this is a waste of time, as FileMaker will possibly improve their admin console. But it seems like they are perfectly happy with what they offer right now, and I cannot wait any longer.
Peter, as always, you are a brilliant mind!
Yes, this tool gives you the basics, but I left it completely open for you to expand on and to learn from the code (though you are one of the most skilled developers, so there’s hardly anything you can learn from me)
Unfortunately, I think it will take a while… for FMI to get their FAC up to the functional level of FMS16 Admin Console. Their strategy seems to be that with the REST API and CLI commands, we can build the tools ourself, if we are not happy with FAC…
Don’t overestimate my brilliance, I’m just a regular guy, who likes to stand on the shoulders of giants, like Todd Geist, who is really saving me a lot of time with projects like this. I use his “JSON Generator”. Now that is a briiliant tool, that is splitting up the returned JSON into tables and scripts.
Allthough the virtual list technique is awesome, I feel it’s somewhat slow for a lot of files. So I will take an approach where the JSON reply will be parsed in stored records (hence Generator). I plan to use it single user/local, avoiding multi-user issues.
Isn’t it great, that you can just combine and modify to your likes ?
Thanks to taking the tool for a spin and use it – and for your contributions to the community.
Amazing File. Thank you Claus. I am noticing a bug, I can seem start/pause/stop files using your GUI interface. everything clicks, but the status doesnt change on the server.
I can’t recreate this.
However, if you read the above comments, there is a bug in the tool. Look in the scripts and look for places where there is a JSONsetElement () function. The JSON types are wrapped in quotes, which they shouldn’t be. Just remove the quotes and everything should work fine.