Jump to content
Answers

Filemaker Install/Port 443 not Open error

Recommended Posts

We have had Filemaker 15 Server up and running of while but when we originally  installed it was installed on port 444 (because of our router configuration). We wanted to reinstall using port 443. So I uninstalled per instructions, uninstalling, bonjour, microsoft items, java etc... Rebooted our Windows Server 2012. Ran installer and got the error message the port 443 was not open. Rand netstat -a -o from command prompt, it said Filemaker 14/ on port 443 was listening (PID 768 and 4), So used skill to kill the PID. Rebooted, still unable to install Filemaker 15, port not open.

Then went  into diagnostic mode, started the installer service. Installed successfully but then could not launch Filemaker server, could not even change firewall settings. So now we are restoring the server to the image backup. 

Would like to uninstall and reinstall again tomorrow using port 443, any hints or tips on what to check before an uninstall and reinstall.

Any help would be greatly appreciated. I would call FM tech support but they are not available on the weekends.

 

 

Share this post


Link to post
Share on other sites

Your basic troubleshooting is correct: find out what is occupying port 443 and 80 and work around that.

However: it is not normal that immediately after a reboot it would report that FM14 (not FMS) would be open.  That does not make sense and is something that definitely needs to be looked at.  Is FMP installed on that machine?  If so, get rid of it.  This machine is not used as a TS box, is it?

One thing in your set up routine: after uninstalling all the components and before the reboot: delete or rename the "filemaker server' folder that is left in Program files.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By dataclip
      We have a couple of servers running on AWS. As of the middle of last week we suddenly are having connection problems. The server logs mostly lists error 10, sometimes error 51. These customers have poor internet connection, so we have set up a server and a client in the cloud. The users connects to the client through an RDP session. It is a Windows enviroment with one customer using Windows server 12 and FMS 14, the other Windows server 16 and FMS15. We use a seperate AD server to control the RDP access and accounts to the FMP server, clients have no acces to the FMS server.
      I have read previous posts on this issue. I do not think there can be any hardware issue, since the server is hosted with Amazon and both server and client are on an internal network. To be sure I have filed a support request with Amazon as well.
      The strange thing is that the error message sometimes occurs within a minute and then FMP freezes on the user while they are still working in the FM app. It is my understanding that error 10 occurs if the client does not respond to the server ping for 2 pings, so time out for this error should be 125 seconds. 
       

       
      These servers have been running without this issue for a long time now. Any idea why this has suddenly changed and why the error message errors while tghe users is using the FM app?
       
    • By mr_mike
      I'm looking for both guidance and software to assist in FileMaker Change Control.  With over a 100 deployed solutions across multiple servers the process change management from dev > test > production is very labor intensive.  BaseElements helps a lot but it is only one part of the puzzle.  Porting the data from production > test across these solutions and then doing UAT and QA is again, labor intensive.
      How are others handling this?  Is there some software or process documents I'm missing?  I'd welcome any input to this topic.
      Mike
    • By theusualsuspect
      I'm wrapping my head around the Standby Server feature, and there's only one aspect that I can't figure out. I use Webdirect, so I'm forwarding port 80 to the internal ip address assigned to my primary server. If that were to go down, my standby server would take over - but it's assigned a different ip address - so my router's port forwarding rules will still be pointing to the ip address of the primary server. Is this accurate? If so, is there a way around this?
    • By cbum
      For security reasons, my institution is requiring me to migrate my FMS15 solution, currently residing on a MacPro in my office, to the IT data center. Since they do not run MacOS, this includes a migration to a hosted windows server running FMS advanced. I no nothing about windows (eg: what is a hosted win server vs simple win server ???) , so I will be totally dependent on the IT staff knowing what they are doing (and they barely know FM, I narrowly escaped having them try to recreate the solution in Access for $$$$$ ...):
      Current Environment
      ·      FileMaker Server Advanced running on local Mac OS12.12 system.
      ·      RAID-0, Solid State Drives
      ·      8-Core CPU
      ·      32gb RAM
      ·      FileMaker DB is 100gb with additional storage required for temporary files and local DB backups
      Proposed Environment
      ·      Hosted Windows Server running FileMaker Server Advanced
      ·      4-CPU
      ·      16gb RAM
      ·      1tb Storage
       
      I have many questions/concerns, but would appreciate feedback on 2 issues:
      1. Backups: My understanding is that FM is adamant that no backup system can touch a “live” database file, causing potential corruption. FMS has its own internal backup mechanism, and you point it to some external drive / directory etc, where it creates backups that can then be copied/archived by a system process or third party backup system.
      The IT manager I am discussing this with replied the following: "Backups should not be an issue either. We've been using this model on our SQL servers and have not experienced a single issue over many years. They do their backups and we do our own as well."
       
      I don't know what the windows server system is doing for backups, but are the FM warnings about letting other backup systems touch live FM files only for 3rd party SW, and system processes are OK? Any specifics I should communicate to the IT guys? Again, I know nothing about how win or win/server does this.
       
      2. Performance:  I am obviously worried performance will take a hit, if only from networking.
      I am hosting a dozen related files ranging from 1-50 GB, typically 5-10 concurrent local and remote users.
      The proposed environment seems less optimized for DB performance - what are the key parameters I should negotiate on? My current 32gb RAM may well be more than what is needed (I don't use any web or go functions, just straight FM clients), but can I determine from the admin console logs/stats how much is really needed? My request for SSDs was immediately shot down, how much can I get from various RAID configs they may or may not agree to?
       
      Thanks for any feedback - I am so not looking forward to this...
       
    • By vincenzo
      Hello, 
      I have a filemaker server 15 advanced running on windows server 2008r2 in a local LAN network. I want to connect to server with client (filemaker 15 pro). Everything work well in the local LAN but I am unable to access to the database outside the office using internet connection and IP. I just have made the port forwarding setup (5003 and 16000) but no results. Maybe the Windows server need to be opened in some service or funcionality?
      Before of the server I had a simepl windows XP pc running filemaker server 5.5 and it work well also outside the lan.
      Thank you
×

Important Information

By using this site, you agree to our Terms of Use.