I switched IIS off and ran Netstat to see what else was running and what ports are open. I can verify that nothing is running on 80 or 443 and that the machine is listening on port 80 but not 443. There is no SSL installed on this server.
It turns out that Filemaker 13 is written by folks who don’t know how to handle Windows beyond version 7. Windows 7, 8, 8.1, Server 2012 and 2012R2 all have system service called http.sys that listens on port 80. That makes it impossible to run applications and services that haven't been integrated with this feature to also listen on port 80, like IIS, Apache and so on. Disabling http.sys only works if you are sure you don’t have any use for Windows applications that do know about http.sys. However, as every system nowadays has both an ipv4 and an ipv6 address I bound http.sys to the ipv6 general address to free up the local general ipv4 address and this allowed me to overcome the problem.
FMS does not try to use port 80 at all. FMS does install some components for IIS.
Whatever you did seems to have sold your issue, but the underlying reasoning does not seem correct.
Thank you, I was indeed somewhat premature in thinking the problem was resolved. The issue displayed in the screenshot above was overcome allowing FMS to install, but later when running the deployment assistant it halted at the test stage.
Now the reason for the halt is clear. It is using localhost which now corresponds to ::1: but tests for the xml file on 127.0.0.1 on PORT 80.
So, whilst you are correct that the changes I made may well have overcome the initial problem they are not in fact the answer. However, you may be mistaken in thinking that port 80 is not used by FMS because all my errors indicate to the contrary. FMS should run under IIS but if you refer to the initial post you will see that this led in a perpetual loop and the only service using port 80 was as described.
IIS is running and shows the Filemaker Database Server Website splash screen but as matters stand the test.xml file connection is being refused. As I say I know the reason this is because FMS is attempting using a IPv4 address whereas localhost is using the IPV6 address.
I undid my earlier bodge and finally managed to complete the installation. Although now successfully installed the question remains.
Why did FMS get caught in a loop during the initial installation reporting that ports 80 and 443 had to be available, clicking the disable option failed etc. as initially described?
Here are some notes to assist others similarly affected:
This was a fresh install of Windows Server 2012 Standard edition (note it was not R2) with very few roles and features activated. IIS had been added and proven to be working. The Firewall was amended to accommodate FM ports. The default site (the only site) had been disabled. If I emnabled it Filemaker did successfully disable yet still came back reporting an the port 80/443 problem.
Netdiag proved that the only service running had PID 4 (System) which I traced to be http.sys. Altering the IPV4 and IPV6 configurations overcame the obstacle because in effect port 80 was not free. Having got most of the way through the install I altered the IP settings back to original and then finished the install.
Can I please ask, because of exactly the same problem how did you "Altering the IPV4 and IPV6 configurations" to overcome the obsticle.
This is going back a while and in the intervening period I have installed many FMS13's without the same problem. I think that what was different on this server was the two network cards; internal and external. The Internal Card was set up to use both IPV4 and IPV6 addresses whereas the External was purely IPV4.
In subsequant installations I have ensured that only one Network card was present during the installation and that it only used IPv4. Post installation I added the additional cards and IPV6 settings where used.
If that does not help then please tell me what is going wrong for you and I'll try to assist.
Thanks for the quick reply and I will have a look at your suggestion.
This is a remote installation which makes it a little harder, my first problem of this kind as well.
I'll let you know how I go.
I was also installing remotely when i ran into this problem and when I stop to think about it I'm fairly sure that subsequant installations have either been in frontof the machine or by logging into a host server and setting up a new virtual server onto which Filemaker server was installed.
Your problems should disappear after doing this:
First, uninstall these components from the Control Panel:
a. FileMaker Server 13
c. All installed versions of Java
d. Microsoft Visual C++ 2012 Redistributable (if you see earlier versions of this, don't worry about those)
e. The four parts of the Application Request Routing application (if you don't see all four parts, remove what's there):
--Microsoft Application Request Routing 2.5 or 3.0 (either one)
--IIS URL Rewrite Module 2
--Microsoft External Cache Version 1 for IIS 7
--Microsoft Web Farm Framework
Stop all services that port 80 and 443 that are using or listening (this was a problem) Typically they're easily found by doing netstat -a
Then reinstall from a full installer.
I'm not so sure about all that devonell has said, it seems a bit excessive to me, but his remark about Port 80 reminded me that http.sys was listening on port 80 and I'm sure that is what was causing the error I had.