Or perhaps there is something wrong with our server that it's blocking that port. Perhaps this is because Filemaker hasn't even gotten to the point of being able to transmit through that port I don't know. Attempting to telnet to port 16000 on the server gives an error: "Could not open connection to the host, on port 16000: Connect failed". We tried turning off Windows Firewall and uninstalling Symantec protection. Then we get an error that says "The Filemaker Server Admin Console Start page is not available." It says "Please wait while the Admin Server starts". After installation (or perhaps as part of the installation), internet explorer opens a window which tries to establish a connection to Filemaker's local admin console. In order to upgrade, the instructions say to uninstall Filemaker 11 and do a clean install of 12. We are trying to install Filemaker Server 12 on a machine running Windows Server 2008 R2 Standard, Service Pack 1.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |