The powers that be restart their Windows Server 2003 machine once a
week.

I experienced reboot with FMS running, reboot with databases closed
beforehand, and reboot with databases closed and database server stopped
beforehand.

In all cases (not after every reboot, though), the database server
doesn't start after the reboot, and it can't be started from the admin
console.

FM Service can't be stopped or restarted. A 2nd reboot usually fixes the
problem (not the most popular approach, though).

The admin found out that using taskkill on the processes
- fmservicewrapper
- fmserver

makes it possible to restart FM Service without rebooting the machine.

Any suggestions?

--
http://clk.ch

Perhaps the reboot is not a complete off/on reboot? Maybe the processes
aren't killed. (like with a re-login process)
You can check this by not starting FM after the reboot and then checking if
these processes are killed.

Do you restart FM manually? If not: perhaps the process becomes active to
soon within the upstart chain? I had a similar problem once which I
'solved' with a batch file delaying FM by 30 seconds.

You could lecture your powers that be about the need for continuity. Server
could run without restarting easily. It is made for it. I see no gain in
restarting every week.

--
Keep well / Hou je goed

Ursus


"Christoph Kaufmann" <clk (AT) tele2 (DOT) ch> schreef in bericht
news:1jo1ekv.zv22ntc6bbcqN%clk (AT) tele2 (DOT) ch...

Ursus <ursus.kirk (AT) ziggo (DOT) nl> wrote:

They say it's just precaution.

A batch file that start's Filemaker Service? How do you kick it off?
--
http://clk.ch

Precaution for what exactly?

I had to search a bit for that info.
Can't find the original anymore but I seem to remember I used the sc.exe
tool from the resource kit to create a script.

--
Keep well / Hou je goed

Ursus

"Christoph Kaufmann" <clk (AT) tele2 (DOT) ch> schreef in bericht
news:1jo3cw1.13pqg5j8o2nguN%clk (AT) tele2 (DOT) ch...

On 2010-08-31 04:47:53 -0700, clk (AT) tele2 (DOT) ch (Christoph Kaufmann) said:

To ensure that those files will become corrupted?

Rebooting a FM server without the proper shutdown procedures will
guarantee that frequently you'll lose data (when the shutdown comes
before data in cache is written to disk) and that eventually you'll get
corrupted files (when a write to disk is happening at the moment of
shutdown) as the end-of-file is left off, or some similar damage is
done.

This is the dumbest thing I've ever heard of. A properly configured,
dedicated FM server can run for months or years without rebooting,
barring necessary system updates. And in those cases, shutting down the
server software properly is mandatory.

Just when you think manglement can't get any more pointy-haired...
--
Lynn Allen
--
www.semiotics.com
Member FBA
FM 10 Certified Developer