Filemaker Server and IIS Grief

[Greg Hains]

Hi.

I am looking to work around a problem that I am having with FMS/IIS and Apache. Now I know that one is not supposed to run anything else alongside FMS, but the problem is IIS it would seem.

In my case, I have Apache hosting a few small websites on port 80. IIS also wants port 80. So I would like to achieve either of the following:

1. Either have FMS be able to use Apache for the IWP function (most ideal arrangement as I'm not keen on IIS really anyway) on port 80, or

2. Work out how I can use another port number under IIS for FMS. Problem with this though is that I am hosting several domains and websites and issue is that IIS doesnt do this well, if at all.

Now I know this covers several technologies that arent too relevant to this forum (ie IIS and Apache), but if I could get FMS/IWP to work under Apache I would be a happy man.

Anybody got anything that might help?

Cheers in advance.

Greg

[Wim Decorte]

#2

Every web server uses port 80 by default, but you can change that easily enough. In IIS it's in the web site's properties (just right-click on it).

[Greg Hains]

Hi Wim.

Im would prefer to leave my Apache running on port 80 so would need to change the IIS IWP port to something else. Does simply changing the default web site port number change the IWP port as well?

Greg

[Steven H. Blackwell]

IWP uses whatever port the web server uses. Of course, you'll need to change the CGI's that call IWP published databases to include the new port.

On Windows OS, Apache is not supported for IWP or any other type of CWP.

Steven

[Greg Hains]

Hi Steven.

Thankyou four your response as I have decided not to give up on this pursuit.

I have configured IIS to use port 81 and I can load a web page through a browser though that port -or whatever port I set it at - so I know that bit works OK. What I do find curious is that Im unable to telnet (127.0.0.1 81) into it as I can any other web server. IWP reports much the same, that the test failed.

I dont want to turn this into an IIS question, but if a browser can access a page, why can FMSA not? And the Telnet thing bothers me too.

If FMSA supported Apache, life would be soooo much easier.

Greg

[Wim Decorte]

Can you post the URL you're using for IWP?

Since you now have IIS running on a non-standard port you have to include the port in all URLs:

http://theWebServer:81/fmi/iwp

Also: why would you expect telnet to listen on port 81? That doesn't make sense, telnet has its own port. 23 is the default telnet port.

When in doubt, use this list:

http://www.iana.org/assignments/port-numbers

[Greg Hains]

Hi Wim.

Thank you for your reply - I appreciate your help.

I know that its possible to Telnet into any port service and get a response provides you give it the right information as the service will respond. eg "telnet 127.0.0.1 80" - I use this method all the time. I only used this here as a diagnostic tool to see if IIS was even responding. The web page says it is, but FMSA seems to think not.

I dont even get as far as using the URL to access an IWP page as the Server Deployment process fails. I get:

Testing Web Server...

Return Code = false

But I would be using http://thewebserver/fmi/iwp:81

Im curious as to why you have the port number half way through the address - Ive not seen it done that way before.

Cheers,

Greg

[Wim Decorte]

But I would be using http://thewebserver/fmi/iwp:81

Im curious as to why you have the port number half way through the address - Ive not seen it done that way before.

The anatomy of the URL is:

- webserver: IP address or DNS name of your web server

- port that the web server listens on

- "/fmi/iwp" is the signal to the webserver to pass the request on to the fms web server tool that gets installed on your IIS. The web server tool will then work with the FMS web publishing engine who will in turn communicate with the FMS database engine

Your URL: http://thewebserver/fmi/iwp:81

would still hit "thewebserver" on port 80 since no port is specified immediately following the web server and you'd be asking the FMS web server tool to interpret the "iwp:81" command which is meaningless to it.

[Wim Decorte]

I dont even get as far as using the URL to access an IWP page as the Server Deployment process fails. I get:

Testing Web Server...

Return Code = false

You hadn't indicated before that this is where you're stuck. Have a look at the FMS readme, it explains how the IIS authentication needs to be set up. If it doesn't allow for anonymous then you'll see what you're seeing.

Also: do you have more than just the "default web site" running in IIS?

[snitting]

Hi guys,

sorry to barge in on your discussion :

I'm experiencing the exact same problem described in the last post by Greg (Testing Web Server...

Return Code = false), and I do have "anonymous" enabled in the IIS authentication. There must be at least one additional problem somewhere...

Cheers

[Greg Hains]

Hi Wim,

I have removed Apache from the server and am using stock-standard IIS6 on port 80. Without FMSA loaded, IIS appears to work fine. I then install FMSA 11 onto the box and whilst it seems to host files in Pro mode OK, whenever I try to use IWP, the WWWP service sticks in Starting status, and FMSA is unable to communicate with it.

I have spent dozens of hours (no exaggeration), pulled out my remaining grey hair in an effort to locate the problem.

Suggestions made that I have followed:

- Check all Service Packs on W2K 2003 are up to date.

- Removing FMSA, registry entries, and remaining files - ready for clean install.

- Checking security on Internet User account (although referenced instructions don't exactly align with what I have here, so this is a weak point)

- Reinstalling FMSA clean, and only having IWP loaded for database deployment

- Reloading W2K3 completely fresh.

- Holding my mouth right and becoming religious

The one extra thing that was suggested (but most people said didn't help) that I didn't try, was having the NIC disabled (or no connection to Internet when installing FMSA), but as my server is 3000km away and I remote into it, doing this will lock me out.

I was using FMS10 when I first wrote this topic, and upgraded to FMSA11 hoping it may help. I think the problem lays with IIS or Windows, but speak tho them and they advise if it works with FMS then the problem IS FMS - you know how it goes.

Judging by the many people having reported this (all the way back down to FMS8), then this is not a new problem.

Filemaker themselves (althought friendly and helpful - genuinely) say that everything Ive tried should do the trick.

Any comments please.

Cheers,

Greg

Edited May 23, 2010 by Guest