Set up

[bronwync]

A while ago (2004) someone posted the following message, there were a lot of responses, but no "eureka, I have it". I have exactly the same problem. I have fixed it by restarting the engine etc using the command line, and it works for a bit (an hour or so), but then it reverts again. This is not a lot of use. Does anyone know the definitive answer?

"Hi everyone,

I'm about to shoot myself just trying to install FileMaker Server 7 Advanced.

Here's my setup:

Xserve running OS X Server 10.3.5, fully updated. 2GHz G5, 2GB RAM.

Services running: AFP, Apache (completely default), and FIleMaker Server 7. That's it.

(FWIW, all appropriate ports open on our firewall.)

This Xserve is basically brand new. I've been running FileMaker Server forever, and upgraded to FIleMaker Server 7 about 2 months ago. Thus far it's been running great.

We're putting up a new web site that will require a bit of integration with FileMaker Server. So, I had to purchase the Advanced add-on.

FM Server 7 and the Advanced package are on the SAME machine.

Installed Advanced, and it didn't work - the Web Publishing Administration Console ('Admin Console' from now on) would not come up when I accessed http://localhost/fmi/config or http://127.0.0.1/fmi/config. Talked to FM tech support, after doign a bit of troubleshooting, a complete uninstall, manual removal of the Web Publishing folder, and a reinstall did the trick. I was then able to access the Admin Console.

I punched in an Identifier and Passcode on the FM Server Admin application ('Admin App' from now on), and on the Admin Console side of things, entered the FM Server address as 127.0.0.1 and entered the Identifier and Passcode.

This did not work at first. In the Admin Console, in the FileMaker Server tab, under Server Address, I get the mesage: "The specified FileMaker Server is not accepting the Publishing Engine connection. Check the server or specify an alternate server." And in the Published Databases tab, I get: "The specified FileMaker Server is not licensed for additional Publishing Engine connections. Check the FileMaker Server license or click here to specify an alternate server." (NOTE: I already updated the license number in the Admin App to reflect the Advanced add-on, and the Admin App does report Publishing Engines as Permitted. FM tech support ran the serial number and it does check out as an Advanced serial, so no prob there...)

So... a full restart of the machine.... and voila! Things seemed to be working! Publishing Engine talking to Server, Published Database section working...

...and a few minutes later, it stopped working. And it does this on all consecutive reboots. Same error messages as before, even though the Admin App is showing that there is a Web Admin Console on the machine (which it wasnt doing before).

So I'm very very stuck. FM tech support escalated the case, but I needed this working yesterday, and both tech support and I are totally out of ideas short of a full reinstall of everything including the OS - since the OS is COMPLETELY unmodified and there are NO services other than AFP and Apache and the FileMaker ones running, this seems totally unnecessary, and would knock my users out for much too long for a fix that may not even work. ANY HELP on this would be greatly appreciated - in all my years of server work I've never run into a problem as dead-end as this.

Random items:

- I have started, stopped, and restarted the Web Publishing Engine via Terminal numerous times with no luck.

- IIRC, Tech support mentioned that there should be two processes called FM Web Publishin [sic] running, but I only see one. I can't kick all my users off to reboot the machine and see if there are TWO running during the time that this whole thing DOES work, unfortunately.

- To reiterate, FM Server 7 and the Advanced package are on the SAME machine, and I'm telling the engine to refer to the FM Server with 127.0.0.1. I have tried to swap this with 'localhost' but that does not work.

- I'm accessing the Admin Console through http://127.0.0.1/fmi/config. I've tried logging in other ways (localhost instead of 127.0.0.1, remotely from another computer using it's internal IP, etc) but it has not made a difference.

- ALL PORTS that FileMaker, Apache, Tomcat, etc. use are fully open on our firewall.

MANY THANKS in advance to anyone that can help out!

"