Can't stop web publishing engine

[Nephron]

Hi gang,

Two related problems have sprung up for us. FM Server Advance 7, on an XServe with OS X server 10.3.8.

First, we noticed that we could not reboot our server remotely, it would hang and never complete the reboot cycle. Someone from the datacentre would have to go and manually reboot.

Second, when I tried to put on the v7.3 patch for the Web Publishing Engine, the updated kept saying that it could not install because the web publishing engine was running. OK, used the Server Admin program to stop the FM Server, used my web browser to administer the server, turned off web publishing. Still couldn't install the patch, web publishing engine still running. Finally I had to Force Quit manually the two processes running under the fmweb user. Now I could install the patch. Putting the two together, I tried an experiment. As long as I Force Quit the fmweb processes, the server reboots fine. If I don't Force Quit, no reboot, hung server, needs manual restart.

Any ideas what has gone wrong with my Web Publishing Engine? Why can't I get it to stop?

Cheers!

[Martin Brändle]

It's probably a root process that was started on system startup.

The FMS7A Web Install Guide on page 52 states:

To stop the Web Publishing Engine and Administration Console, enter [in the Terminal]:

sudo SystemStarter stop "FileMaker Web Publishing"

To start the Web Publishing Engine and Administration Console, enter:

sudo SystemStarter start "FileMaker Web Publishing"

To restart the Web Publishing Engine and Administration Console, enter:

sudo SystemStarter restart "FileMaker Web Publishing"

[Nephron]

Thanks Martin,

Good find. The next page mentions why the web publisher kept restarting after each reboot. This is very helpful, but I am still a bit worried about why this service won't stop on it's own. Is anyone else having this issue?

Thanks for your speedy and helpful reply, Martin.

Cheers!

[deepdream]

That's weird Nephron, because it behaves the same way a lot of times on our Win2K servers. I couldn't install the v3 updates because I couldn't stop the WPE nor the FMSA services. Had to reboot manually, stop them before any client login or WPE admin login, and then I could install the update.

Sorry, that's not help.